i don't quite understand.. if i were to run a for loop with the variable X from 1 to X, (let X = 5) the loop would first set X to 1 and then run the loop once. then it would evaluate if 1 = X (which it should be now) i'm not sure... this just seems odd
I think it works like this, since the actual loop statement is evaluated first, then it will set the integer to 1 then 2 then 3 etc, so you eventually end up with what you originally started and it doesn't bug because the first line is only evaluated once. I am just speculating btw don't take my word for it
@Usernameisntworkingright: Go
Is this trigger just a set up of one team? or both?
@Usernameisntworkingright: Go
i don't quite understand.. if i were to run a for loop with the variable X from 1 to X, (let X = 5) the loop would first set X to 1 and then run the loop once. then it would evaluate if 1 = X (which it should be now) i'm not sure... this just seems odd
@Usernameisntworkingright: Go
oh wait! nevermind... I put your trigger into my map and it works perfectly! THANK YOU!1!!!!1!1!!!
@EVILEMU: Go
I think it works like this, since the actual loop statement is evaluated first, then it will set the integer to 1 then 2 then 3 etc, so you eventually end up with what you originally started and it doesn't bug because the first line is only evaluated once. I am just speculating btw don't take my word for it