[BUG][Server][2.15.1] Server Config Updater making server not joinable when starting creating a new world

[TigerWalts]

Technical Specs (please complete the following information):

• Craft to Exile Version 2.15.1
• World Type multiplayer
• RAM Allocation 6GB

Describe the bug When starting a server with a new world the server is not joinable until you restart the server. Players get the message:

Internal Exception: io.netty.handler.codec.decoderexception: java.langindexoutofboundsexception: index: 27, Size: 5

Restarting the server stops the error happening.

I have tracked the problem down to it being caused by a Server Config Updater when its server config file <world>/serverconfig/serverconfigupdater-server.toml has not yet been created.

To Reproduce Steps to reproduce the behavior:

1. Start a server with a new world
2. Try to join the server
   • Unable to connect
3. Restart the server
4. Try to join the server
   • Able to connect
5. Stop the server and remove the config file <world>/serverconfig/serverconfigupdater-server.toml
6. Start the server
7. Try to join the server
   • Able to connect again

Expected behavior Being able to join the server on the first start

Additional Information (screen shots, etc.) Related Issue:

• https://github.com/mahjerion/Craft-to-Exile-Dissonance/issues/350

Edits Server Config Updater identified as the cause

[TigerWalts]

Removing the <world>/serverconfig/serverconfigupdater-server.toml will lead to the server being un joinable on the next server start.

Disabling Server Config Updater and all the configs in <world>/serverconfig allows players to join on the next start.

This means that Server Config Updater is not working as intended when there isn't a <world>/serverconfig/serverconfigupdater-server.toml file created yet.

As a workaround I tried adding a defaultconfigs/serverconfigupdater-server.toml with the content:

#Version this world is on. This value gets updated automatically!
#Range: > 0
version = 0

This didn't work. I also tried setting the version to 1 in case the config wasn't validating.

---

This is clearly a bug with Server Config Updater. I can't see any other workarounds.

[mahjerion]

Weird, not sure why you're running into this. Haven't seen it yet. Best to report it to the mod author if you haven't already.