#To Continue This Game: access the pre-vehicles build 38.3 via the steam betas tab

1 messages · Page 1 of 1 (latest)

mighty mesa
#

I'm hosting a small modded server for 5 or so players. We've run into this issue everytime I've tried hosting about 3weeks IRL time and about 3 months in game. It's set to backup every 15 minutes and on start. Looking for any help

#

More info, my PC crashed and I was unable to safely close the server/game on this instance. Every other time has been a safe launch and shutdown. I would like to avoid doing the map_ver.bin fix as that caused everything to reset except in the immediate area of the host.

limpid sentinel
#

@spice birch

#

<@&756556556488933526>

#

@limpid cipher

limpid cipher
#

You're using pre-vehicles 38.3?

mighty mesa
#

41.78 I believe

limpid cipher
#

...then I'm confused by the channel title. but anyway:

mighty mesa
#

It's the error code

limpid cipher
#

Did this start with the hotfix a day or two ago that updated 41.78 but did NOT change the version number?

#

And does the servername or save name have two dots in it?

mighty mesa
mighty mesa
limpid cipher
#

looking at the java, that error comes from a check on map_t.bin

#

actually that's not quite right

mighty mesa
#

I have a debuglog I can share with you

limpid cipher
#

But it's teh closest I have, and my decompiled java is from the original41.78 not the updated updated 41.78

#

probably just the error and a few lines above it for context

#

But, the short answer is I think one of the files in the save is corrupted and now the game reads to to try and figure out the save version, can't make sens of it, and defaults to that error. I'd guess it's map_t.bin, but I don't know if that is something you can copy from another save or not.

#

Do you have backups of the save?

mighty mesa
#

I do, it backsup every 15 min and on start

#

They're compressed files tho

limpid cipher
#

Without a better plan, backup what you have now and try replacing the map_t.bin file from a known-good backup. If that is no good, roll back teh whoel thing to a known-good backup

finite path
#

the prblem is that your save got corrupt

#

you need to restore one of the backups

mighty mesa
limpid cipher
#

This is how you died.

#

(or the make new game/copy map_t.bin might work... but probabvly this is how you died)