Here's a video explaining the bug. Essentially what it is is a bug that can pull aggro onto a disruptor even if units otherwise wouldn't be drawn to it. Essentially due to the way blizzard coded disruptor attacks to warn players before the damage goes off it causes the ai to behave strangely and can lead to some crazy problems.
Disruptor AI Bug
Forum Index > SC2 General |
Arcanous
17 Posts
Here's a video explaining the bug. Essentially what it is is a bug that can pull aggro onto a disruptor even if units otherwise wouldn't be drawn to it. Essentially due to the way blizzard coded disruptor attacks to warn players before the damage goes off it causes the ai to behave strangely and can lead to some crazy problems. | ||
AmericanUmlaut
Germany2558 Posts
| ||
SC2Toastie
Netherlands5725 Posts
| ||
SC2Toastie
Netherlands5725 Posts
Is this where I can balance whine about Zerg receiving UI buffs and Protoss a Game Mechanics Nerf :D:D? | ||
Bey
United States78 Posts
| ||
Excalibur_Z
United States12180 Posts
| ||
Danglars
United States12133 Posts
On December 01 2015 17:08 Bey wrote: OMG this happened to me in a real game. I had an obs over an opposing protoss player and every time he casted his disruptor ability it would pull my army in at him. It actually pulled a ton of units onto the disruptor shot that wouldn't otherwise have died. I couldn't figure out for the life of me what was going on. Good find! I hope they do something to fix this. Abusable by jockeying for position on map, sending out one (as far as I know it aggros units WITHOUT giving the "your army is under attack" prompt, then send out rest in direction of approaching army so they're ready to explode just as your opponent realizes he needs to pull his army back from annihilation. I'll try to find the replay where it was pissing me off. | ||
pure.Wasted
Canada4701 Posts
On December 01 2015 17:21 Excalibur_Z wrote: Nice video, good explanation. Thanks for reporting. Could you also crosspost this on the Battle.net Bug Report forum? http://us.battle.net/sc2/en/forum/13440/ This is definitely something I'd consider a pretty high severity issue. I would assume that this is the same Disruptor bug we were Called to Act on testing the fix for in the PTR. | ||
| ||