File coremod = new File(minecraftDir,"coremods");
        for (String cont : injectedContainers)
        {
            ModContainer mc;
            try
            {
                mc = (ModContainer) Class.forName(cont,true,modClassLoader).newInstance();
            }
            catch (Exception e)
            {
                FMLLog.log(Level.SEVERE, e, "A problem occured instantiating the injected mod container %s", cont);
                throw new LoaderException(e);
            }
            mods.add(new InjectedModContainer(mc,coremod));
        }

 

in Loader.identifyMods() the location of the coremod is passed to the mod container, but the folder name specified is "coremods". anybody know if this is just some code that was overlooked in the 1.6 update or if it's intentional?

yep. that's what i'm doing now thanks though!

 

and a heads up to anyone who uses eclipse and grabs the mod location through injectData, it can give you a null location if you use the vm arguments to load your IFMLLoadingPlugin instead of a dummy jar file in the mods folder. (of course, it could just be my eclipse set up that's screwing things up for me, but i doubt it is)

Happens for me, too.

Alternative:

source = new File(getClass().getProtectionDomain().getCodeSource().getLocation().toURI());

But I bet you know that trick already, too.

 

actually, i don't. i'm not very experienced with handling files/uri/url stuff. still learning about it thanks!