General BindableEvent timing issue

[veilict (MNSD_Vel)]

I haven’t had an issue like this ever before, this is my first time encountering this issue.

Re-Pro Steps:

• Set up a BindableEvent, anywhere applicable.
• Hook onto the .Event signal.
• Using prints to visualize the depth into the instruction, print in log when the :Fire method was called, and when the event was received by the scheduler.

Result:

Instruction Set:

Log (Both RECEIVED and FIRED. messages come from the signal callback):

The event is received AFTER the declaration of NewText and NewIcon.

Every time in the past, I have never had a timing issue such as this. Events always fired all callbacks immediately upon calling :Fire.

So if an investigation can ensue to hopefully fix this (it seems the callbacks may be firing on a deferred thread), I would greatly appreciate it so I don't have to create pseudo-events and fill up more memory.

It’s even present on Roblox-issued RBXScriptSignals and not just from BindableEvents.

Example being: Instance:GetAttributeChangedSignal

[focasds]

Workspace.SignalBehavior is probably set to Deferred. Change it to Immediate if you want to keep it the old way.

Roblox is planning on having this behavior by default in all games in the future, so build your game with that in mind and expect the events to not trigger exactly after you change a property or call Fire().