Weird brick save mess-up

[paulguy]

A week ago I made a save and it seemed to have no problems, but loading it back up resulted in all kinds of broken builds.  Not sure what happened there, but if it happens to anyone else, I wrote a little utility (Sorry, I can't make Windows executables.) that should fix at least default bricks.  It works in python 3.4, probably not 2.7.

Fixer utility: https://github.com/paulguy/minitools/blob/master/fix_bl_save.py
You'll also need: https://github.com/paulguy/minitools/blob/master/BLSFile.py

If you have everything set up, it should just be a drag and drop.

If anyone wants the original screwed up save to see what happened, I can provide it.  I am curious to know how that happened.

[Ad Bot]

[honytawk]

Saves save only what you have seen.
So if builds are far apart from each other, then you have to fly around before you can make an other save.

What exactly does your script do?

[phflack]

i think he's talking about how it somehow messed up writing a brick in the save file, causing anything after to not be loaded

[paulguy]

nah I'm talking about bricks being offset by 0.5 based on type.  No idea what triggered it.

Click for larger images.
Broken:

Fix applied: