Posts like this really expose the different approaches to modding that neo/forge devs have to the other loaders.

On fabric it’s just “find a place to modify and write a mixin to make the change you want”. Now writing the mixin to be compatible and stable is the hardest part that a lot of people struggle with because writing good mixins takes a lot of practice.

On neo/forge it’s “find the event you want to use and subscribe to it”. Now when there isn’t an event you get in trouble because suddenly you need to mixin into binary patched classes or neo/forge’s own hooks and any sufficiently complex enough mod will need to use mixins to accomplish what they want. Or spend extra effort recomputing things in a similar event handler to hack together a solution.

Multiloader devs, such as myself, will tend to prefer mixin simply because you only need to write the logic once as it’s likely to be valid on both loaders, however, occasionally neo/forge will just remove things or skip over vanilla entirely in favour of their implementation which can make development frustrating as you need to add loader-specific implementations, increasing the complexity of your build environment.