Originally Posted by OSWO
The .sp files are there, you can add a LogToFile to the slap function and recompile the plugin.
Would be quite time consuming to add that to every plugin and recompile it. I'm able to capture sm_slap when using a CommandListener along with any other command that is run through chat (! /) or typed in console. My issue is that the menu used in sm_admin seems allow any command to bypass a CommandListener which makes it harder to log everything.
Originally Posted by psychonic
All of the actions mentioned get logged to the SourceMod log file by default (in sourcemod/logs/).
If you want them to log to the game log instead (and thus available in a log stream like you can capture with HLSW), there is an option in SourceMod's core.cfg for that.
I Guess it does log them, as long as its a plugin that has "LogAction" written into it which seems to not include most of my plugins, but this isn't my preferred way to have these logged.I have a plugin that logs each admin command to a file with the admins name and steamid which is accomplished using a CommandListener, but the sm_admin menu is bypassing that. Is there a possible way I can capture all commands used in the sm_admin menu so that I can have everything neatly logged?
In the core.cfg I did change "LogMode" "daily" to "game" and this does indeed allow the sourcemod log to get displayed in HLSW, but then i loss that log file and i have problems reading the tf/logs because filezilla always says the latest log is being used by another process and wont transfer it to me. Would it be possible to have both the sourcemod/log and display to hlsw?
Thanks for your responses.