I recently discovered/realized a major flaw in a library of mine: plugins listening to its custom events will receive events regarding every plugin hooking it, but each event can only apply to one plugin. If a developer doesn't realize or consider this, they'll end up acting upon events regardless of whether it concerns their plugin or not, and while this will work in an isolated scenario, it causes severe problems when run in an environment with more than one hooking plugin. I need a way to control which plugins receive the library's events, or at least a way to work around it. I feel like there's an obvious solution, but it's nearly 3 AM, so I'm not really thinking too clearly. Anyway, some help on this stupid, stupid issue would be greatly appreciated.