Posted June 24, 20169 yr I've been developing a mod with IntelliJ IDEA, and I just tried loading the normal .jar (not the -sources.jar) from build/libs in the MC client outside of my development environment. The client crashes with "net.minecraftforge.fml.common.LoaderException: java.lang.NoSuchFieldError: IRON" So, I imagine I'm just not generating a proper, obfuscated jar. But, a scan through Google hasn't yielded a solution. I've uploaded my crash report and mod jar. Links below. Any suggestions? Crash report Mod jar
June 24, 20169 yr We don't want .jar, we need source (git would be nice). You are probably using some dependency wizardy (I assume that since you have hella lot of other mods, if they are not dependency, please remove them for testing) or @SideOnly/Proxy where you are not supposed to, or some reflection magic. Seriosuly, there are plenty possibilities. 1.7.10 is no longer supported by forge, you are on your own.
June 24, 20169 yr Author Here's both the source jar (129 KB) and the full project (12 MB) (it's not on github yet). I'm not doing anything particularly fancy. I just have the other mods installed because they have some utility stuff that's useful for testing. I only have a hard dependency on Base Metals.
June 28, 20169 yr Author Figured out the problem. I had added "--stacktrace" to my build batch file for debugging. Removing that, so that the line was simply "gradlew build" rather than "gradlew build --stacktrace" let it build the jar correctly.
June 28, 20169 yr That's not how Gradle works but OK... Don't make mods if you don't know Java. Check out my website: http://shadowfacts.net Developer of many mods
June 28, 20169 yr Author Indeed. I just tried my old build batch again without incident. So, I have absolutely no idea why it wasn't working before. Nothing has changed between the build that crashed and the successful builds that followed. Not a single line of code was changed anywhere, and I used the exact same MC instance, unmodified from the last attempt.
July 5, 20169 yr Author I've confirmed that simply running the client in IntelliJ IDEA using the runClient task changes the jar such that it crashes the proper client. This is because the runClient task also rebuilds the mod, although not in the same way, apparently. So, after testing in the IDE, I have to build again to get a fresh release jar. Incidentally, my mod is now on github.
July 5, 20169 yr I've confirmed that simply running the client in IntelliJ IDEA using the runClient task changes the jar such that it crashes the proper client. So, after testing in the IDE, I have to build again to get a fresh release jar. Incidentally, my mod is now on github. jus browsing through the mod seeing what you did, why in the lang file you have item.turtletech:turret_extender.name=Turret Extender twice? its not that importent but i was wondering.. Doing stuff n' things
July 5, 20169 yr Author Edit: actually, the first was the item. The second was the tile. Just a copy/paste fail from when I added a new block. Thanks for pointing it out. Replaced the second one with a tooltip.
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.