The changes work well, but I think this should be converted to the ShipInit pattern. What that basically means for you is that instead of the hooks always being registered and having an early return, ShipInit will register/unregister the hooks whenever the corresponding CVars change. I think there's a few examples in the codebase already, my Custom Message Hooks branch has several more examples.

Best Example I can see is Assignable Tunics and Boots. AssignableTunicsAndBoots.cpp has a call to RegisterShipInitFunc at the bottom, which calls RegisterAssignableTunicsAndBoots whenever CVAR_TUNICBOOTS_NAME changes (defined earlier in the file as CVAR_ENHANCEMENT("AssignableTunicsAndBoots") earlier in the file), which uses COND_VB_SHOULD to register or unregister the hook according to the value of the CVar. Then, in the body of the hook, you can already assume the setting is turned on which simplifies that logic. And then you don't need the calls in TimeSavers_Register.

The pattern you're currently using is the older one from before ShipInit existed, and those should probably all be converted to ShipInit over time.

If any of that is confusing or if you need help let me know, I can help you get it converted over.

It's clear, I've dealt with shipinit quite a bit already

The pattern you're currently using is the older one from before ShipInit existed, and those should probably all be converted to ShipInit over time.

Why wait? #5416

I'd like to request one thing before merging this, that being something leggett mentioned in another PR: more specific initFunc names. I think it would be good to get in the habit of just having their names reference their purpose as, even though they're static so they're locally-scoped, they're not namespace-locked, and I'd just rather avoid a bunch of same-name functions throughout the ShipInit addons.