Can someone confirm that bug for me? (I can't right now). Like, can someone just create a loop which loops 2039 times and checks if it works or not? Wouldn't that put this mystery to bed?
It can run 2038 threads at once. I don't know when it breaks in continuous lines of code though. Although I suppose I could just run a repeat forever that increments x and prints it to the screen and see where it dies. But I also think that continuous lines depend more on the computer rather than the editor itself actually.
Edit: I got to 7452 loops before it broke for me. Using
I wasnt sure if "line count" was actual lines, or if a loop added to the line count. I didnt have a "trigger error" but simply stuff in that trigger stopped happening. Namingly, a dialog box was not created. If I moved that part of the trigger to the top, it was made, but the last portion of another dialog box (now at the bottom of the trigger) was not being made. Nothing returned an error though.
Is the issue you are testing about trigger length, or actions per minute? If you are testing actions per minute, then that would be related to every action in every trigger, and then the type of action. For instance, modify variable+1, running in an endless loop will complete more cycles than a "create dialog item" in a given time frame.
A test you could do is to manually create 1000 "modify variable +1" (you could copy and paste a bunch at a time) and then after it runs, display the number. That could give you an idea if there is a max lines count limit, or just a max actions per frame limit.
@GlornII: Go
I must point out that I correct myself later. It's 2038 actually.
edit: also note errors at line 340 doesn't mean it broke 340 kines in, it means the 340th line in your code broke it.
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
Can someone confirm that bug for me? (I can't right now). Like, can someone just create a loop which loops 2039 times and checks if it works or not? Wouldn't that put this mystery to bed?
Or unless the condition counts in which case that is 4078 lines.
Or are we talking brand new lines of code and not counting repeats?
Otherwise it's hard to say if people experiencing this isn't some other subtle bug they're running into
@finiteturtles: Go
It can run 2038 threads at once. I don't know when it breaks in continuous lines of code though. Although I suppose I could just run a repeat forever that increments x and prints it to the screen and see where it dies. But I also think that continuous lines depend more on the computer rather than the editor itself actually.
Edit: I got to 7452 loops before it broke for me. Using
Edit2: Actually It's still running, it just freezes up for a few minutes.
Edit3: It looks like it's executing about 2000 times a frame
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
I wasnt sure if "line count" was actual lines, or if a loop added to the line count. I didnt have a "trigger error" but simply stuff in that trigger stopped happening. Namingly, a dialog box was not created. If I moved that part of the trigger to the top, it was made, but the last portion of another dialog box (now at the bottom of the trigger) was not being made. Nothing returned an error though.
Is the issue you are testing about trigger length, or actions per minute? If you are testing actions per minute, then that would be related to every action in every trigger, and then the type of action. For instance, modify variable+1, running in an endless loop will complete more cycles than a "create dialog item" in a given time frame.
A test you could do is to manually create 1000 "modify variable +1" (you could copy and paste a bunch at a time) and then after it runs, display the number. That could give you an idea if there is a max lines count limit, or just a max actions per frame limit.
Skype: [email protected] Current Project: Custom Hero Arena! US: battlenet:://starcraft/map/1/263274 EU: battlenet:://starcraft/map/2/186418