Jump to content

Recommended Posts

Posted

So I've been trying to tackle this for a couple days now without success. I'm trying to add a torch into minecraft, the model is correct and it even works with the block states, but i can't get my texture to render. All i get is the pink and black texture.

 

 

My mod can be found here https://github.com/werl/more_torches.

 

 

Thanks in advanced.

Posted

Please update your BlocksInit class.

Your client-proxy calls BlocksInit#registerBlockRenderer, which in your repo atm, doesn't exist.

 

Does your block not have any texture at all, or only when actually, placed, or only when in your hand?

 

You must also call your proxy's registerRenderer in preInit not postInit, if your renderer uses ModelLoader, which I hope that you are using instead of the vanilla Minecraft#getMinecraft way.

Also previously known as eAndPi.

"Pi, is there a station coming up where we can board your train of thought?" -Kronnn

Published Mods: Underworld

Handy links: Vic_'s Forge events Own WIP Tutorials.

Posted

Thanks for your reply and sorry for taking so long to reply.

 

There is no texture at all, it is actually using the models from vanilla minecraft I believe currently. I've been looking into ModelLoader but have been running into some issues. I'm not exactly sure how to use it.

 

 

ModelLoader.setCustomStateMapper(boneTorch, new StateMap.Builder().build());

 

 

That is how I'm currently using it, but it still seems to not be working.

Posted

Once again: Your GitHub repo is frankenstein'd. It shows classes calling methods that don't exist anywhere, so I have absolutely no clue on how your BlocksInit.registerRenderer looks fully.

 

ModelLoader rendering has to be initialized in preInit. You are doing your registration in postInit, way too late.

 

Haven't touched the ModelLoader#setCustomStateMapper at all, so cannot help you much there sadly, but do switch your call to proxy#registerRenderer from postInit to preInit. If anything, that should solve at least one issue here.

 

Also previously known as eAndPi.

"Pi, is there a station coming up where we can board your train of thought?" -Kronnn

Published Mods: Underworld

Handy links: Vic_'s Forge events Own WIP Tutorials.

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

  • Who's Online (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

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