Fortress bounding box issue with Forge 1.8 (11.14.1.1337)

[irtimaled]

Nether fortress bounding boxes in 1.8 vanilla and latest Forge for 1.8 are not the same - the structure data that forge is showing is different than in the fortress.dat file.

 

In this particular example it's a fortress that was generated in 1.6.2, then the world was updated to 1.7.2 so the fortress.dat file contains the 1.7.x bounding boxes and don't line up with the blocks.  In 1.8 Vanilla it shows the correct bounding boxes:-

https://pbs.twimg.com/media/B_-ykjVVEAEX0W4.png[/img]

 

However in Forge 11.14.1.1337 (and several earlier versions) the bounding boxes look like they were generated fresh in 1.8.

https://pbs.twimg.com/media/B_-ykb6VAAARz9e.png[/img]

 

[irtimaled]

I've dug into the Forge source and it looks like the WorldSpecificSaveHandler is trying to load the fortress.dat file from ./saves/world/DIM-1/data rather than ./saves/world/data

 

Since the file wouldn't be there (cos that's not where it's stored) it would be regenerated!

[irtimaled]

Created issue on GitHub repo...

https://github.com/MinecraftForge/MinecraftForge/issues/1747

[LexManos]

This is a issue that's fixed by Forge. Namely the fact that structures are intended to be world specific, so that mods can come along and create custom worlds with the same type of structures.

This has been the case since Nether fortresses were introduced.

So as long as you've loaded the old world in a version of Forge for that MC version it'll work fine.

Without special casing the nether and breaking other worlds, we cant really do anything.

Simple solution if you havent gone through the normal forge update process is just to move your fortresses.dat file.