Strangeness with an InjectedModContainer

[voidzm]

I'm trying to figure out how to create a coremod with Forge. I have it mostly running fine, but my GUI Handler is complaining because it can't find a mapping between my mod object and its wrapper ModContainer (which I am injecting manually). However, the LoadController refuses to put my mapping in the mod list unless the ModContainer specifies itself as "mutable" via the "isImmutable()" function. FML, for whatever reason, wraps my ModContainer (which specifies as mutable) in an InjectedModContainer, which does nothing as far as I can tell other than hardcoding the container state to "immutable". Hence, the LoadController sees the immutable state, refuses to load the mapping, and the GUI Handler won't register.

 

Does anyone know how this is supposed to be done properly? It seems ridiculous for a ModContainer to even have an immutability property if FML is just going to wrap it in an immutable container right after instantiation.

[voidzm]

I was afraid that was going to be the case. If both the regular mod and the coremod can load from the same jar, that should be an okay solution. I just didn't want to have two different files for the user to install. Thanks for the help!