From a programming point of view I think you need to start using arrays.
A solution to the example you gave:
- Create a variable of type dialog item
- Tick the array box and set to 4
- Create a map initialize trigger that sets each variable:
Event:
Map Initialization
Actions:
Set DialogItemArray[1] = (whatever btn_b1 equals)
Set DialogItemArray[2] = (whatever btn_b2 equals)
Set DialogItemArray[3] = (whatever btn_b3 equals)
Set DialogItemArray[4] = (whatever btn_b4 equals)
- Now to hide all the buttons:
Local variable:
integer - button = 1
Actions:
For Each button From 1 to 4 (Increment 1) Do Actions -
Action - Hide DialogItemArray[button] for (Player group((Triggering player)))
So you have to set each button in the array but once you've done that you can do anything to all your buttons with little effort show/hide etc etc. This can be done with almost anything such as units or points/regions. You can see how this is useful when you have for example 50 buttons. If you change a button in the array then all the triggers will change the button they affect.
Hope this helps if this was the problem you were experiencing. Though this would require change to a lot of what you may have done it does pay off in the long run.
0
How different is trigger 01 from trigger 02?
0
From a programming point of view I think you need to start using arrays.
A solution to the example you gave:
- Create a variable of type dialog item
- Tick the array box and set to 4
- Create a map initialize trigger that sets each variable:
Event: Map Initialization
Actions:
Set DialogItemArray[1] = (whatever btn_b1 equals)
Set DialogItemArray[2] = (whatever btn_b2 equals)
Set DialogItemArray[3] = (whatever btn_b3 equals)
Set DialogItemArray[4] = (whatever btn_b4 equals)
- Now to hide all the buttons:
Local variable: integer - button = 1
Actions:
For Each button From 1 to 4 (Increment 1) Do Actions -
Action - Hide DialogItemArray[button] for (Player group((Triggering player)))
So you have to set each button in the array but once you've done that you can do anything to all your buttons with little effort show/hide etc etc. This can be done with almost anything such as units or points/regions. You can see how this is useful when you have for example 50 buttons. If you change a button in the array then all the triggers will change the button they affect.
Hope this helps if this was the problem you were experiencing. Though this would require change to a lot of what you may have done it does pay off in the long run.
0
It's available with the editor on Starcraft 2's release
0
I think he means no more than 3 as a minimum number of players required to complete a game