Local vs Socket Hooks

[pseudo wasp]

We've talked a bit about this internally, because some cards events are difficult for modules to handle with the currently scope of hooks.

The current recommendation is: hooks run locally and the event consumer can decide to trigger a socket event that results in other clients performing an action.

The potential future state is that core may provide some infrastructure for broadcast hook events which are triggered on one client but executed on another.

I don't think this will be part of V9, so my main advice would be to design whatever solution you go with here that is sufficiently modular that if core offers an official way to do it in the future you can easily change your implementation.