Jump to content

Errors in currently selected datapack prevent the world from loading


Recommended Posts

Posted (edited)

Hi, I've been playing on a custom modpack for nearly 200 hours now and ran into an error.

spacer.png

Note: This isn't the exact screenshot from my game but this is the exact error message. 

I was attempting to add in a block called magical soil (a part of the allthemods modpack) which said it originated from the kubejs mod. I copy pasted in some files but it never showed up so I replaced the whole kubeJS folder with one from the ATM9 modpack but this created a bunch of errors because of missing mods so I tried restoring the old folder. The game doesn't crash anymore but it gives me this "Errors in currently selected datapacks" message. 

I tried renaming the level.dat_old file to level.dat as some people recommended but this didn't help at all. I noticed some mods were missing but even after adding back in the ones I saw the error persisted.

 

Edit: Pastebin Files

The log files is quite large and I have no idea how to read it, had to cut it into 2 parts:

Crash Log 1

Crash Log 2

When trying to create a new world the game crashes before getting to the screen and gives the exit code -1 and this is the crash log

World Creation Crash

I had the same issue when I was making the pack and I eventually solved it by removing the mods that were conflicting/crashing but I suspect that this wouldn't solve the issue with the already created world. I was thinking that maybe the issue was a mod that accidentally got disabled/removed but I'm not sure.

 

Edited by JoshN
Posted

Please read the FAQ on how to post your logs; embedding them in your post like that makes them very hard to read, which may make it harder for people to help you.

I'd be interested to know if you run into the same problem(s) if you create a fresh world, vs loading into the one you've been playing.

Posted

The log files is quite large and I have no idea how to read it, had to cut it into 2 parts:

Crash log 1

Crash log 2

When trying to create a new world the game crashes before getting to the screen and gives the exit code -1 and this is the crash log

World Creation Crash

I had the same issue when I was making the pack and I eventually solved it by removing the mods that were conflicting/crashing but I suspect that this wouldn't solve the issue with the already created world. I was thinking that maybe the issue was a mod that accidentally got disabled/removed but I'm not sure.

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.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Please read the FAQ (https://forums.minecraftforge.net/topic/125488-rules-and-frequently-asked-questions-faq/) and post log files as described there, using a site such as https://mclo.gs/ and post the link here.  
    • I tried updating the mods in my modpack which caused incompatibilities so i have tried to revert them back to their older versions i was using before. In the logs it doesnt show me any clear incompatibilities except for tfmg & entity texture features, but when i try to remove those it still doesn't work. I have tried removing the forge-client.toml file which was a suggestion i found on  a few other posts. This is the log file i get. [inline log removed] Any help would be appreciated. Thanks in advance
    • I don't use KubeJS, never even heard of it. But after doing what "Ugdhar" suggested earlier in this post with the "config/Mekanism/generator-storage.toml", I tried going into an individual save's serverconfig folder, and just deleting everything except the parcool folder (I have that mod installed.) Then, a bit of loading and temporary freezing later, seems to have worked. Even when quitting to menu and loading back in, or also when quitting to menu, exiting to desktop, and re-launching MC, choose a save and loading it.
    • [Mekanism] Broken tags in Mekanism recipes detected, please check server logs for details. You will be missing some recipes and machines may not accept expected inputs. Do you use KubeJS? It is some kind of bug with it and not fixed A workaround is setting "allowAsyncStreams" to false in the KubeJS common config file https://github.com/KubeJS-Mods/KubeJS/issues/1016   For the rest of your issues, keep deleting these files - now it is the jei-server.toml file If the file is not in config, check the worldsave serverconfig folder These files usually break after updating mods, game crashes or force closing the game    
    • And now to add salt to injury, I keep seing this message in game: [Mekanism] Broken tags in Mekanism recipes detected, please check server logs for details. You will be missing some recipes and machines may not accept expected inputs. What does that mean and how can I fix that too ?
  • Topics

×
×
  • Create New...

Important Information

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