Detecting when Bladestorm is issued...

I haven't been able to detect when the order is issued for Bladestorm. I tried

Event: Unit is Issued Order with no target
Condition: IssuedOrder = Order("whirlwind")

and also on a lark tried...

Event: Unit is Issued Order with no target
Condition: IssuedOrder = Order("bladestorm")

Order=whirlwind

that is the exact line from the code in the txt file, so whirlwind should work

Ya that's what I thought. You can also select it from the dropped down of orders with no target, convert it to custom, and see that the order is "whirlwind".

However, I still can't get it to detect the issued order. It's really wierd. I don't have this problem with any of the other orders I've tried. Just Bladestorm.

After digging even further into this problem, I dug up the following entries in the UI\TriggerData.txt:


I can take this to mean the following:
1) the order is definately "whirlwind"
2) the order type is definately "no target"

I was curious if Blizzard had just made a mistake when the left the "WESTRING_UNITORDERNOTARG_BLADESTORM" and tried changing it to "WESTRING_UNITORDERNOTARG_WHIRLWIND" and then implanting it into the War3patch.mpq. No luck with that either.

Running out of ideas....I've attached a map I made that should display a text message when Bladestorm is ordered. As you can see, it doesn't work.

you took both of those way out of context, they are both for the same thing. One is for the pulldown menu the other is for the presets for comparison

I decided that there is a problem with the Event. I confirmed this a when I created the following trigger for testing purposes.

Event: A Unit Owned by X is issued an Order with no target

Condition: Issued Order equal to Order("stop")

Action: Unit Order (Ordered Unit) to Order("whirlwind")

OK. The above trigger creates a round-about method of issuing the whirlwind through a trigger instead. When the unit is issued to stop, it casts whirlwind.

This works. Not only does the whirlwind work, but the original trigger I created to DETECT the whirlwind also works! (see the first post)

So that begs the question...what exactly doesn't work? Obviously it's the event. The event only detects when Bladestorm has been issued IF IT WAS ISSUED FROM A TRIGGER, not if you issued it from in-game by clicking on it or using the hotkey.

It may not exactly be the event that's the problem. After all, it works fine when your using a trigger. But at the very least, it's in whatever the message the engine uses to tell the event an order has been fired for bladestorm.

This has to be a bug. Anyway, In the process of all this, I figured out a work-around. (although it requires spell editing) Basically, just make Bladestorm a UNIT ABILITY instead with no hotkey, no button, no button position. Then take another spell or ability you aren't using that doesn't have a target, and give it Bladestorms tooltips, button graphics, mana cost and cooldown. Just assign Bladestorm as a unit ability, and your other custom spell where as a hero ability where Bladestorm would normally be...then just create a trigger that issues Bladestorm whenever the other spell is ordered. I haven't tested this yet, but it should work.

This problem has been discussed many times before, its a bug that in-game, the order is not actually issued, or is not what we expect it to be, instead it is simply done. As you stated, if its accessed via a trigger it all works fine, otherwise the order is never detected, the same is true for some auto-cast spells, and defend i believe

Well it's really annoying:)