Re-ordering variable order

[Snigglel]

Hi! I want to be able to store any order into a variable to re-order it after using an ability but I can't seem to find a function for it in GUI.

Please help!

 

[Chaosy]

Event - issued order
set variable = issued order

 

[Snigglel]

Yes, but then I want to execute that order again. How do I do that?

 

[Chaosy]

Guess you will also have to save target/target type which makes it annoying but it's still simple.

 

[Snigglel]

Hmm... If it's just a point or unit target, then yes, but what if my unit is about to build a building? Or cast a spell?

 

[Chaosy]

All orders are catchable with events, but it wll be hard to repeat certain orders on demand anyway.
Ability on cooldown, building already existing, pathing blocked etc

 

[Dr Super Good]

Hmm... If it's just a point or unit target, then yes, but what if my unit is about to build a building? Or cast a spell?

Those are also instant, point or widget target orders.

You will need multiple variables to store the order correctly.

• Integer Order ID: The order ID integer of the triggering order. Must be order ID and not string because some orders have no order string.
• Unit Target: Target unit of triggering unit target order.
• Item Target: Target item of triggering item target order.
• Destructable Target: Target destructable of triggering unit target order.
• Point Target: Target point of triggering point target order.
• Integer Order Type: Unique integer value for each type of order. Is used by flow control code to select which order action to run.

Use separate triggers for each basic type of order. Order targeting object trigger has extra logic to resolve what type of target was used. This is likely done by checking the values returned by the appropriate event response functions for a non-null (not no value) value. Each type of order is given a unique integer used by the order type variable. This integer can be used inside an if/then/else structure to call the appropiate issue order action.

If using JASS the following variables can be merged together...

• Unit Target: Target unit of triggering unit target order.
• Item Target: Target item of triggering item target order.
• Destructable Target: Target destructable of triggering unit target order.

Into...

• Widget Target: Target widget of triggering object target order.

And 2 of the unique integer constants used for order type could be removed. This is because the order can be processed as a widget rather than its 3 child types.

Integer Order Type could be replaced with Trigger Order Type. One sets this to a trigger which sole action is the appropriate issue order action. This avoids the ugly constants and flow control but will be slower due to the huge overhead of running a trigger as opposed to calling a function or performing some tests.

The lookup of Integer Order Type could be optimized using a binary search tree arrangement. This would reduce the worst case lookup time from O(n) to O(log2(n)) where n is 5 (3 for JASS) for slightly fewer comparison operations.

 

[Snigglel]

Those are also instant, point or widget target orders.

You will need multiple variables to store the order correctly.

• Integer Order ID: The order ID integer of the triggering order. Must be order ID and not string because some orders have no order string.
• Unit Target: Target unit of triggering unit target order.
• Item Target: Target item of triggering...

Thank you very much Dr Super Good!