In my Hunger Games map, I'm using powerups that spawn via timers instead of health and ammo droids. Today I was adjusting the timers when the game started freezing at the point in the script when all of the powerup spawn timers were started. After I commented out some of the timers in the script, it stopped freezing. As far as I can tell, there's nothing wrong with my code; I literally copied and pasted the timers (the original ones were tested and fully functional) and bumped up the number in the name each time. This got me wondering: is there a hard-coded limit on the number of timers that can be running at one time in the game?

I had a similar issue with the powerups themselves. I kept getting this error in the log: It showed no correlation with any particular timer or powerup. I would get a period where powerups would spawn just fine, then I'd get a few to several of these errors in a row. I got the error a lot when the powerups were first spawning, so I spread out the spawn times some more and the error occurred less frequently. Is there also a limit on the number of powerup items that can exist at the same time?
(Note: it might also be that I'm hitting the overall object limit in my map, because I have a LOT of stuff in the world)


Here are the ammo spawn functions in my lua. All of the timers have been tested and are functional (except the last few in the normal "ammospawn()" function, which seemed to be what was causing the freeze). In the game, the armorspawn() starts first, and 30 seconds later all of the other spawns are started together.

I remember running into a similar problem when I tried getting delayed shield regeneration working. I got the delay working, but due to the nature of the function, which was to create a timer each time the player was hit, the game would freeze pretty shortly after beginning a match.

While I don't think there's necessarily a limit to the amount of timers you can have, there's probably a memory management issue with timers that disallows too many of them to be running at once or being created too rapidly, or something.

Yeah, I guess I'll have to reduce the number of spawns I have. Another thing that might be (but probably isn't) related is the way I reset the timers: instead of each one restarting itself, I have them set in a loop, so that when one timer ends, it starts a different one, and each timer is restarted once and only once until it comes back around to the first timer. At the beginninng though, I start about 3/4 of the timers in the loop. I don't think this should cause any issues, but I don't know, maybe the game just doesn't like big loops of timers like that :S

EDIT: What about the powerups? Does anyone know if there's a limit on those?

EDIT 2: It occurred to me that there might be a SetMemoryPoolSize for powerups, and it turns out there is. I set it to 512 and stopped getting the error. It's kind of annoying that the error doesn't say anything about the memory pool though.