Windows Server crashes when getting GRAVE message in client server distribution

[jasonrohrer]

I'm guessing this is because the server is missing its settings files and various TXT files, but I haven't been able to pin-point the problem.

The crash happens when trying to print the GO message here:

https://github.com/jasonrohrer/OneLife/blob/86232707b6dd0a032f8c063b2f9df322828aca27/server/server.cpp#L21637

Very strangely, the client is receiving a GO message with a (null) string, like this:

GO
-68 15 0 0 -0.000000 0(null) eve=-943501440

But the string isn't NULL, which is the strange thing.

I'm going to have to try running the server without its files on Linux to see if I can get more information about what's going on here.

And even if the files are missing, the server shouldn't crash.

[jasonrohrer]

I'm guessing that these missing files will fix the crash, but I'm not sure.

Put these TXT files right in the same folder as OneLifeServer.exe:
serverTextFiles.zip

Put these settings files in a "settings" folder in the same folder as OneLifeServer.exe:
severSettingsFiles.zip

Note that the client "settings" folder is NOT needed for the server.

So perhaps you can make a copy of the OneLife folder, to make a spot for the server to run in isolation, and the replace the existing "settings" folder (which is used by the client) with the new settings folder from the ZIP archive above.