Jump to content

Errors in currently selected datapack prevent the world from loading


JoshN

Recommended Posts

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
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

    • Try deliting feur builder  It caused this issue in my modpack
    • I am not using hardcoded recipes, I'm using Vanilla's already existing code for leather armor dying. (via extending and implementing DyeableArmorItem / DyeableLeatherItem respectively) I have actually figured out that it's something to do with registering item colors to the ItemColors instance, but I'm trying to figure out where exactly in my mod's code I would be placing a call to the required event handler. Unfortunately the tutorial is criminally undescriptive. The most I've found is that it has to be done during client initialization. I'm currently trying to do the necessary setup via hijacking the item registry since trying to modify the item classes directly (via using SubscribeEvent in the item's constructor didn't work. Class so far: // mrrp mrow - mcmod item painter v1.0 - catzrule ch package catzadvitems.init; import net.minecraft.client.color.item.ItemColors; import net.minecraft.world.item.Item; import net.minecraftforge.registries.ObjectHolder; import net.minecraftforge.fml.event.lifecycle.FMLClientSetupEvent; import net.minecraftforge.fml.common.Mod; import net.minecraftforge.eventbus.api.SubscribeEvent; import net.minecraftforge.client.event.ColorHandlerEvent; import catzadvitems.item.DyeableWoolArmorItem; @Mod.EventBusSubscriber(bus = Mod.EventBusSubscriber.Bus.MOD) public class Painter { @ObjectHolder("cai:dyeable_wool_chestplate") public static final Item W_CHEST = null; @ObjectHolder("cai:dyeable_wool_leggings") public static final Item W_LEGS = null; @ObjectHolder("cai:dyeable_wool_boots") public static final Item W_SOCKS = null; public Painter() { // left blank, idk if forge throws a fit if constructors are missing, not taking the chance of it happening. } @SubscribeEvent public static void init(FMLClientSetupEvent event) { new Painter(); } @Mod.EventBusSubscriber private static class ForgeBusEvents { @SubscribeEvent public static void registerItemColors(ColorHandlerEvent.Item event) { ItemColors col = event.getItemColors(); col.register(DyeableUnderArmorItem::getItemDyedColor, W_CHEST, W_LEGS, W_SOCKS); //placeholder for other dye-able items here later.. } } } (for those wondering, i couldn't think of a creative wool helmet name)
    • nvm found out it was because i had create h and not f
    • Maybe there's something happening in the 'leather armor + dye' recipe itself that would be updating the held item texture?
    • @SubscribeEvent public static void onRenderPlayer(RenderPlayerEvent.Pre e) { e.setCanceled(true); model.renderToBuffer(e.getPoseStack(), pBuffer, e.getPackedLight(), 0f, 0f, 0f, 0f, 0f); //ToaPlayerRenderer.render(); } Since getting the render method from a separate class is proving to be bit of a brick wall for me (but seems to be the solution in older versions of minecraft/forge) I've decided to try and pursue using the renderToBuffer method directly from the model itself. I've tried this route before but can't figure out what variables to feed it for the vertexConsumer and still can't seem to figure it out; if this is even a path to pursue.  The vanilla model files do not include any form of render methods, and seem to be fully constructed from their layer definitions? Their renderer files seem to take their layers which are used by the render method in the vanilla MobRenderer class. But for modded entities we @Override this function and don't have to feed the method variables because of that? I assume that the render method in the extended renderer takes the layer definitions from the renderer classes which take those from the model files. Or maybe instead of trying to use a render method I should be calling the super from the renderer like   new ToaPlayerRenderer(context, false); Except I'm not sure what I would provide for context? There's a context method in the vanilla EntityRendererProvider class which doesn't look especially helpful. I've been trying something like <e.getEntity(), model<e.getEntity()>> since that generally seems to be what is provided to the renderers for context, but I don't know if it's THE context I'm looking for? Especially since the method being called doesn't want to take this or variations of this.   In short; I feel like I'm super super close but I have to be missing something obvious? Maybe this insane inane ramble post will provide some insight into this puzzle?
  • Topics

×
×
  • Create New...

Important Information

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