Issue in Dev Environment
Beanxxbot opened this issue ยท 9 comments
Hi!
It's very possible I'm derping up here really bad and am totally missing something, but I didn't notice a deobf or dev version of mekanism to put in my dev environment. Other research has shown me that it's supposed to just work no matter what in my eclipse/mods folder (I'm using InteliJ IDE), however it's not. This is the crash it gives me: http://pastebin.com/D3nFV6TN which I'm having trouble comprehending. The only other mods I have in there are Botania and Baubles, both are deobf as well as the dev versions of both CodeChikenLib and ForgeMultiPart. Let me know if I'm being stupid! I'm using Mekanism 8.1.2.229
I have mdk, the issue is when I start up my game instance from inside my dev environment, it crashes because it's not a deobf mod
Mekanism{8.1.2} Mekanism Unloaded->Constructed
MekanismGenerators{8.1.2} MekanismGenerators Unloaded->Constructed
MekanismTools{8.1.2} MekanismTools Unloaded->Constructed
That was from your crash report... Use the MDK which afaik doesn't include the jars and is an API base.
Also, from the download page:
Note: MDK (Mekanism Development Kit) is intended for use by developers and should not be used alongside the other modules.
Wait, how am I supposed to test this unless I don't have the three mekanism mods inside my eclipse/mods folder. I have the API in my dev environment, but the actual mekanism items and blocks aren't in my game.
If you're making an add-on to mekanism, you don't need them to be there. You code API references around the mdk iirc. @aidan, can you shed some light on this please?
@aidancbrady * above was mistype