unregister a TickHandler - TickRegistry.unregister(ITickHandler)

[zsawyer]

I know that right now one can pass "EnumSet.noneOf(TickType.class);" or "null" for the overridden tick()-method. But this does not seem like a neat solution.

To optimize performance it should be possible to cleanup a tick handler that is not needed anymore: TickRegistry.unregister(ITickHandler)

This comes into use when mods provide an interface to be disabled or deactivated at runtime.
But there might also be occasions where TickHandlers are logically bound to ingame objects. When the Object is gone the Handler should too.

Right now there will still be an artifact handler instance which will just return null on tick(). But this means unnecessary memory usage and method calls, and statement evaluations (esp. in the for-loop at FMLCommonHandler.java:114 with unnecessary calls at lines 116, 117, 118)

Thanks for considering.

[immibis]

Is there a measurable performance benefit?

[cpw]

I'm not sure what would benefit here. The cost of tick queue management has never been measurable that I have seen.

[zsawyer]

As this is only an enhancement request and not a PR I have no test data.
But being able to clean up objects which eat up ram and cause extra code execution simply sounded like a good idea to me.