Amnesia: The Second Dimension [READY FOR LAUNCH]

[MrBehemoth]

I decided to take a scientific approach to this. Over the last week, all of my free time at home has been spent doing experiments. Setting up test maps, using control groups, tweaking variables and processes, recording and comparing results. I don't know anything about statistical significance or any of that malarky, but, as of tonight I can make a few conclusions that I'm 99.9% sure are accurate. (Some of this has already been said.)

1) There is a limit on callbacks as discussed.

2) This includes timers.

3) Once the limit is passed, the engine will crash at the next load. However, it's possible to go way over the limit before loading. That's why it sometimes seems like the limit is ~65k. But using short tests and frequent loading over long periods of time, I've pinned it down as closer to ~58,300, or ~61,700 if OnStart(), OnEnter() and OnLeave() count as callbacks.

I don't know what the significance of these numbers is, unless it's 65,535 with some kind of deduction.

4) This is the important (and disappointing) part. This is not a limit on the number of callbacks (event listeners) you can add. It's a limit on the number of callbacks getting called.

To clarify, if you set up an empty map with two entities and used AddEntityCollideCallback() just once, with no other script, if the entities collide more than about 58,000 times then the engine will crash the next time it loads a map.

5) As well as relying on collision callbacks for all kinds of puzzles and gameplay features, the "timerless loop" uses 60 collision callbacks per second. All this is why almost entirely getting rid of timers made the mod last longer before crashing, but since it still relies heavily on callbacks, it mounts up to over 58k easily in about 15 minutes of play.

6) I really don't know what to do about this.