Why would you need a nested while-loop? For one player, it is one action to set the alliance aspect "shared vision" to false; for multiple players you might need one single loop.
nested while loop inst something very slow. It will iterate only 256 times for 16 players. It is nothing. I have done very big script for each element in 256*256 array, with no lag. The only thing you should do is a small function (or even action), like disableSharedVision() with loop inside it
Is it possible to control shared vision somewhere other than in triggers? I really don't want to create nested while loops just to turn it off...
Why would you need a nested while-loop? For one player, it is one action to set the alliance aspect "shared vision" to false; for multiple players you might need one single loop.
It really depends on what kind of event you want to turn shared vision on/off.
nested while loop inst something very slow. It will iterate only 256 times for 16 players. It is nothing. I have done very big script for each element in 256*256 array, with no lag. The only thing you should do is a small function (or even action), like disableSharedVision() with loop inside it
@Frizi: Go
why the hell would you need a while loop.... use a for loop for gods sake
should only need to loop once and do if thens for each player depending on under what conditions you want to turn vision on and off
you can set vision in a
simple if thens should handle the rest