["ERR NCSimple_Serializer (ch=0)" & "EXC Memory stream is not expendable"]

22 hours ago, Kuvuplan said:

 

On the dedicated server, with the server off, grab the 3 files for the affected player at %APPDATA%/Roaming/7DaysToDie/Saves/[Map Name]/[Game Name]/Saves

There is a .map, a .ttp, and a .bak of the .ttp file.

Give a copy of those files to the player.  Reading the server logs can give clues on which sets of files go to which player.  Also, the .ttp file has the username string in there somewhere if you open it as a text file and know what username(s) to search for.

 

Note:  The player profile saves use the same path on the server and client PC's.

 

That player creates a new single player game, preferably with the same map.  Our player that succeeded used a map they downloaded (Which was different from the server's custom map).  The one that failed was using Navezgane.

After that new game is created, quit, overwrite their %APPDATA%/Roaming/7DaysToDie/Saves/[Map Name]/[Game Name]/Saves with the files that came from the server.

Then re-launch the single player game.

While that game is running, it should be obvious that this character is not starting from scratch.  Inventory should have some stuff.

Quit that game.

They then grab those files and send them back to the server.

The server overwrites it's copy of %APPDATA%/Roaming/7DaysToDie/Saves/[Map Name]/[Game Name]/Saves from the ones the player sent.  (Hopefully the server has backups in case something goes wrong/worse)

Server launches, players connect, and should be safe from that issue, long enough at least to put their drones away.

 

Thanks for the assist, that's exactly what I did.

 

For the unaware, the easiest way to get to the appdata folder is to hold the windows key, press R. In the window that pops up type %APPDATA% and click ok. It might put you in the roaming folder, but if it doesn't, just open the roaming folder and then the 7daystodie folder.

["ERR NCSimple_Serializer (ch=0)" & "EXC Memory stream is not expendable"]

I had this issue and found a work around if you're not able to log in. The first time I had the error pop up I was able to log in a couple times but kept getting the error and had to relog. Eventually I was no longer able to log in.

 

I solved this by copying my player profile to a single player world, start the single player game, exit the single player game, copying the player profile back to the dedicated server. There seems to be a limit of 2 mb on player profiles for dedicated servers, and it can't get bigger than that. This limit doesn't seem to exist for single player worlds. Something with the drone is loading up the player profile with info that it shouldn't be. Once you load into a single player world, it cleans the erroring data and brings your player profile down to the size it should be and then you can load it on the server.

 

For now it seems we just need to put the drones in a box until TFP can fix the issue.