I can't remember if I asked this before but is there a reliable way to detect the game being reloaded, without EUDs? I'm thinking of tricks like the ones used in cheat detection etc.

You could make the saving function crash by having more than 65536 triggers.

I could be wrong here (and I can't test right now), but if memory serves:

Triggers with waits in them reset when the map loads. If you can dedicate a player to be indefinitely wait-blocked (or just having a long wait in it to make it unlikely that a save would land on the cycle where the trigger completes), you could detect a trigger having been executed more than once over the course of the game.



Post has been edited 2 time(s), last time on Jan 12 2013, 12:46 am by Roy.

I tested your triggers out, and what happened is the Wait got set to 0 when it loaded, but the trigger didn't restart from the beginning.

The same principle you've explained here could still be used to detect loading, though. One way would be to have a DC timer that approximately matches the long Wait, except it's slightly shorter. If at any point the DC is higher than 24, and the action after the Wait is triggered, then you know the game was loaded.

Note that I went with 24 DC to take into account the offset that's going to happen when the timer and Wait eventually rollover. To prevent this offset from accumulating, you can figure out the offset, then make the timer regulate itself by subtracting some number of DCs after each rollover (like what we do in real life with leap seconds).

In reality, you could probably just use the Wait by itself and use the action after it to detect loading. 4294967295 milliseconds is 7 weeks, so it's most likely unnecessary to account for rollovers, especially with no saving taking place.