Hey, I have a coremod that I just named SuperUser cause it changes things that we're complied by the byte code of java.

The only thing I came across that it disabled it self:

Mod SuperUser has been disabled through configuration

 

disabled trought configuration, why is that. I haven't inserted any config that may disable it.

If it's automated to disable by Minecraft where can I reject it and make it run for aslong as the Minecraft is open ?

 

Thanks alot.

	public boolean registerBus(EventBus var1, LoadController var2)
{
	var1.register(this);
	return true;
}

 

Yeah, its return true; still the same.

I have tried this on MCP and reguler Minecraft.

both logs return the same, do you have any ideas about it ?

There is nothing in my ModContainer except a super(new ModMetadata());

and it extends DummyModContainer.

 

I dont see any problem over there.

Its in the ModContainer, I'm not that stupid.

http://pastebin.com/C2SQGJ9s

You can check it out overthere

That is indeed weird. Maybe your IFMLLoadingPlugin is referencing the wrong ModContainer.

 

It's something with the DummyModConatiner for me. after I changed DummyModContainer it had been fixed.

The problem is it's using an @Override that overrides my thing from return true; to return false;

I'm gonna try some stuff, altought nothing worked for now.