Moves signal overrride warnings to it's own log file (#70034)

I'm tired of seeing it in the runtime log. If the signals_log file exists, that means something needs to be fixed. Enjoy.

admin: Moved signal overriden stack_trace warnings to it's own log file.
This commit is contained in:
ShizCalev
2022-09-20 22:46:07 -07:00
committed by GitHub
parent 6baebf47a1
commit feadabf1a4
4 changed files with 25 additions and 18 deletions
+1 -1
View File
@@ -192,7 +192,7 @@
for(var/sig_type in (islist(sig_type_or_types) ? sig_type_or_types : list(sig_type_or_types)))
if(!override && target_procs[sig_type])
stack_trace("[sig_type] overridden. Use override = TRUE to suppress this warning")
log_signal("[sig_type] overridden. Use override = TRUE to suppress this warning.\nTarget: [target] ([target.type]) Proc: [proctype]")
target_procs[sig_type] = proctype
var/list/looked_up = lookup[sig_type]