I have tried manually setting the first angle to 290 and still seeing this mess up. The text messages showing is to show me which then/else is playing. 3 and 4 never show up, only 1, 2, and rawr show.
I never noticed my triggers go beyond the 2nd If Then Else. After that it gives an underflow or overflow error (I don't remember which). Fortunately there were alternative ways of doing what I wanted to do, but I don't know if that's your case.
The last three If Then Else statements should be on the same level as line 40, however, if I am understanding your trigger correctly.
A while ago, I ran into a problem with a (facing of unit) function call. It was in the form 235 < facing of unit < 270, but it never seemed to evaluate to true, no matter how I turned the unit.
Just now, I made a map that printed out (facing of unit) to the screen for my unit and it looks like facing works a little differently than might be expected:
90
^
180/-180 < > 0
V
-90
That is, when the unit was point left, it's facing was 0. When the unit was down and left, it's facing was like -45. and up and left was 45.
So the unit's facing is between -180 and 180, not 0 and 360 like the editor displays.
Didn't work. XD
I have used tons of if/then/elses in other triggers that I think are working correctly. Guess I'll try mixing them up. I know a way to reduce 2 of the if/then/elses. Which should be what I need.
Thanks for the responses, i'll post if it was the if/then/elses after I do the fix.
Removed 2 and tried, then tried with it by it self and they still didn't work. Reloaded map and I got this error message:
Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, 92DA6208, Lib: 0)
Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, 6BD840C0, Lib: 0)
Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, EBEE879F, Lib: 0)
Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, CF3103C6, Lib: 0)
Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, B00573A0, Lib: 0)
Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, D18DCFB3, Lib: 0)
Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, 084C0D82, Lib: 0)
Idk if this is new or not tho, I normally get error messages and ignore them because they don't seem to infect anything in game.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
This part: http://pastebin.com/kRsBryUQ is skipping the first 2 and going straight to the third.
Full trigger, angle is random point is set and velocity I think is .5 or .6...
http://pastebin.com/9Bmfd4ij
I have tried manually setting the first angle to 290 and still seeing this mess up. The text messages showing is to show me which then/else is playing. 3 and 4 never show up, only 1, 2, and rawr show.
I never noticed my triggers go beyond the 2nd If Then Else. After that it gives an underflow or overflow error (I don't remember which). Fortunately there were alternative ways of doing what I wanted to do, but I don't know if that's your case.
The last three If Then Else statements should be on the same level as line 40, however, if I am understanding your trigger correctly.
A while ago, I ran into a problem with a (facing of unit) function call. It was in the form 235 < facing of unit < 270, but it never seemed to evaluate to true, no matter how I turned the unit.
Just now, I made a map that printed out (facing of unit) to the screen for my unit and it looks like facing works a little differently than might be expected:
90 ^ 180/-180 < > 0 V -90That is, when the unit was point left, it's facing was 0. When the unit was down and left, it's facing was like -45. and up and left was 45.
So the unit's facing is between -180 and 180, not 0 and 360 like the editor displays.
@roguelike: Go
Didn't work. XD I have used tons of if/then/elses in other triggers that I think are working correctly. Guess I'll try mixing them up. I know a way to reduce 2 of the if/then/elses. Which should be what I need.
Thanks for the responses, i'll post if it was the if/then/elses after I do the fix.
@Skittles17: Go
Removed 2 and tried, then tried with it by it self and they still didn't work. Reloaded map and I got this error message: Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, 92DA6208, Lib: 0) Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, 6BD840C0, Lib: 0) Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, EBEE879F, Lib: 0) Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, CF3103C6, Lib: 0) Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, B00573A0, Lib: 0) Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, D18DCFB3, Lib: 0) Warning: Invalid trigger element reference removed from Function Call 'If Then Else' (Function Call, 084C0D82, Lib: 0)
Idk if this is new or not tho, I normally get error messages and ignore them because they don't seem to infect anything in game.