Fougerite Saving has been tested for a couple of days, this build seems to be fine, and running without issues. Please try It.
PATCHER WAS MODIFIED RE-PATCH OR USE PREPATCHED DLLS.
IronPythonModule updated. Please delete IronPython.Deps from the Managed Folder. Add every new IronPython and Microsoft dlls to the Managed folder, since I updated the engine from 2014 to the latest available .NET 3.5 support. (late 2016)
Web.CreateAsyncHTTPRequest has been added for plugins to use. These webrequests shouldn't be causing laggs while they are being used, and get/post requests are also supported. You will have to specify a method with a string parameter which is the callback function expecting the result.
The 1.6.9 will be dropping the usage of external script language support, and will have a built in one with auto reload support, and auto load support. The directory structure will be changing, there will be a long note of It.
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.