I noticed a bug around amxx_logging setting. When cstrike/addons/amxmodx/logs directory is not writable, amxx does not print error messages to the terminal, even if amxx_logging is set to 3. When amxx_logging is set to 3 and cstrike/logs is writable, amxx still prints nothing to the terminal. Looks like amxx first checks for the directory to be writable and then enables/disables logging regardless of the amxx_logging setting.
Also, I do not understand why amxx does not write error messages to cstrike/logs when amxx_logging is set to 3 and the user has sufficient permissions to write to cstrike/addons/amxmodx/logs. I tested with the following code:
PHP Code:
server_print("max_entities: %d, %f", global_get(glb_maxEntities));
Redundant %f specifier causes amxx to print an error to the terminal:
PHP Code:
L 09/17/2023 - 20:12:06: String formatted incorrectly - parameter 3 (total 2)
L 09/17/2023 - 20:12:06: [AMXX] Displaying debug trace (plugin "test.amxx", version "unknown")
L 09/17/2023 - 20:12:06: [AMXX] Run time error 25: parameter error
L 09/17/2023 - 20:12:06: [AMXX] [0] test.sma::test (line 22)
but nothing to cstrike/logs directory.