Frequently kicked to login & progress loss when using Windows (non-docker) build

[DuskViper]

Hi there! First off, thank you so much to everyone who has worked on this and for keeping at it. I still remember those Skype group chats back then - I just recently stumbled upon this again and it is amazing what you made possible. You really made a dream come true!

Thus excited, these past few days I have been trying to play a bit of LU like back then.

I came upon the following issue(s) and I am curious to know your opinion on this:

Problem description:

1. I can play and connect but the server will kick me (and other players if connected) back to login after a while saying "A server has lost the connection" in the console. This causes the progress since the last auto- or forcesave to be lost.
   This mostly happens in Avant Gardens when rebuilding destroyed mechs. Sometimes I can rebuild a small number of them but it reliably crashes after a few mechs at the latest when rebuilding (immediately at building start, at completion or up to a few seconds after completion).
2. On top of this, there seems to be a similar kick to login every 10 minutes or so while the cmd/powershell terminal freezes up.

This seems to happen on all kinds of windows builds (without Docker) - I tried this with a release server, a self-built server, with the 3.1.0 server and alternated between the Darkflame and the LU1.10.64 client, problem persists. Sharedconfig.ini and boot.cfg are adjusted as requested in the READMEs.

HOWEVER, when using Docker (which is basically Linux iiuc), then this bug disappears. Does that mean that Windows is the source of the problem here?

I eventually got the Docker setup to work but it has been a few days' worth of testing, so I would be curious to know what you think.
Is there something very basic I have missed in the setup or is this a bug?

I apologize for the naive question, got almost zero coding experience here. I would be very happy If you could give me some pointers here :)

Log.txt Disconnects at 10:36:25 and 10:38:58

[jadebenn]

You definitely shouldn't be using the Darkflame client. That was a bit before my time, but it's not supported anymore. I presume this is happening with the vanilla client as well? When you set up the server and configured the resource directory, you made sure that it was pointing at a vanilla one, correct? I want to make sure this isn't some issue where the server is looking for a resource it can't find.

[DuskViper]

Yes, good point with the client - I figured that out after a while (as the readmes still mention the DF version as a viable option). And yes, the problem is 100% reproducible even with the LU 10.10.64 client + the latest Windows DF server release.

[EmosewaMC]

Can reproduce on main and only on windows. LIkely windows specific issue

[EmosewaMC]

should be fixed on latest. Do you need a release to confirm if its fixed? @DuskViper

[DuskViper]

Hello, thanks for getting back to me and for working on this!

Just got time to test both issues on release 3.2.1 by rebuilding about 70 bots and staying online for ~25mins - can confirm that it's fixed!