The SaveInfo issue is actually an internal problem with one of the timestamp functions. It causes other problems too - for example, trying /showmessage and a message showing that there is already a showmessage active, when there clearly isn't, and problems with Lyse spamming all over the show.
Developers can fix the SaveInfo problem by resetting the variable which stores the timestamp when the message shows.
(Save::LoadInfo() - if(iSavedSlot == INVALID_SAVE_INFO_SLOT) [...])
The initial timestamp problem is probably in mktime(). Personally I just use (Get)TickCount for time stamping.
Developers can fix the SaveInfo problem by resetting the variable which stores the timestamp when the message shows.
(Save::LoadInfo() - if(iSavedSlot == INVALID_SAVE_INFO_SLOT) [...])
The initial timestamp problem is probably in mktime(). Personally I just use (Get)TickCount for time stamping.