Yeah, it's a 13 player map, but I don't have any duplicate triggers, I just loop through arrays to account for all the players so that doesn't grossly inflate the script size, it might as well be one player.
I suppose I have to deal with it though. No one feature in this map exceeds 500 lines of code, so pruning seems like the only option if that's really the script limit.
Alright, original posts deleted because my original theories were false. Turns out I just hit a script limit; that is, too many triggers affecting the overall script size. For future reference, the limit seems to be around 40,000 lines. I really hope this is not the case, but I've reached a point where all I have to do is make one more trigger and the game fails due to too large a script, so I don't know what else it could be.
Just so you know, no error pops up, the game just starts and none of the triggers work at all. If you open the map up with a debug window, all it says is "Too many threads: script too large"
So I'm not sure what I'm doing wrong here, the -move and -exit command works fine, but the -loc didn't seem to work at all, in fact -loc and -move didn't seem to print any text. I managed to fix it by turning the line:
d(4,"Current Viewing Location:");
into:
print(4,"Current Viewing Location:");
But I can't mess with the line:
dp(CameraGetTarget(1));
without making all the other commands fail to work altogether. I was trying to store CameraGetTarget into a variable so I could print it out, but to no avail. I can't even figure out what the dp() and d() functions even do, but I guess I'm really nub at this sorta thing. o.O
0
@s3rius: Go
Yeah, it's a 13 player map, but I don't have any duplicate triggers, I just loop through arrays to account for all the players so that doesn't grossly inflate the script size, it might as well be one player.
I suppose I have to deal with it though. No one feature in this map exceeds 500 lines of code, so pruning seems like the only option if that's really the script limit.
0
Alright, original posts deleted because my original theories were false. Turns out I just hit a script limit; that is, too many triggers affecting the overall script size. For future reference, the limit seems to be around 40,000 lines. I really hope this is not the case, but I've reached a point where all I have to do is make one more trigger and the game fails due to too large a script, so I don't know what else it could be.
Just so you know, no error pops up, the game just starts and none of the triggers work at all. If you open the map up with a debug window, all it says is "Too many threads: script too large"
0
@vjeux: Go
Y'know, when I realized this, I slapped myself, so it's all good now.
0
@vjeux: Go
So I'm not sure what I'm doing wrong here, the -move and -exit command works fine, but the -loc didn't seem to work at all, in fact -loc and -move didn't seem to print any text. I managed to fix it by turning the line:
into:
But I can't mess with the line:
without making all the other commands fail to work altogether. I was trying to store CameraGetTarget into a variable so I could print it out, but to no avail. I can't even figure out what the dp() and d() functions even do, but I guess I'm really nub at this sorta thing. o.O