HA I LIED. Fougerite.dll was updated. There was a small problem that the manual saving caused multiple timers reported by salva. All seems to be fine now REALLY. LOL.
MODIFIED THE PATCHER RE-PATCH OR USE THE PREPATCHED FILES.
Fougerite.dll was updated.
Fixing the last background save issue.
The original saving didn't cause this issue, since the server was "held up" by the lagg, and placing an object didn't hurt the list while iterating It. It is now safe to say that the saving system is completely threaded without issues, and the save system will cause no lagg even on a 71000 object counted map. Legacy's saving system works as It is intended to be now
The problem when using command "quit" (Server saving then becoming unresponsive, then hardly closing) was solved. You may use both CTRL + C or the command quit to stop the server. Both of them were tested using a map that has 71000 objects. The server should save, manually trigger the shutdown, and simply close on both. The quit command also Kills the process at the very end instead of triggering Application.Quit. CTRL+C does the exact same, but leaves your console open at the end. They both do the same, basically triggering LibRust.Shutdown();. All should be fine with the saving system from now on.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.