Ordering Building to Cancel Construction Doesn't Work

[DEE-BOO]

The ALLOW and DENY messages show, but canceling doesn't work. The triggers check if the building is being build on Grass Trim, if it is not being build on Grass Trim, the building should cancel. Test map below.

Triggers

• Only Build On Trim Grass
  • Events
    • Unit - A unit Begins construction
  • Conditions
  • Actions
    • Set Fence_Unit = (Constructing structure)
    • Set Fence_TempPoint[0] = (Position of Fence_Unit)
    • Set Fence_TempPoint[1] = (Fence_TempPoint[0] offset by 45.26 towards 45.00 degrees)
    • Set Fence_TempPoint[2] = (Fence_TempPoint[0] offset by 45.26 towards 135.00 degrees)
    • Set Fence_TempPoint[3] = (Fence_TempPoint[0] offset by 45.26 towards 225.00 degrees)
    • Set Fence_TempPoint[4] = (Fence_TempPoint[0] offset by 45.26 towards 315.00 degrees)
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Terrain type at Fence_TempPoint[1]) Equal to Cityscape - Grass Trim
        • (Terrain type at Fence_TempPoint[2]) Equal to Cityscape - Grass Trim
        • (Terrain type at Fence_TempPoint[3]) Equal to Cityscape - Grass Trim
        • (Terrain type at Fence_TempPoint[4]) Equal to Cityscape - Grass Trim
      • Then - Actions
        • Game - Display to (All players) for 0.00 seconds the text: ALLOW
      • Else - Actions
        • Custom script: call IssueImmediateOrderById (udg_Fence_Unit, 851976)
        • Game - Display to (All players) for 0.00 seconds the text: DENY
    • Custom script: call RemoveLocation (udg_Fence_TempPoint[0])
    • Custom script: call RemoveLocation (udg_Fence_TempPoint[1])
    • Custom script: call RemoveLocation (udg_Fence_TempPoint[2])
    • Custom script: call RemoveLocation (udg_Fence_TempPoint[3])
    • Custom script: call RemoveLocation (udg_Fence_TempPoint[4])

 

[KILLCIDE]

Try adding a 0 second wait before you cancel the order.

 

[DEE-BOO]

Defuq? Worked perfectly, thanks man. OFF TOPIC: I need to lie down, my back is killing me.

 

[KILLCIDE]

No prob. I actually asked DSG why adding a wait timer before the function call fixed it, and this is what he told me:

 

[DEE-BOO]

Weird, there should be a list of weird stuff to take notice of. Anyways thanks again . Solved

 

[Flux]

Just let me remind you guys that 0 second wait is actually about 0.1 to 0.2 second. It is not really accurate. I don't know if that will bother you or not just saying. If you really want accuracy, 0 second timer is the way to go, but timers are hard to use in GUI so you will probably end up using /learning JASS.

 

[Chaosy]

I think a wait can be +- .27 seconds. At least so I hear

So it's better to use a timer that expires in 0 seconds, I think. If that bugs just make it 0.01 seconds, it will still be more accurate.

 

[Dr Super Good]

What I said applies for order events and not construction events although likely something similar is happening (event fires before the building finishes initialization so cannot be cancelled).

For what you are after doing you should be using the Unit Issued Point Order event so you can deny the structure as it is ordered instead of when construction starts.