Possible wrong use of the "@SideOnly(Side.CLIENT)"

[broncotc]

The current file Charge.java consists 2 decorators of "@SideOnly(Side.CLIENT)" which will cause the mod built from trunk to crash. I was testing truck build due to the sponge incompatibility of the current beta 4 release.
In construction stage of loading module "charge", it throws an exception: "java.lang.RuntimeException: Attempted to load class mods/railcraft/api/charge/Charge$IZapEffectRenderer for invalid side SERVER". This implies the behavior of the decorator "@SideOnly(Side.CLIENT)" might be resisting the entire class/enum from loading instead of strip certain methods from a loadable class on the server side.
What I described here is not matching with the behavior documented here: ForgeDoc/Concepts/Sides , but removing the 2 "sideonly" decorations will make it load and work in the sponge server. Also the forge doc do suggest to not use this decoration except certain very specific circumstances.

Version numbers for your reference:
Forge: 14.23.5.2811
SpongeForge: 1.12.2-2768-7.1.5
Buildcraft: current git
Java: openjdk version "1.8.0_171"

Thank you for investigating into this.

[CovertJaguar]

I admit something did feel off about #33. Hopefully it doesn't cause any issues with running on a normal dedicated server.

[liach]

Duplicate of #33

[liach]

The cause is clear: The code referencing the field is not removed in <clinit>. The modified version of #33 has fixed it.