player_quit doesn't fire on first event (interpreter-only)

Question

player_quit doesn't fire on first event (interpreter-only)

LadyCailinBot opened this issue 11 years ago · 5 comments

LadyCailinBot commented 11 years ago

CMDHELPER-2796 - Reported by PseudoKnight

--If I click the disconnect button, it doesn't seem to fire a player_quit bind. If I instead close the Minecraft window to receive disconnect.endOfStream then it runs a player_quit bind script.--

UPDATED: It only misses the first event when you bind player_quit in interpreter.

CH Build 2379
CB Build 2865

LadyCailinBot · Answer 1 · 2013-09-09T21:20:26.000Z

Comment by PseudoKnight

It doesn't fire on disconnect.genericReason either.

LadyCailinBot · Answer 2 · 2013-09-09T21:21:40.000Z

Comment by PseudoKnight

Okay, I'm confused. I just saw it fire on disconnect.quitting for the first time. Something is wrong, but I'm not sure what. I'll do more testing.

LadyCailinBot · Answer 3 · 2013-09-09T21:27:36.000Z

Comment by PseudoKnight

Okay, I think what's happening is that it's not firing on the first event after it's bound. Every subsequent event fires okay. My initial testing involved a lot of unbinding and rebinding.

I'm going to test if this is only an issue in interpreter.

LadyCailinBot · Answer 4 · 2013-09-09T21:33:25.000Z

Comment by PseudoKnight

Okay, this seems to only be an interpreter quirk, so no big deal. Events bound in main.ms or on-demand in aliases seem to work fine on the first event.

LadyCailinBot · Answer 5 · 2013-09-10T14:27:59.000Z

Comment by LadyCailin

Hmm. Very interesting behavior. I don't think I've ever really tried events from interpreter, but regardless, I'll look into this.

Share to