This is my trigger. For some reason, this happens after I press the button.
What's wrong with it? I tried to place the If Then Else things one after one, inside each other...
edit:
Also, if I spam the button online on battle.net, the trigger will be executed multiple times resulting in multiple units spawning for me. That's impossible to test offline, but UI delays are a problem source during online play.
-> You should add a check if the dialog is visible for the player to fix that problem.
But you might want to experience the problem yourself first.
edit:
Also, if I spam the button online on battle.net, the trigger will be executed multiple times resulting in multiple units spawning for me. That's impossible to test offline, but UI delays are a problem source during online play.
-> You should add a check if the dialog is visible for the player to fix that problem.
But you might want to experience the problem yourself first.
An easy fix is to use the Turn (current trigger) Off action at the start of the actions, then at the end add a Wait action followed by Turn (current trigger) On... or if multiple people will have access to the button at the same time, throw a switch instead and make that switch part of the conditions.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
This is my trigger. For some reason, this happens after I press the button. What's wrong with it? I tried to place the If Then Else things one after one, inside each other...
Change the unit create action to Unit - Create units with default facing.
Angle between points is calculated for setting the "facing ...".
You need to chose "any player" in the event.
edit:
Also, if I spam the button online on battle.net, the trigger will be executed multiple times resulting in multiple units spawning for me. That's impossible to test offline, but UI delays are a problem source during online play.
-> You should add a check if the dialog is visible for the player to fix that problem.
But you might want to experience the problem yourself first.
An easy fix is to use the Turn (current trigger) Off action at the start of the actions, then at the end add a Wait action followed by Turn (current trigger) On... or if multiple people will have access to the button at the same time, throw a switch instead and make that switch part of the conditions.