[gH0sTy]

Originally Posted by daleGEND Has anyone looked into these errors?

You're probably using an outdated version as line 25 checks if the client is > 0 before attempting to get the admin ID.

Originally Posted by Powerlord admin_logging_custom doesn't check if the client is -1 or 0 before attempting to get the user's admin ID...

Incorrect, read above.

Originally Posted by Horsedick yeah it does but as I said it needs to have a way to restrict targeting certain steamid's or flag users vs everyone under any use of SM commands

Try the attached version, it will create a sm_admin_logging.cfg file where you can set the flag(s) you want to log.

[TheHardstyleBro]

Originally Posted by gH0sTy You're probably using an outdated version as line 25 checks if the client is > 0 before attempting to get the admin ID. Incorrect, read above. Try the attached version, it will create a sm_admin_logging.cfg file where you can set the flag(s) you want to log.

Thank you, works perfectly

[Pixeli]

Originally Posted by gH0sTy You're probably using an outdated version as line 25 checks if the client is > 0 before attempting to get the admin ID. Incorrect, read above. Try the attached version, it will create a sm_admin_logging.cfg file where you can set the flag(s) you want to log.

THC_RPG Plugin q flag dosen't write anything into log like if you giving levels or credits or xp its not save into admin logs.

[Horsedick]

Originally Posted by gH0sTy Try the attached version, it will create a sm_admin_logging.cfg file where you can set the flag(s) you want to log.

Well let me ask you this.... if you assign say "o" flags - and we know admins have access to all flags will it still pick up on Admins whom will also have this flag and if so can you set it to exclude them from getting logged?

Edit: yeah apparently it will still pick up on anyone with o flag - so looks like it would require an exception cvar.

[Jumpman]

Originally Posted by gH0sTy Try the attached version, it will create a sm_admin_logging.cfg file where you can set the flag(s) you want to log.

I use this version, but still get this error message

L 09/03/2012 - 20:11:05: SourceMod error session started
L 09/03/2012 - 20:11:05: Info (map "gg_beacn_redux") (file "errors_20120903.log")
L 09/03/2012 - 20:11:05: [SM] Native "GetUserAdmin" reported: Client 7 is not connected
L 09/03/2012 - 20:11:05: [SM] Displaying call stack trace for plugin "admin_logging_custom.smx":
L 09/03/2012 - 20:11:05: [SM] [0] Line 36, C:\Users\Administrator\Desktop\GunGame Server\addons\sourcemod\scripting\admin_loggi ng_custom.sp::OnLogAction()
L 09/03/2012 - 20:20:04: Error log file session closed.

[GrO]

Is it possible to edit this plugin so it'd work with Groups?

[Pixeli]

Originally Posted by GrO Is it possible to edit this plugin so it'd work with Groups?

I have same question Is it possible to add q flag for thc_rpg plugin, that mean't you get admin logging when someone give to another players levels,credits,xp or giving itself.

[Horsedick]

Originally Posted by Pixeli I have same question Is it possible to add q flag for thc_rpg plugin, that mean't you get admin logging when someone give to another players levels,credits,xp or giving itself.

you can add a flag in overrides and this will pick it up - only big issue is being able to white list steam id's if they fall within a logged flag as it wouldn't be needed. This plugin has so much potential its just not all that great as of now.

[Pixeli]

Originally Posted by Horsedick you can add a flag in overrides and this will pick it up - only big issue is being able to white list steam id's if they fall within a logged flag as it wouldn't be needed. This plugin has so much potential its just not all that great as of now.

Like This?

Overrides
{
    /**
     * By default, commands are registered with three pieces of information:
     * 1)Command Name         (for example, "csdm_enable")
     * 2)Command Group Name    (for example, "CSDM")
     * 3)Command Level        (for example, "changemap")
     *
     * You can override the default flags assigned to individual commands or command groups in this way.
     * To override a group, use the "@" character before the name.  Example:
     * Examples:
     *        "@CSDM"            "b"                // Override the CSDM group to 'b' flag
     *         "csdm_enable"    "bgi"            // Override the csdm_enable command to 'bgi' flags
     *
     * Note that for overrides, order is important.  In the above example, csdm_enable overwrites
     * any setting that csdm_enable previously had.
     *
     * You can make a command completely public by using an empty flag string.
     */


"thc_rpg_level" "q" //THC_RPG Levels
}