ERR NCSimple_Serializer (ch=0):

I've found a fix to broken profile. Create new local game, enter world and exit. Copy your broken profile from server to local game. Start game, wait until profile get fixed. Copy it back to server.

Profile is broken the moment it gets over 2MB, 2049kb you will get an error. A healthy profile after 30 hours of real time, is around 20kb.
Can you PLEASE details what files you exactly copied and where, thank.

 
Can you PLEASE details what files you exactly copied and where, thank.


If what they are suggesting is that being the host of the game fixes the data backup, then you would only be able to fix your personal file as each player profile is linked to their steam account.

Basically if you take your save file from the online saves folder and place it in username/Appdata/roaming/7daysToDie/saves folder (Save file is named something like Nafade County, or Navezgane or could be a custom name) and then launch 7daystodie and hit continue game. The game should be in the game list if done correctly. If a red popup happens that says its missing the data file used when making the world you need to get that from the server also. It will be in data/worlds folder. That goes in /Appdata/roaming/7daysToDie/GeneratedWorlds. If done correctly the game should load up the same character/world from the online game with all the stats and everything.

NOTE: I don't know if this fixes it, as I haven't had to do that, but that's how you would load your online game locally. I hope it helps

 
I've been running into this error since the last update and just today it occurred for another friend on my server too.  It seems to have something to do with the drones, seems "jd clear" command may fix it or temporarily fix it.  When I first was seeing the error I relogged several times but the error came back after 5-10 seconds of logging back in.  Saw someone on the forums posted to run "jd clear" very soon after relogging to fix, so I tried it and the error went away, although I lost my drone.  I didn't use a drone for a few days after, but today I decided to give it a try.  In a matter of 5-10 seconds after deploying the drone the error came back.  I relogged, ran "jd clear" and pulled the drone into my inventory and am no longer using drones and haven't seen the error since.  My friend did the same, and the error seemed to go away for him as well (although he quit for the night shortly after this occurred so maybe not a great example).

Anyone know if the developers know of this issue and/or plan to release a hotfix or something, I miss my drone already :(

 
We are being hammered by this error as well on our Dedicated Server. How long does it take to fix it? Should not be rocket science.

 
If you want to play your game please go back to a20.3b6 or go forward to a20.5b2 EXP aka 'latest_expiremental' this is no longer a legit issue as there are fixes.

@Rolandcan you lock this thread?

 
Last edited by a moderator:
hah... rolling back, and probably breaking your world, or opting into exp beta and probably breaking your world, are not fixes.

 
hah... rolling back, and probably breaking your world, or opting into exp beta and probably breaking your world, are not fixes.
It will do neither of these things if they are playing modless. With mods however Rolling back will have some red text but it can be ignored and only shows once and a20.5b2 EXP will probably have errors even I am unaware of. (I have not thoroughly tested with using older saves and opting into a20.5b2 EXP. I know better than to challenge fate. A smart pack owner can just back up structures as prefabs and other than actual loot you can use commands to go right back to point you are not saying it is not a pain but it is in fact the only real fix.) 

After thorough testing though I can safely say anything relying on Spherii Core will fail when upgrading to a20.5b2 EXP - I already wrote an issue and I am sure that Spherii wil fix it. (This includes lock picking and npc core.)

 
Last edited by a moderator:
Back
Top