You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically the opposite of SHOULD_CALL_PARENT - it bans child procs from calling the parent proc.
Example of where it'd actually be useful:
/datum/controller/subsystem/proc/fire(resumed =FALSE)
SHOULD_NOT_CALL_PARENT(TRUE)
flags |=SS_NO_FIRECRASH("Subsystem [src]([type]) does not fire() but did not set the SS_NO_FIRE flag. Please add the SS_NO_FIRE flag to any subsystem that doesn't fire so it doesn't get added to the processing list and waste cpu.")
The text was updated successfully, but these errors were encountered:
Basically the opposite of
SHOULD_CALL_PARENT
- it bans child procs from calling the parent proc.Example of where it'd actually be useful:
The text was updated successfully, but these errors were encountered: