Cadiboo

Try and find your EE installation and kill it with fire. Make sure your JAVA_HOME is set too.

Now that looks like a z-fighting issue. Make sure that your model elements aren't in exactly the same place. Transparency (what you use with CUTOUT) isn't a problem. Translucency (what you use with TRANSLUCENT) is a problem. Your mod looks amazing btw!

You can't AFAIK. I'm pretty sure this is being fixed in 1.14. If you actually need translucent models, you're out of luck, but if you don't you should be able to just use the CUTOUT or CUTOUT_MIPPED render layer.

1) Don't necro a thread thats 7 years old 2) Don't hijack a thread with your own problem. Your problem is different, make your own thread 3) Sorry we don't support 1.2.5 or any version under 1.10 on this forum anymore due to their age. We simply don't know how to help you anymore. You can go to the Minecraft Forum where I think that they still still support older versions, or update to a modern version of Minecraft (the latest version or the one before it) to receive support on this forum.

If you download the mod that Decocraft requires, you won't have this crash anymore. If you remove Decocraft, you also won't have this crash anymore.

The most likely cause of this is that one of your mods requires a Forge version over 2779 in which that method was added. You're using Forge 2772. I recommend that you update Forge. This may not be the cause of your error though.

1. Mods are not compatible in between versions except if the mod is tiny and the updates to the game were tiny. 1.12.2 -> 1.13.2 compat is impossible and there is no way to know about 1.13.2 -> 1.14 as 1.14 isn't out yet. 2. Depends on the mod, the update for one of my mods required changing a few type names, rewriting 2 heavily vanilla dependant classes & updating a library mod to 1.13.2. I took less than 2 days and could have been faster. Massive mods, as usual will probably require some form of rewrite. Badly-written mods/mods with outdated code will also require a rewrite. 3. Yes, and Forge will now support more features

I'm unable to make sub categories with @LangKey in my config. I've tried putting @LangKey on my inner class, my field, the fields inside the inner class. Nothing. I asked on MMD, and was told that someone else had asked, and they didn't think it was possible, but weren't 100% sure. I can include code, but I don't think its necessary in this case. Nothing about localisation or config in my logs. I'm doing this in a dev environment. Obviously this shouldn't affect anything, but I've had weird stuff happen with @Config in a release/dev environment before.

Do you remember where you read this?

Post your log and your code as a working GitHub repository

IIRC you need to call obj loader.add domain earlier. Try putting it in your mods initialiser (inside a proxy of course). Putting it in a static initialiser in your statically subscribed ClientEventSubsciber (or the initialiser of a non static one) should work

@SidedProxy distinguished between physical sides. You seem to want to distinguish between logical sides. Also, any interaction with minecraft objects from a packet thread needs to be done inside of a scheduled task.

I think that Scratch is to programming what crawling is to flying an airplane (or at least to driving a car).

@SubscribeEvent(priority=blah)

This is the reason we don’t support 1.7.10. No one knows how to write mods for this version anymore.

2 subscribe event methods with different priorities. The @SubscribeEvent accepts a priority

If you cancel the event you need to render the player’s model. I suggest having 2 subscribers. 1 in which you render the normal model at Priority=NORMAL, and another that only cancels the event, with priority=LOWEST

You need to properly instantiate your class. Look at your class’s constructor and see what it needs in there

If that’s how you want to implement it. You could also implement it in 1 Block or in a bottom block. I personally would use a top block.

What: Not using a "common" proxy. Why: Proxies exist to seperate side-specific code, if there is code that is common, it should not be in a proxy. Consequences: Issues with physical sides, hard to read code. A "common" proxy goes against fundamental OOP and logical concepts. How: Have an interface (usually called IProxy or Proxy) and have your client and sever proxies implement this class. Your interface should be in a common package (usually util) and your sever and client proxies should be in their respective packages. You can read more at https://gist.github.com/Cadiboo/fbea89dc95ebbdc58d118f5350b7ba93. This is more of a code style thing. I recommend putting your register methods into the appropriate event subscriber.

You may/may not have already read this, but it’s useful - https://gist.github.com/williewillus/353c872bcf1a6ace9921189f6100d09a. You need to fix your error with not being able to see the minecraft library as an attached source before you continue Modding. Everything that mods do is based off vanilla.

To fix the bright pink texture, change “items/shield” to “<modid>:items/shield”. Without the modid, the game will look for that texture in the vanilla textures (a resource location without a domain defaults it’s domain to “minecraft”). To fix the wrong transforms, add your own display tag, or set the models parent to something with default transforms. Common parents are “item/generated” or “item/handheld” (for axes, shovels etc.). Look at vanilla item models for examples

Also

Forge has a discord, an IRC and these forums. Lex also has a Patreon that you can donate to or a bitcoin address if that’s your thing.

You need to know basic Java before you make a mod. Even spending 1-2 hours reading or watching a good tutorial helps immeasurably. Sorry to be blunt with you, but this is an absolute pre-requisite. On the upside you now know one of the causes of this error, and know how to fix it. Usually googling an error you got should get you an decent explanation. This problem deals with such basic Java that no one appears to have asked this question on google (the error is pretty self explanatory to someone with basic Java knowledge), so this advice doesn’t apply in this specific case, but it is good advice in general! Happy Modding!