Jump to content

Recommended Posts

Posted

Hi, i'm rather new to modding and I'm trying to load an item texture but no matter what I try it won't load. I've double checked directery naming, they are as follows:

assets\test\textures\items\TestItem.png    and    assets\test\models\item\TestItem.json

my mod id is "test" and the item name is "TestItem"

 

The json file is as follows:

{

 

    {

    "parent": "builtin/generated",

    "textures": {

        "layer0": "test:items/TestItem"

    },

    "display": {

        "thirdperson": {

            "rotation": [ -90, 0, 0 ],

            "translation": [ 0, 1, -3 ],

            "scale": [ 0.55, 0.55, 0.55 ]

        },

        "firstperson": {

            "rotation": [ 0, -135, 25 ],

            "translation": [ 0, 4, 2 ],

            "scale": [ 1.7, 1.7, 1.7 ]

        }

    }

}

 

The only thing I could find when Troubleshooting was the console said:

[22:27:42] [Client thread/ERROR] [FML]: Exception loading model test:item/TestItem with loader instance, skipping

com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Expected name at line 3 column 5

 

My forge version is 1.8.9-11.15.1.1902 if that helps.

If any more information is needed please let me know and i'll provide it.

 

again i'm rather new to modding so if its a stupid mistake I apologize in advance,

thanks!

 

 

 

Posted

ok first off thanks for replying,

I removed the first and last curly brackets but the texture still does not load and the log now said:

Exception loading model test:item/TestItem with loader instance, skipping

com.google.gson.JsonSyntaxException: java.io.EOFException: End of input at line 17 column 6

Posted

add the following method to your item class:

 

@SideOnly(Side.CLIENT)
public void initModel() {
	ModelLoader.setCustomModelResourceLocation(this, 0, new ModelResourceLocation(this.getRegistryName(), "inventory"));
}

 

then in preinit after you have registered the item call the initModel() method...it seems that the JSON is finding the texture ok since there are no errors, so this is the only thing I can think of..make sure when you call GameRegistry.registerItem(), that it has the same name (not class name, but registered name) of the texture..I never really modded for 1.8, but I think 1.8.9 has this functionality..at any rate, you really should just move up to 1.9.4 as it is general consensus that 1.9.4 will be the defacto version for a while

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 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)

×
×
  • Create New...

Important Information

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