i grew pretty dependant with "set switch 1", "toggle" or "release switch 2"
they were very handy events
but i could never find a good substitute for them in warcraft 3 nor galaxy editor pretty much because its a much more sophisticated editor.
what can i use in galaxy editor thats acts like a "switch" condition?
This is new to me, so let me ask thee of more knowledge
So you can set a trigger that is set to go on "Boolean X True", and have a different trigger be what affects whether Boolean X is true or false. In theory this would work correct?
Assuming that is correct, how would one physically set this up in the triggers module. Would the 2 triggers and the boolean (which is a variable right?) have to be within the same trigger?
Or could one set trigger 1, boolean x, and trigger 2 as indipendents in the global hierarchy?
and sorry to go on and on, but assuming the immediately above is true, how would one link the three? would source: value be the place to link them?
There are global variables and local variables. Global variables are defined in the same place triggers are defined (the tree view at the left of the trigger editor) and local variables are defined within a trigger. All triggers have access to global variables (read and write), but to local variables only the instance of a trigger where the variable was defined has access to it.
If you set a global boolean variable to True, it's True to all triggers until it's changed to False.
i grew pretty dependant with "set switch 1", "toggle" or "release switch 2" they were very handy events
but i could never find a good substitute for them in warcraft 3 nor galaxy editor pretty much because its a much more sophisticated editor. what can i use in galaxy editor thats acts like a "switch" condition?
Booleans.
You can create variables of type Boolean. They have only two values: True and False. It's basically Switched and Unswitched.
This is new to me, so let me ask thee of more knowledge
So you can set a trigger that is set to go on "Boolean X True", and have a different trigger be what affects whether Boolean X is true or false. In theory this would work correct?
Assuming that is correct, how would one physically set this up in the triggers module. Would the 2 triggers and the boolean (which is a variable right?) have to be within the same trigger?
Or could one set trigger 1, boolean x, and trigger 2 as indipendents in the global hierarchy?
and sorry to go on and on, but assuming the immediately above is true, how would one link the three? would source: value be the place to link them?
There are global variables and local variables. Global variables are defined in the same place triggers are defined (the tree view at the left of the trigger editor) and local variables are defined within a trigger. All triggers have access to global variables (read and write), but to local variables only the instance of a trigger where the variable was defined has access to it.
If you set a global boolean variable to True, it's True to all triggers until it's changed to False.
@A1win: Go
cheers A1win