ClientNewCallback() is always called after client/New()

ID:2910812
 
Feb 2 2024, 12:18 pm
Resolved
Certain events related to client initialization, like sending the client appearance (and therefore client verbs) did not trigger until client/New() ended. This has been changed so that now as soon as the default client/New() ends, that behavior is triggered even if more code has been added to a client/New() override after the default call.
BYOND Version:515.1630
Operating System:Windows 11 Home
Web Browser:Chrome 121.0.0.0
Applies to:Dream Daemon
Status: Resolved (515.1631)
This issue has been resolved.
ClientNewCallback() is currently called once client/New() finishes entirely, preventing the client from accessing client verbs until after client/New() finishes.
Feb 5 2024, 3:35 pm
Lummox JR resolved issue with message:
Certain events related to client initialization, like sending the client appearance (and therefore client verbs) did not trigger until client/New() ended. This has been changed so that now as soon as the default client/New() ends, that behavior is triggered even if more code has been added to a client/New() override after the default call.