Server Crash Unable to boot - UTF - 8 characters

[Mad]

Version

2.0 (b295)

Platform

Windows

Dedicated server
2.0 b(295)
UTF - 8 character error

Logs:
This log is when the issue happened
This log is what happened when booting up

Here is the error when booting

• 2025-06-29T12:57:31 25.530 WRN SpawnPoint Read missing block rIdle����E
• ArgumentException: The output char buffer is too small to contain the decoded characters, encoding 'Unicode (UTF-8)' fallback 'System.Text.DecoderReplacementFallback'.
• Parameter name: chars
• at System.Text.Encoding.ThrowCharsOverflow () [0x00027] in <819cf46d02f74ba4ae2d757a73aa5ae9>:0
• at System.Text.Encoding.ThrowCharsOverflow (System.Text.DecoderNLS decoder, System.Boolean nothingDecoded) [0x00026] in <819cf46d02f74ba4ae2d757a73aa5ae9>:0
• at System.Text.UTF8Encoding.GetChars (System.Byte* bytes, System.Int32 byteCount, System.Char* chars, System.Int32 charCount, System.Text.DecoderNLS baseDecoder) [0x0023c] in <819cf46d02f74ba4ae2d757a73aa5ae9>:0
• at System.Text.DecoderNLS.GetChars (System.Byte* bytes, System.Int32 byteCount, System.Char* chars, System.Int32 charCount, System.Boolean flush) [0x00059] in <819cf46d02f74ba4ae2d757a73aa5ae9>:0
• at System.Text.DecoderNLS.GetChars (System.Byte[] bytes, System.Int32 byteIndex, System.Int32 byteCount, System.Char[] chars, System.Int32 charIndex, System.Boolean flush) [0x000a2] in <819cf46d02f74ba4ae2d757a73aa5ae9>:0
• at System.Text.DecoderNLS.GetChars (System.Byte[] bytes, System.Int32 byteIndex, System.Int32 byteCount, System.Char[] chars, System.Int32 charIndex) [0x00000] in <819cf46d02f74ba4ae2d757a73aa5ae9>:0
• at PooledBinaryReader.ReadString () [0x00069] in <7e35fe482576460c95b0faebd4830b17>:0
• at SleeperVolume+SpawnPoint.Read (System.IO.BinaryReader _br, System.Int32 _version) [0x00051] in <7e35fe482576460c95b0faebd4830b17>:0
• at SleeperVolume.Read (System.IO.BinaryReader _br) [0x0018c] in <7e35fe482576460c95b0faebd4830b17>:0
• at World.ReadSleeperVolumes (System.IO.BinaryReader _br) [0x00021] in <7e35fe482576460c95b0faebd4830b17>:0
• at World+<LoadWorld>d__62.MoveNext () [0x00410] in <7e35fe482576460c95b0faebd4830b17>:0
• at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00026] in <be2cce08ca774b9684099a81093ecac0>:0
  
  I am aware a mod I have can be causing the issue. I am reporting the information I have.
  

 

[Dwight1225]

Hi, there. I met the same issue yesterday. Could you please tell me what the mod which may cause this issue is? My log was like:

2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block Right� 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block estedSleeperIdle� 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block eperIdle2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block eeperIdle� 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block � 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block � 2025-06-29T21:29:53 16.867 WRN SpawnPoint Read missing block 2025-06-29T21:29:53 16.870 EXC ArgumentException: The output char buffer is too small to contain the decoded characters, encoding 'Unicode (UTF-8)' fallback 'System.Text.DecoderReplacementFallback'.Parameter name: chars

 

[Riamus]

Unless there is a clear error occurring at the top of the log file where mods are loaded that shows which mod is having problems, people can't really help you to determine which mod is the problem. You will need to figure that out on your own by removing mods one by one until it stops giving errors (or starting with no mods and adding them one by one). You can save time by removing (or adding) half at a time and then another half and another half until you the problem goes away (when removing) or appears (when adding) so you can get through more mods in each test.

But remember that very few mods will work in 2.0 until they are updated. So you should be starting with zero mods and only adding mods that have been updated for 2.0.

 

[Dwight1225]

Unless there is a clear error occurring at the top of the log file where mods are loaded that shows which mod is having problems, people can't really help you to determine which mod is the problem. You will need to figure that out on your own by removing mods one by one until it stops giving errors (or starting with no mods and adding them one by one). You can save time by removing (or adding) half at a time and then another half and another half until you the problem goes away (when removing) or appears (when adding) so you can get through more mods in each test.

But remember that very few mods will work in 2.0 until they are updated. So you should be starting with zero mods and only adding mods that have been updated for 2.0.

My server can not restart after like 14 days away (in-game time) and got a log just like above. And thanks for your reminder, indeed I have some V1 mods in my Mods. I'll check for them to make sure I don't have outdated mods that may cause saves corrupted or broken. But the fun thing is my mods now do not show any hints that may have bad issues (I watched for dedicated server logs when starting a new save).

 

[Jugginator]

Not a bug. This is a common issue with CSM and isn't an issue when using the vanilla client. Something in the CSM mod is causing this, you should raise the issue with them so they can fix it. When reporting bugs, please wipe all of your mods and make a new save with a pure vanilla setup and see if the issue reproduces; if it does definitely report it and if it doesn't, then you can slowly introduce mods until you get the issue again -- easiest way to see what's breaking it.