Pressing "Stop", destroying target before Burst= finishes resets the burst counter

Bug #895567 reported by EVA-251
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ares
Fix Released
Medium
Unassigned

Bug Description

There's not much more to it. If a unit with a multiple burst weapon destroys its target before it has Burst= number of shots, the burst count is reset.

In addition, by using the Stop command, the player can manually reset the burst, which can be exploited to give the cheater a significant advantage over his opponent.

##### STEPS TO REPRODUCE #####
1: Get an elite Apocalypse Tank
2: Attack a group of Prism Tanks with the elite Apoc- he will finish off the Prism Tank before firing all four rounds, and move on to the next Prism- and keep going until there are no more tanks to kill.

or
Just target an enemy unit, spam attack orders and mash S at the same time.

##### ADDITIONAL INFORMATION #####
In addition, I've seen the AI abuse this bug a few rare times, with Apocalypse Tanks firing random 10-15 super rapid-fire bursts.

Revision history for this message
skyboy (skyboy) wrote :

Yeah, this has been a bug since Ra2 1.006, possibly before. Funny to watch how people react to an elite apoc destroying their base without stopping to reload, not as funny when you're receiving it.

I vote removing it though

Revision history for this message
reaperrr (reaperrr) wrote :

This has been a bug since at least TS.

Revision history for this message
Chanterier (speederyr) wrote :

I was just able to notice how truly exploitable it is. Any unit with burst=2+ can be used for abuse. This is almost as rage-worthy as the guard-command-on-enemy-harvester issue, it really bothers me that WW never fixed this.

Revision history for this message
falaka21 (falaka21) wrote :

This makes Apoc Tanks much more effective and unbalanced...(invincible in large groups) I support you in this matter ,EVA-251..

Changed in ares:
assignee: DCoder DCoder (dcoder1337) → nobody
Revision history for this message
Mig Eater (mig-eater) wrote :

Nearly five years later, any chance of this being fixed in the future?

Revision history for this message
AetherDawn (aetherdawn) wrote :

It had been fixed in NPEXT IIRC...
When will ARES?

tyuah8 (tyuah8)
Changed in ares:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.