a9d9d9djgdj

Alright, thanks to you termin8or I think I've found the solution. Inside the eclipse/mods folder delete all the mods inside their. Put them instead inside the jars folder inside the eclipse workspace and then add to build path. It seems to work fine with me now doing that.

If you use Class.forName("net.minecraft.client.gui.inventory.GuiInventory"); (as long as your mod is a core mod, maybe it'd work otherwise, I never tried) then it resolves that.

So, is there a new ASM infrastructure with the 1.8 update? Because RenderPlayerAPI, PlayerAPI, NEI, and my own mod don't work when it tries to edit the bytecode of classes in the eclipse workspace

Yes, I can provide links if necessary, but PlayerAPI, RenderPlayerAPI, CodeChickenCore, and NEI are all available for 1.8. Also, as a foot note. I can fix the problem (sort of) by calling Class.forName("CLASS_NAME"); which then loads the class and all is good. However, this doesn't fix the problem, more like a hotfix. Also, possibly unrelated. Minecraftforge mistakes CodeChickenCore for being a duplicate mod as seen here. [13:24:33] [Client thread/ERROR] [FML]: Found a duplicate mod CodeChickenCore at [minecraft.jar, minecraft.jar]

Currently in my forge build for 1.8 I have found that every time I try to add a core mod (specifically codechickencore and NEI, though this includes PlayerAPI and RenderPlayerAPI) it will give me the following error. Again, this is for 1.8, I've looked for awhile for an answer and I'm sure it is something obvious, but I'd like a fresh pair of eyes on this. Thank you