Bug/Issue A Very annoying issue with starbound teleporters

There is a topic about restoring data: http://community.playstarbound.com/threads/fixing-lost-corrupted-universes-and-player-files.119985/

~ Iris ~

 

Bookmarks are bookmarks regardless of teleporter or ship nav. Bookmarks are tied to the universe uid. I wouldn't have linked it if it wouldn't work.

~ Iris ~

 

Did you even read it?

~ Iris ~

 

Okay, here's a quick, but complete writeup on how to fix your player.dat file if the universe has become corrupt. (Just expanding the explanations provided by Trinosaur and Iris Blanche.)

To fix a player.dat file, you have to be able to run programs from the command line, understand directory structures, and use a text editor.

Recovering Teleporter Locations After a Universe has Become Corrupted:​

Step 1: Understanding the problem.

The way Starbound saves progress is very, very fragile. If something interrupts it, like a PC crash or power outage, it might lose data. If the universe data is lost this way, it will throw away the old data and create a new file for the universe, losing important information. This new universe will have a new "UUID," a number that uniquely identifies the universe. All of the planet data is still there, though, so the universe can mostly be fixed.

If your player file is intact, but a universe that you play in has been re-generated, then your player file will have all of its bookmarks (flags and teleporters) associated with the UUID for the old universe. When you log into the new universe, the UUID has changed and the bookmarks in your player file won't match the new universe UUID, so you will see no stored teleporter locations.

Step 2: Make a backup.

Back up the entire contents of the storage/ directory under Starbound, so you can replace anything you accidentally break.

Step 3: Fixing the problem.

Using tools provided with Starbound, you can unpack your .player file from its binary format into a human-friendly text format called JSON. Then, using a text editor, you can find where the UUID for the bookmarks is stored, and update it to the UUID for the

Dumping Files to JSON:

In the win32 directory under Starbound is dump_versioned_json.exe. (It'll probably be in a different directory if you're not using Windows.)

You'll need to run dump_versioned_json.exe from the command line. It takes two arguments: the first is a binary .dat file to dump, and the second is the file name to write.

You should export both the .dat file for the universe, and for the .player file to fix. Here's how it might look. (The filename for the player will be different. Steam purchasers, for example, will have different directories.)

Code:

D:\Games\GOG Games\Starbound\win32>dump_versioned_json.exe "D:\Games\GOG Games\Starbound\storage\universe\universe.dat" "D:\Games\GOG Games\Starbound\universe.json"
D:\Games\GOG Games\Starbound\win32>dump_versioned_json.exe "D:\Games\GOG Games\Starbound\storage\player\9ca17817bd04c5b382b28ebd162c7ccd.player" "D:\Games\GOG Games\Starbound\player.json"

Fixing the UUID :

Open both .json files you just created with a text editor.

In the universe.json file, you'll see a line like:

Code:

    "uuid" : "8f4a5ef782f9e679221d032067bbbac2",

What you want is the 32 character value inside the quotes. That's the new UUID for the universe.

Search the player.json file for the word "bookmarks". You'll find at least one line like this:

Code:

    "bookmarks" : [["d1f02b748cf6537014abbd0eabc4284f", [{

I think if that player has played on different servers, you might have a few lines like it. Right after that line will be a bunch of entries with teleport locations. You should recognize one group of them as the ones you've lost.

See how the two 32 character values are different from the player and universe files? That's why the game can't display your teleport locations correctly. The UUIDs are different.

Fix the problem by copying the UUID from the universe file into the value in the player file.

Turn the player JSON file back into a binary:

There is another tool: make_versioned_json.exe to turn your fixed JSON file back into a .player file.

Use it just like the dump tool, but with the .json file as the first argument, and the .player file as the second.

Code:

D:\Games\GOG Games\Starbound\win32>dump_versioned_json.exe "D:\Games\GOG Games\Starbound\player.json" "D:\Games\GOG Games\Starbound\storage\player\9ca17817bd04c5b382b28ebd162c7ccd.player" 

Step 4: Test it out!

If this was done correctly, when you restart the game and start playing with that player and universe, your teleport locations should be recovered!

If it didn't work, the best thing to do would be to restore the contents of your storage/ directory from the backup you made earlier and try again. If it gets frustrating, sit down with someone else and walk through the procedure together to try and figure out what might have gone wrong.

<- there stands everything(!) about recovering the universe data and restoring the bookmarks

~ Iris ~