[8.42] Shredder second skill lock

[RedNova]

I don't know if this can be fixed by scripting, but here goes.
When using the shredder, it happens sometimes that when you activate the shredder second skill (the close-combat ground only buzzsaw strike, forgot the exact name. Meh) you cannot control your tank until it has delivered the attack (or the game cannot find a path and deems the task impossible), which can lead to a wild and deadly goose chase for the shredder if it's intended target runs away (and usually into a CP and a bunch of creeps).
Usually, it happens when I activate the skill and get stunned while "running to strike". After the stun the order remains and it cannot be cancelled.

I'm trying to remake the pattern but it is quite hard to do alone, since it happens more often when you are stunned by enemy skills.

[Exodus]

This is the normal behaviour of the Warcraft engine in this case, I doubt that I can do something about this :/

[RedNova]

Thanks for the info. I'll be more careful with this guy from now on :-)

To wit: this also happens with the goblin tank.

[TKF]

When the skill gets in range, when the shredder and goblin tank attacks, and it doesn't matter how far away the enemy tank gets when the skill activates.

However the animation delay is the main cause for the delay. I don't know if setting both abilities speed to 5000 would help.

[Exodus]

The main problem is getting stunned while you are about to use your ability (eg trying to get in range to use it). After the stun your unit wants to execute the skill no matter what. This can happen with every skill, but because you wanted to use a short range skill, its a more critical issue.

[DerSatan]

what is the base skill of these goblin stun skills?


is it the dwarfen hammer which he throws? (dunno the name)

[horselance]

Yes it happens with every "target required" skill. And there is no way to stop your tank afterwards. If you are lucky, your enemy hesitates for something and you use your skill then you are free. (if not still dead)
It is a problem of Warcraft itself, not about BT.