Kuvuplan

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.

We have been using a Friends Only server since Alpha 20 was released, and have had Drones following us around since we first encountered them. About 3 in-game days into 20.4, 3 of us got hit with this issue and it was right before a Blood Moon was about to start. We tried server restarts and other debugging steps which ended up not working until we encountered this thread. One of us stayed safe by putting the drone away as soon as we learned that it was a probable cause. Another managed to avoid the issue for awhile by running away from their spawn point after recovering from this crash. Which managed to prevent the Drone from waking up and following them around causing a crash. After the blood moon, they walked over to the drone, which then activated. They emptied it's inventory, put the drone into their inventory, and then got this crash. After a logout and log in, they seemed fine, and had the drone on their belt. Another followed Backslash2099's advise and that resulted in a .ttp that went from a bit over 2,000 KB to 30 KB after using a single player world to sanitize it. There was some strangeness with their inventory, but it seemed to work out. Another followed those same steps, but got error messages about downloading and modifying data, and each time they loaded that profile, they got a level 1 character at a starting point, with a 10 KB .ttp file. We ended up using a backup of their profile from earlier in the day. They lost 3 in-game days worth of progression, but that's better than starting over from scratch. When the issue was hitting us, we couldn't go longer than 30 seconds logged in before the console error would show up, and then be in a private session type thing where the other players would be stationary, and we couldn't interact with world objects. After our various recovery steps and preventions, we managed to finish the Blood Moon (After using some settime commands on the server to delay it a bit while we debugged) and stay connected after the looting and rebuilding afterwards. The 20.3 backup files for all 4 of our player profiles have about 2,000 KB .ttp files. After we shut down the server post blood moon, the one that had a restore, and then shoved the drone into a storage box is at 30 KB. The one with a successful singe-player sanitize is at 62 KB. The one who avoided it by putting a drone in a box before getting the error is at 1,777 KB. The one who ran from the drone, then went back for it is at 2,045 KB with the drone still in their inventory. This one knows to watch out and stash the drone somewhere safe next time we launch the server.

We have Feral Sense on, because it's a new feature and let's try it out. 3 of us were exploring the map on our freshly unlocked bicycles and crossed into the wastelands. It was getting to be evening so we thought we would spend the night at the motel near the outskirts of town, one of the first things we encountered. Vending machines were friendly, though there were a lot of occupants on the site, a few of them were Feral, somebody thought it necessary to use a machine gun to clear it up faster. A couple of us decided to hold out in one of the upstairs rooms, and take pot shots at anything we could see helping the other guy who was still cleaning up the streets. After enough uninvited guests tried to get into our room, we placed a block over the door way. We kept an eye out the window but eventually they stopped knocking and the other guy found a place to hole up as well, I think a neighboring room. Downstairs was a loud party, we were having trouble sleeping in the room, but didn't want to go out there and alert management, I'm sure they could hear the party too. At some point, our floor started glowing green, and then suddenly it was no longer a floor, and one of us ended up crowd surfing in that party for 10 seconds or so before they managed to find some jumps to get back into our room. Some med kits and first aid bandages were applied, as that was not a friendly party to crowd surf on! We decided to make a new door out of the bathroom and we met up with our 3rd person and built a bridge to the adjacent store. Not sure what it was, but it had a roof that was mostly clear. We spent the rest of the evening watching the party in the unit below us, who then filled the alleyway between the motel and the store, and occasionally some would find their way up to our roof. Bouncing between the room and the roof generally kept them occupied and we had no more close calls. When morning arrived, the crowd dispersed and we got on our bikes to head home, feeling weary from the night before. We tried to leave a note for management that our stay was uncomfortable, and the neighbors were really loud and broke fire codes with the number of attendees. Also, the hole in the floor was their fault, not ours. 0 out of 5 stars, do not recommend.