Jump to content

Recommended Posts

Posted

I am starting to experiment with modding for 1.9.4, and I figured out how to register items, but I'm having more trouble with blocks. The game crashes when the method, 'RegisterRenders' from my block init class is called by my client proxy class. I can't figure out what I'm doing wrong, so can someone please help me? Thanks in advance.

 

Crash Report:

 

  Reveal hidden contents

 

 

Block init class:

 

  Reveal hidden contents

 

 

TestBlock (BlockTm) class:

 

  Reveal hidden contents

 

 

ClientProxy class:

 

  Reveal hidden contents

 

 

Mod class:

 

  Reveal hidden contents

 

 

Tell me if you need any more details.

This is my creative and unique signature.

Posted

I tried changing my registerRender method to this, but I'm pretty sure I'm still doing something wrong :/

public static void registerRender (Block block, String resloc) {
Item item = ItemBlock.getItemFromBlock(block);

ModelLoader.setCustomModelResourceLocation(item, 0, new ModelResourceLocation(Reference.MOD_ID + ":" + resloc, "inventory"));
}

 

This is my creative and unique signature.

Posted

You mentioned registering an ItemBlock, and I noticed that both Item and ItemBlock had the method getItemFromBlock, so I tried using ItemBlock instead of Item. It clearly didn't work.

This is my creative and unique signature.

Posted

Okay, I managed to not make it crash by changing my registerRender method to this:

public static void registerRender (Block block, String name) {
ItemModelMesher mesher = Minecraft.getMinecraft().getRenderItem().getItemModelMesher();

mesher.register(Item.getItemFromBlock(block), 0, new ModelResourceLocation(Reference.MOD_ID + ":" + name, "inventory"));
}

However, when I run the game the block doesn't appear as if it wasn't registered.

This is my creative and unique signature.

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

    • "I want to understand how complex mods with ASM transformation and coremods work, such as Xray or AntiXray. Why do they break when you simply rename packages? What features of their architecture make refactoring difficult? And what techniques are used to protect these mods? I am interested in technical aspects in order to better understand the bytecode and Forge loader system."
    • I can't figure out if you're looking for help trying to steal someone elses work, or cheat at the game....
    • Title: Why Is It So Hard to Rename and Restructure Mods Like Xray or AntiXray? 🤔 Post text: Hey everyone! I’ve been digging into Minecraft modding for a while and have one big question that I can’t figure out on my own. Maybe someone with more experience could help or give me some advice. Here’s the issue: When I take a “normal” Minecraft mod — for example, one that just adds some blocks or new items — I can easily change its structure, package names, or even rebrand it entirely. It’s straightforward. But as soon as I try this with cheat-type mods like XrayMod or AntiXray, everything falls apart. Even if I just rename the classes, refactor the packages, or hide its identity somehow, the mod either breaks or stops working properly. XrayMod in particular is proving to be a nightmare to modify without losing its core function. So my question is — why is this so much harder with cheat mods like Xray? Is there something fundamentally different about how they’re coded, loaded, or protected that prevents simple renaming or restructuring? And if so, how can I actually learn to understand someone else’s cheat mod enough to safely refactor it without breaking the core features? I’ve already been spending over two months trying to figure this out and haven’t gotten anywhere. It feels like there must be some trick or knowledge I’m missing. Would really appreciate any thoughts, tips, or references — maybe there are guides or techniques for understanding cheat-mod internals? Or if you’ve successfully “disguised” a cheat mod like Xray before, I’d love to hear how you did it. Thanks in advance for any help or discussion. ✌️
    • just started making cinamatic contect check it out on my channel or check out my facebook page    Humbug City Minecraft Youtube https://www.youtube.com/watch?v=v2N6OveKwno https://www.facebook.com/profile.php?id=61575866982337  
    • Where did you get the schematic? Source/Link? And do use an own modpack or a pre-configured from curseforge? If yes, which one On a later time, I can make some tests on my own - but I need the schematic and the modpack name
  • Topics

×
×
  • Create New...

Important Information

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