Corrupted multiplayer campaign ? (all items on station's floor)

[Matse [FR]]

I've been hosting a campagin for my friends for several sessions but tonight after completing a wreck recovery mission when we docked to the Dank station everything went south

Three of us ended up inside the station with all our items removed (everything including clothes, badges etc) and scattered on the ground. The fourth player became a spectator instead.

The items were duplicated several times : I had other players badges in my inventory but thos players had their badges too.

Then we discovered some weird bugs : impossible to repair anything, if I try to repair something I can take damage from it, but if I don't take damage the progress bar doesn't move.

Some doors seem to have a kind of invisible force field around them : moving through them results in weird stuff...

We tried quitting the game and reloading it after recovering all our items and we ended up in the same state : one as a spectator, the others with all items on the station's floor

We then tried starting a new mission in the hope it would restore things to a normal state but no luck.

I guess we will have to start a new campaign now... I'm not sure I want to do that if there's a chance that the game gets messed up again though :/ Kinda frustrating, we were like 12+ hours in the campaign and now it's unplayable

EDIT : list of topics that relates to this bug :
https://steamcommunity.com/app/602960/discussions/1/5367692919518152477/
https://steamcommunity.com/app/602960/discussions/1/5367692919513742262/
https://steamcommunity.com/app/602960/discussions/0/5367692919521926052/

[Rost]

Just stumbled upon the exact same issue. Very frustrating and it happened seemingly out of nowhere.

[Matse [FR]]

Sorry it happened to you, was it in multiplayer too ? I wonder if the devs would be interested in getting our save files or something to investigate.

[Fonkin]

Yeah the same thing just happened to me, I was playing with someone else and when we finished a round suddenly all of the crew but me disappeared with their items on the floor. One other thing that seemed weird was that the logbook that we were returning was on the floor with the rest of the items (normally it should despawn), and the only potential cause I can think of was ending the round with the logbook in my toolbelt? Sorry the same thing happened to you, it's a shame to lose a save like this.

[Matse [FR]]

Thanks for replying, it seems quite a few players got this bug, on a positive note it should help getting it fixed quickly.

I think you're right about the logbook : I've been reading posts on this forum and from what I gathered the bug seems to be triggered either by a logbook (I remember something about too many characters in it or something) or a faraday artifact (I have no idea what it is but it seemed to be confirmed by a few players).

When the bug happened for us we had at least one logbook, back from a wreck salvage mission. We picked up every item on the floor and I don't remember seeing a logbook among those but we had tons of stuff from the wreck so maybe we just didn't notice, or maybe it was in one of our belts.

There may be a way to recover our saved games if the issue is only with a specific item : it should be possible to edit the save file and remove the item, maybe I'll try that if I get some time to spend on this. And if it's lost then it's no biggie... the annoying part is knowing that bug could happen again on a new game, so we just stopped playing barotrauma for the time being.

[Fonkin]

I've managed to find a solution! The corrupted data seems to be caused by a certain logbook entry having too many characters, so if you had it on your character's inventory (which I did) you can go into the character data for the save file and just delete the item from the inventory (logbooks are labelled as "handheldterminal" in the code, and you need to delete everything up to the </item>), and everything works fine. If the logbook was in the ship, it should be in the .save file, which is .gz file so you need to extract the .xml from it and edit that, then turn it back into a .gz, then rename back to .save. Not sure what the solution for the faraday artifact problem would be but maybe deleting that from the save in the same way would work. Seems like an easy fix for the devs, they can just remove the problematic entry. Hope this works for others.

[Matse [FR]]

Thank you for your detailed reply, much appreciated ! I can't test this right now but it all makes sense so I'll take your post as the solution for others to see