[Bug] GetInvokingResource returns nil when internal event

[kn0pee]

Summary

When triggering an event inside the same resource as the handler, GetInvokingResource returns nil. On prior server versions, this would correctly return the name of the resource.

Easy enough to patch in script, but could cause some legacy resources to stop working.

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b92 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

Windows 11

CPU

No response

RAM

No response

Using txAdmin?

No

Hosting provider

Self-hosted

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Register an event handler in a resource, with a print for GetInvokingResource
2. Trigger the event from inside the same resource
3. GetInvokingResource returns nil

Expected Behavior

GetInvokingResource should return the name of the resource that the event was triggered from

Actual Behavior

GetInvokingResource returns nil

Evidence

No response

Additional Context

AddEventHandler("repro:myEvent", function()
    print("myEvent triggered")
    print("Current resource name:", GetCurrentResourceName())
    print("Invoking resource name:", GetInvokingResource())
end)

CreateThread(function()
    Wait(1000)
    TriggerEvent("repro:myEvent")
end)

[wolfram-cfx]

Thanks, we are looking into it.

[Gogsi]

A fix for this bug has been implemented and is available in the latest patch b95. Please try again and let us know if the issue persists. Thanks for your help!