The skipTime script command makes incorrect changes to the game world time when skipping large amounts of time (say one year).
When given extremely large numbers (say three years), it starts a continuous "time warp" effect that reduces the game to about 1 FPS. This condition is persistent until the game is restarted, and may continue until the game crashes with an "Out of memory" type error message.
Both of these issues seem to be related to the way the game stores the current date.
Workaround:
Use the setDate command to make large changes to game time
Tested in 0.71.106998
Maybe skiptime wasnt designed to handle large intervals for which setdate is probably more suitable
@KillZone Kid
Undoubtedly, but commands should be a bit more robust. The persistent low FPS time warp state this issue can create has potential for malicious use, ruining not only the current mission but the current game instance.
Time warp low FPS issue still a problem in dev build 1.43.130502. FPS is subsequent missions is slightly better than before (8 FPS), but mission editor reports strange config errors that normally don't occur, suggesting this issue somehow affects the game config.
Unable to reproduce persistent low FPS issue in build 1.54, but inaccurate resulting time/date after skipTime persists.
Trivial, but still a bug.