Help And Support

[sibercat]

Having a problem with SoulMask-Server-Manager? Not sure how to use one of the features? Post your questions here.

[Cryshah]

Hi, great job to help manage a server but ...
I can't apply parameters live, in the logs, there are the following commands that appear, and then it stops there, it only applies the first line of modified parameters

logserversupervise: Warning: try run admin command: logserversupervise: sc expratio 4
logserversupervise: display: expratio 4
logserversupervise: error: receiveerror: SE_NO_ERROR
logserversupervise: closing connection remoteconnection

maybe i did something wrong

[sibercat]

Try updating to https://github.com/sibercat/SoulMask-Server-Manager/releases/tag/1.1.1

[Cryshah]

I tried this new version, same issue

deleted everything and re-installed because it didn't detect that the server was running

[Cryshah]

stop server / modify passwords or other settings / start server
it didn't detect that the server was running : "Server 1: Starting..."

tried normal or admin mode

[sibercat]

Can you test this for me: https://s3.dualstack.us-east-1.amazonaws.com/soulmaskservermanager/SoulMaskServerManager.exe

Addressed a different bug.

What was wrong: the server wipes and rewrites its log file every time it
starts. The manager was still reading from a position in the old log, so after
a restart it never saw the "server ready" line and just sat on "Starting..."
until a 15-minute fallback kicked in.

I installed a real server locally and reproduced it end-to-end. Fixed build
attached (v1.1.2).

Please test the restart path specifically:

1. Start the server, wait for "Running"
2. Stop it
3. Change a setting
4. Start it again

What you should see: within about a minute you should get
Server fully loaded and registered. in the Console tab and the status should
flip to Running. On my test box it took 37s cold and 44s after a restart.

You'll also now see Still loading... (30s elapsed) messages while it works —
that's normal. A real server genuinely takes 40s+ to load, and the old build
gave you no feedback during that, which probably made it look frozen even when
it was fine.

One thing to tell me either way: if you ever see
Server is responding on EchoPort — marking as Running., let me know. That's a
backup detection path that should almost never trigger. If it shows up on your
server, the normal detection isn't working for you and I want to know.

If it still hangs: send me
SoulMaskServer\Server 1\ServerFiles\WS\Saved\Logs\WS.log right after it
happens, plus roughly how long you waited.

[Cryshah]

works fine

[20:26:34] [UI] Starting server...
[20:26:34] Starting SoulMask server...
[20:26:34] Args: … … …
[20:26:34] Waiting for server to finish loading (watching WS.log)...
[20:27:04] Still loading... (30s elapsed)
[20:27:35] Still loading... (60s elapsed)
[20:27:37] Server fully loaded and registered.
[20:28:23] [UI] Stopping server...
[20:28:23] Stopping server...
[20:28:23] Sending world save via EchoPort...
[20:28:27] Sending graceful shutdown signal...
[20:28:32] Server stopped.
[20:29:09] [Gameplay] Custom preset 'Chill' saved and written to GameXishu.json. Restart server to apply.
[20:29:25] [UI] Starting server...
[20:29:25] Starting SoulMask server...
[20:29:25] Args: ... ... ...
[20:29:25] Waiting for server to finish loading (watching WS.log)...
[20:29:56] Still loading... (30s elapsed)
[20:30:26] Still loading... (60s elapsed)
[20:30:30] Server fully loaded and registered.

[Cryshah]

1st start 63s
2nd start 65s

[sibercat]

Thank you. Updated