Open damage220 opened 1 year ago
amxx_logging seems to be only for normal amxx logs as LogError totally ignores amxx_logging value (which i think it's nice as there won't be ppl disabling it and then saying that X its amxx's fault instead of their plugins makings 30 errors/sec)
i really think it's great to have errors logged as another file instead of having to find errors on the regular logfiles as they may get huge
https://github.com/alliedmodders/amxmodx/blob/27f451a868c3154a0ab0d4d70e0a650074fd485d/amxmodx/amxxlog.cpp#L260-L267 but the main issue is that it stops showing errors on console after not being able to write the error log file, which i consider it kinda bad
solutions may be
doing stuff like allowing to change the error log filename formatting or mixing both logfiles would have more cons than pros
So there is no issue with amxx_logging 3
as I simply misunderstood its meaning, though I believe comment in core.ini regarding description of this setting should be more clear.
Having errors to be placed to "normal messages" file may be useful because in this case errors will have context, i.e. you may see that some errors appear at the end of the round or under certain circumstances. I thought that amxx_logging 3
does this. I was wrong.
Environment
Description
When
amxx_logging
is set to3
(HL logs) and the default log directory (cstrike/amxmodx/logs) is not writable, amxx will throw an error in the terminal even if it can write to cstrike/logs.When
amxx_logging
is set to3
andamxx_logs
is set tologs
, amxx prints errors to the terminal and logs them to cstrike/logs, however amxx creates error_20230918.log and does not utilize default HL log files.Problematic Code (or Steps to Reproduce)
public plugin_init() { server_print("%d"); }