Closed ItsBexy closed 8 months ago
It seems like they share the same listener, which somewhat makes since as they are all implementations of AddonActionBarBase.
I still assert that AddonLifecycle is for basic uses and for anything advanced you'll need to hook things yourself like always.
I don't think there's anything I can really do to stop things like this from happening.
I'm not sure I have an especially advanced use-case; listen for ReceiveEvent
, check the type, call one of my plugin's methods if it's a certain type. Not much happening inside the handler.
I'm content to stick with the hook that I currently use for this functionality, but a guardrail or blacklist for addons which share listeners might be appropriate.
I'm running into an issue using
AddonEvent.PostReceiveEvent
with certain addons. If I set up aPreReceiveEvent
orPostReceiveEvent
listener like this:AddonLifecycle.RegisterListener(AddonEvent.PostReceiveEvent, "_ActionBar01", ReceiveEventHandler);
With a simple handler like this:
It will work fine for events on
_ActionBar01
, but will cause an instantaneous CTD when there's an event on any other hotbar, even if I didn't register a listener for any of them.The stack overflow looks like this:
...and so on for a couple hundred lines.
@MidoriKami