Skip to content
This repository has been archived by the owner on May 26, 2018. It is now read-only.

When an error is thrown during the ID remap event, the world gets corrupted #524

Open
skyboy opened this issue Sep 25, 2014 · 6 comments
Open

Comments

@skyboy
Copy link

skyboy commented Sep 25, 2014

Specifically, the error gets swallowed and suppressed, and the level.dat file gets deleted.

  • create a world with multiple mods
  • remove one mod
  • load the world
  • add that mod back
  • load the world
  • change a mod to throw an error during the remap event, change block/item mappings
  • load the world; click "no"

The level.dat file will now be erased, and the backup level.dat file will be used in all future attempts to load the world; having an incorrect ID map

@skyboy
Copy link
Author

skyboy commented Sep 26, 2014

Correction: any successful remap will corrupt the world. The FMLMissingMappingsEvent just doesn't function in any kind of meaningful way.

@skyboy
Copy link
Author

skyboy commented Sep 26, 2014

Okay, there were ItemBlocks that I had removed during the restructure that were not remapping causing the registry to fail its consistency test because the failed items blocked the ID from being used (the ID that the blocks successfully remapped to); FML then reports that the backup level.dat is being used instead of the actual error that occurred.

The title is still correct in that errors that occur here will get swallowed, in addition to being misreported.

@progwml6
Copy link

the original issue was just reproduced in testing w/ some of my mods

@clienthax
Copy link

Still seems to be a issue, (merging one mod into pixelmon)
http://pastebin.ubuntu.com/10706592/

@skyboy
Copy link
Author

skyboy commented Apr 13, 2015

Largely corrected by 12ccf9c.
Unknown if mods throwing errors during the event will cause the same issue. @cpw

@cpw
Copy link
Contributor

cpw commented Apr 13, 2015

It shouldn't, but I'll check.. Probably need to repropogate the error from inside to outside..

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants