Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

"Errors in currently selected datapacks prevented the world from loading." when updating world from 1.16.5 to 1.18.2

Starvixen64

By Starvixen64
in Support & Bug Reports

 Share

Recommended Posts

Starvixen64 Tree Puncher

Starvixen64

Posted
Posted (edited)

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

Edited by Starvixen64
hyperlinks
warjort Reality Controller

warjort

Posted
Posted 
[18Aug2022 01:12:41.158] [Render thread/ERROR] [net.minecraft.world.level.storage.LevelStorageSource/]: Exception reading C:\Users\Princess\AppData\Roaming\.minecraft\saves\16_5 Creative (Azimuth) NonBOP-copy\level.dat
java.lang.IllegalStateException: Unable load old custom worlds.
	at net.minecraft.util.datafix.fixes.WorldGenSettingsDisallowOldCustomWorldsFix.m_185165_(WorldGenSettingsDisallowOldCustomWorldsFix.java:25) ~[client-1.18.2-20220404.173914-srg.jar%2374!/:?]

Your world uses the old custom world format that minecraft no longer supports in 1.18

  • Like 1

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Starvixen64 Tree Puncher

Starvixen64

Posted
  • Author
Posted
9 hours ago, warjort said: 
[18Aug2022 01:12:41.158] [Render thread/ERROR] [net.minecraft.world.level.storage.LevelStorageSource/]: Exception reading C:\Users\Princess\AppData\Roaming\.minecraft\saves\16_5 Creative (Azimuth) NonBOP-copy\level.dat
java.lang.IllegalStateException: Unable load old custom worlds.
	at net.minecraft.util.datafix.fixes.WorldGenSettingsDisallowOldCustomWorldsFix.m_185165_(WorldGenSettingsDisallowOldCustomWorldsFix.java:25) ~[client-1.18.2-20220404.173914-srg.jar%2374!/:?]

Your world uses the old custom world format that minecraft no longer supports in 1.18

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?

warjort Reality Controller

warjort

Posted
Posted (edited)

Mojang didn't provide a way to do that. Presumably because it is a lot of work to do it.

 

This reddit thread discusses how to do it manually by editing the json, but it requires a lot of technical knowledge on the old custom world format and the new world format:

https://www.reddit.com/r/minecraft_configs/comments/hz4ti7/is_it_technically_possible_to_convert_an_old/

But this has a number of problems, e.g.

* Since that thread is 2 years old, the information on that thread will be out-of-date. 1.18 had major changes to world gen storage, hence your problem.

* It assumes a vanilla world, while you said you had Biomes o Plenty which will have additional world gen config that would needs to be converted

 

BTW: I think even in 1.16 the old custom world format wasn't really properly supported.

Instead it just kept any world chunks that you had already created and generated normal (non-custom) chunks for new ones?

Edited by warjort

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Luis_ST Reality Controller

Luis_ST

Posted
Posted
45 minutes ago, warjort said:

Mojang didn't provide a way to do that. Presumably because it is a lot of work to do it.

If i remember correctly vanilla World can be updated without problems, only modded Worlds will get corrupted.

warjort Reality Controller

warjort

Posted
Posted
7 minutes ago, Luis_ST said:

If i remember correctly vanilla World can be updated without problems, only modded Worlds will get corrupted.

No, this is the old buffet worlds or its precursor.

Mojang added a specific check to DFU (DataFixerUpper) that stops these worlds from being updated in the 1.18 snapshots.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Starvixen64 Tree Puncher

Starvixen64

Posted
  • Author
Posted (edited)
10 hours ago, warjort said:

No, this is the old buffet worlds or its precursor.

Mojang added a specific check to DFU (DataFixerUpper) that stops these worlds from being updated in the 1.18 snapshots.

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.

Edited by Starvixen64
eddity edit
warjort Reality Controller

warjort

Posted
Posted

The thing that DFU actually checks for is a "generator" without a "type".

https://minecraft.fandom.com/wiki/Custom#Generator_types

 

 

 

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

warjort Reality Controller

warjort

Posted
Posted (edited)

Actually, I think I misread the code. This stuff can be quite difficult to read. 🙂

I think it is looking for a dimension without a type?

It is definitely looking for something within the world generation settings/dimensions that is missing a type.

Edited by warjort

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Starvixen64 Tree Puncher

Starvixen64

Posted
  • Author
Posted
36 minutes ago, warjort said:

Actually, I think I misread the code. This stuff can be quite difficult to read. 🙂

I think it is looking for a dimension without a type?

It is definitely looking for something within the world generation settings/dimensions that is missing a type.

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! ❤️

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

Announcements



  • Recently Browsing

    • No registered users viewing this page.

  • Posts

    • andreygagloev
      REVIEW OF THE BEST BITCOIN RECOVERY TEAM - MUYERN TRUST HACKER

      By andreygagloev · Posted

      When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • Ugdhar
      corail tombstone fire crash

      By Ugdhar · Posted

      You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • belzabel
      corail tombstone fire crash

      By belzabel · Posted

      So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • elyon44
      Forge 1.12 doesn't download a file

      By elyon44 · Posted

      Okay. Thank you anyway
    • TileEntity
      Forge 1.12 doesn't download a file

      By TileEntity · Posted

      It is 1.12.2 - I have no idea if there is a 1.12 pack

  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept