I need help please!

I programmed a mod and all was good until I wanted to build it to a jar file.

So I did gradlew build in cmd and it seemed to have worked - until I popped it into the mods folder in my .minecraft

I concluded that the lang file wasn't working - because everything was like item.AmethystGem.name

One ore texture wasn't working as well - although all the other ones worked - wtf right?

The oregen also didn't appear to be working as i didn't find any ores

 

the modid jar file

http://www.mediafire.com/file/lkmp783ely3i86q/modid-1.0.jar

Don't panic. There are several stages to debugging. After running in Eclipse (or other IDE), you run SP in your local MC (Forge) client. After that, you should try MP between client and dedicated server.

 

At each new stage, things can go wrong there that don't show up earlier. So put on your thinking cap and gather more info. In particular, find the log file (not console output) from your test run. The log will have more warnings than you'll see on the console.

 

The first question is: Did you perfectly match capitalization where it needs to be matched, and did you use all lower case where it must be all lower case? Reason I ask: Running in an IDE in Windows means using a filesystem that is NOT case sensitive. Running a jar in SP means accessing "files" inside a jar that IS case sensitive. Mixed-case errors hidden earlier then appear. The log should show warnings.

 

And again: Don't Panic.

DERP I didn't check the reference file - the one place I didn't check!

The oregen and the missing texture are gone now - but the blocks and items still show up as item.AmethystGem.name or similar, although I have a en_us.lang file, where it says :

item.AmethystGem.name=Amethyst (this is one example)

DERP - again!

I found out that the lang file has to be called en_US.lang instead of en_us.lang!

 

Thank you jeffryfisher for your help as this was the first 'major' issue I came across since starting modding!! ;D