Not to be a jerk but this is part of the tutorial, this shouldn't be an issue, especially when, by doing a little research, this has been an issue since at least early 2.x. You guys added zombies smelling players before fixing a game breaking bug in the tutorial which is just crazy. It really feels like you guys don't care about the new player experience or your players. Especially when I look for answers to this issue and am basically told to just "start a new world". I'm an adult, playing with other adults, we already have a hard time all getting together, so then telling everyone that "ohh the world that we've spent 20hr on, yeah we have to delete that because there's a bug that's been here for years that has soft locked a players progression" isn't a fair or satisfactory answer. A fix in the mean time would have been a force_complete command, but , as I've said before, this has been an issue for at least a year, I know that isn't happening either. I'm dealing with this same issue and it's my first playthrough, it's a great first impression. I've dealt with less jarring and just far less (in quantity) bugs in game that ARE in early access, this game is in full release and has given me my absolute worst "First player experience" I have ever dealt with in a game since Cyberpunk.
Thank your for your feedback, I'm sorry to hear that your first experience with the game resulted in a bug encounter this bad.
The issue you are experiencing sounds like a known issue which usually happens when a player completes a quest from a party members before finishing the Intro quest, and failing the intro quest.
Depending if you play on a server or on peer-to-peer there is a way to reverse this without forcing everyone to restart.
It does require for the player data of the affected person to get reset.
I'd recommend to store your player items in a crate before resetting your data.
Your level, kill count and challenge progression will be lost and needs to be recovered with admin commands.
And before tempering with any world save data a backup from the current world is highly recommended.
Method: Using Server Save Files
1- Stop your dedicated server before making any changes.
2- Navigate to the server’s save directory: Saves/CurrentWorldName/GameName.
3- Open the player folder in that directory.
4- Find the player’s userid by matching their username in players.xml.
5- Go to the Player folder inside the same save directory.
6- Locate all files containing that userid in their filename (usually .map and .ttp files).
7- Delete all files with the matching userid to remove their data.
8- Restart your server and have the player reconnect to generate fresh data.
Method: On a Local/Host Machine (Peer-To-Peer)
1- On the host machine, open the path: %AppData%/7DaysToDie/Saves (resolves to C:\Users\<user>\AppData\Roaming\7DaysToDie\Saves).
2- Open the save folder used by your server.
3- Follow steps 3–7 from the server method above to remove the player’s files.
I hope this helps resolve your issue.
This specific bug will be fixed in future update.
Best,
Revi
