Jump to content

1.15.2 Mod Loads over and over again after Finishing Forge


Link__95

Recommended Posts

Hello

I started making a Mod for Minecraft 1.15.2,

i havent run into errors jet but minecraft just loads over and over again everytime minecraft is done you can see "Mojang" and the outfading then it loads again from the end of the forge load

 

Since there is no crash i dont have a real log just the start up in my consol that gets like round 3000 lines in a minute so its too much to copy

 

Can anyone help me please?

I made a GitRepo so you can see my code

 

 

 

GitHub https://github.com/Link1995/MinerLifeMod

Link to comment
Share on other sites

Hi

Due to a bug in Forge, when there is an error loading client resources, it cycles infinitely

Examples of cases where this happens:

  • A mod resource failed loading, such as a particle texture list
  • A registry entry is registered twice, causing an exception
  • java.util.concurrent.CompletionException: java.lang.RuntimeException: One of more entry values did not copy to the correct id. Check log for details!
  • An uncaught exception shows up when a mod is loading a custom resource

 

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

 

-TGG

Link to comment
Share on other sites

2 hours ago, poopoodice said:

 


One of more entry values did not copy to the correct id

 Registry Item: Override did not have an associated owner object. Name: minerslifemod:obsidian_bricks Value: air

Try check the registry names

i checked them and cant find a solution (but i found somthing else i forgot :/ but that didnt fixed it either)

i think messed somthing up and just dont see it..

 

i checked

  • the .json files in the blockstates, block and item
  • the names i used the ModBlock and ModItem registry so they match
  • the path for the textures in the .json's for the block and the block item
  • the en_us.json
Link to comment
Share on other sites

Your assets folder needs to be assets/MODID

you have assets/mlm

but your modid is minerslifemod

 

*edit: make sure when you make changes, to push updated code, as well as post updated logs.

Edited by Ugdhar
Link to comment
Share on other sites

15 minutes ago, Ugdhar said:

I'm not sure, but you make your blockitem (in ModItems) an Item, and not a BlockItem. Could that be the issue?

please correct me if im wrong but a block have to be an block and an item

 

15 minutes ago, diesieben07 said:

You register an item with registry name "obsidian_bricks" here.

You register a second item with the same registry name here.

Registry names must be unique.

if i only create the block and not the item the game fails to build

Link to comment
Share on other sites

21 minutes ago, diesieben07 said:

You register an item with registry name "obsidian_bricks" here.

You register a second item with the same registry name here.

Registry names must be unique.

entschuldige du kannst deutsch sprechen eventuell ist das Prätiser zum erklären also wenn ich irgendwas erklären soll oder zeigen sag bescheid :)

 

Edited by Link__95
Link to comment
Share on other sites

11 hours ago, Link__95 said:

please correct me if im wrong but a block have to be an block and an item

Yes, (well, they don't HAVE to) but you are creating it twice as diesieben mentioned, once in the items registry event, and then once in your moditems. I was pointing out the one in ModItems you are using new Item() instead of new BlockItem(), but honestly you should probably just remove that one entirely, since you already create your blockitems in a loop in the item registry event.

 

You should take a step back, I notice you have a LOT of code for having a broken block, which leads me to believe you've been doing a lot of copy & pasting. If you must copy & paste, only do small pieces of code at a time, to make sure they work, and to attempt to understand them as much as possible before moving on.

Edited by Ugdhar
Link to comment
Share on other sites

2 hours ago, Ugdhar said:

Yes, (well, they don't HAVE to) but you are creating it twice as diesieben mentioned, once in the items registry event, and then once in your moditems. I was pointing out the one in ModItems you are using new Item() instead of new BlockItem(), but honestly you should probably just remove that one entirely, since you already create your blockitems in a loop in the item registry event.

 

You should take a step back, I notice you have a LOT of code for having a broken block, which leads me to believe you've been doing a lot of copy & pasting. If you must copy & paste, only do small pieces of code at a time, to make sure they work, and to attempt to understand them as much as possible before moving on.

you're totaly right. the last time i made a mod was in 1.12.2 and it feels like everything has changed maybe i should start again from scratch :/

im sorry for bothering you guys

thank you for your time

Link to comment
Share on other sites

1 minute ago, Link__95 said:

the last time i made a mod was in 1.12.2 and it feels like everything has changed

Yeah, a lot has indeed changed! Here's a link with some of the stuff that changed, it's been quite helpful for me:

https://gist.github.com/williewillus/353c872bcf1a6ace9921189f6100d09a

 

it also has links to other resources for things that changed/1.15 changes.

 

Good luck! **And don't feel bad about "bothering" people here, that's what the forums are for. There's no shame in not knowing something :D as long as you're asking the right questions/accepting advice where applicable, providing requested information, things like that, you're all good

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

    • They were already updated, and just to double check I even did a cleanup and fresh update from that same page. I'm quite sure drivers are not the problem here. 
    • i tried downloading the drivers but it says no AMD graphics hardware has been detected    
    • Update your AMD/ATI drivers - get the drivers from their website - do not update via system  
    • As the title says i keep on crashing on forge 1.20.1 even without any mods downloaded, i have the latest drivers (nvidia) and vanilla minecraft works perfectly fine for me logs: https://pastebin.com/5UR01yG9
    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
  • Topics

×
×
  • Create New...

Important Information

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