Dedicated Server Outside Dev Environment Ignoring @SideOnly

[Reika]

I have noticed a new, hopefully unintended behavior in 1.7.10 Forge regarding the @SideOnly annotation, present in both recommended 1180 and newest 1208.

Basically, many of my classes, when initialized, cause the loader to throw a NoClassDefFound error because somewhere there is a method referencing a clientside class. However, in previous versions of Forge, I used to be able to mark the method @SideOnly(Side.CLIENT) and it would load fine, as the clientside code was ignored on the server.

This is no longer the case. Whenever I have a serverside class with such a method (such as a block referencing Minecraft.class in the getRenderColor() function, or a custom class on which I call registerIcons(IIconRegister)), it immediately crashes upon initializing that class.

 

This is especially frustrating as it only happens outside the developer environment; the eclipse-based debug server runs perfectly fine. This inconsistency, combined with the absurdity of not being able to reference clientside code in clientside methods, leads me to think this is a bug.

 

Is it actually a bug, or am I literally supposed to move half my methods' content to the proxy, which works but is hideously ugly and scattered code?

[LexManos]

It is more likely that you're using it wrong.

So post code, post loaded binaries. -Dlegacy.debugClassLoading=true -Dlegacy.debugClassLoadingSave=true