Starvixen64

Fascinating - your suggestion and my hunch combined proved to be the solution! I categorically knew that it was not a non-standard world type, so I had a browse through the NBT and just deleted out the compactmachines:compact_world tree data, as it's a remnant of a long-uninstalled (but very cool) mod, that left it's data in the NBT. Then I deleted everything from the "dimensions" folder in %appdata%/.minecraft/ without deleting the folder itself. To my great relief, the world has succesfully loaded in 1.18.2, meaning I don't need to lose my most worked-on world to version incompatibility! I'm not sure what the exact issue was, I just know it pertains to Compact Machines and something to do with how the 1.16.5->1.18.2 update treats it's dimensions. I imagine even after deleting the mod itself, it probably left the dimensions themselves (with machines inside) intact. To anyone encountering this/a similar issue, check if you have non-standard modded dimensions, especially those you don't use anymore. Seems to do the trick. Thanks for the help! ❤️

All my dimensions read "minecraft:noise" for "type" under "generator". Is this not default worldgen behaviour?

Do you know of a way to check within NBT as to how the world was generated? Although I do remember possibly fiddling around with BOP at one point, I'm fairly positive this was never an old custom world; it was generated PAST when those became obsolete. Highly confused as to why this world is bugged out in this way Edit: I've had a browse and the level.dat has a separate dimension from overworld, end, nether under "compactmachines:compact_world". I imagine this is because quite a long time ago I used the Compact Machines mod on this world; could this have something to do with it? I don't have practically any data left from that mod but it seems to linger in the NBT.

That's weird, this wasn't a custom world. I did once (I think) edit it between vanilla and Biomes o Plenty type worlds, but all that block data would've been gone anyway. Is there some way to update the world to work with 1.18?

Recently updated from 1.16.5 to 1.18.2 as I found that all my mods had updated to newer versions, so I could upgrade them without needing to drop any. Weirdly, worlds created in 1.18.2 work fine and splendidly with all mods I'm using, but playing my main world (1.16.5, possibly gen'd in 1.14 but I think 1.16.5) in 1.18.2 just leads to this message. Errors in currently selected datapacks prevented the world from loading. You can either try to load it with only the vanilla data pack ("safe mode") or go back to the title screen to manually fix it What would be causing this? Modlist : https://i.imgur.com/AcKjimg.png (using Forge 1.18.2-40.1.73) debug.log : https://www.textbin.xyz/?51a78db1807352d8#CTwkbgkon74hQCBZ324s4PB8N4dYWXb2fPeVqNKbPH8C