You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There aren't any checks for many commands to respect users with higher CGs than you. For example, you wouldn't want someone with CG3 to ip ban anyone with CG 4, 5, 6, 7, or 8.
Commands that need these checks:
Not necessarily. It really depends how the commands are distributed between CGs. We have ban/kill/ip commands on CG7 but we still need them for CG8 ex: killing an admin worker account if it gets stuck online. In general, higher command group number does not mean higher position, just different set of commands.
I agree with @cen1.
Instead I want to add logging into different files for each user who use commands with cg > 1, so it will be possible to find violators.
But your script can be easily added in Lua in handle_command.lua. I remember it as an example for documentation.
btw, /killsession should be deactivated in command_groups.conf because this command is for debugging.
There aren't any checks for many commands to respect users with higher CGs than you. For example, you wouldn't want someone with CG3 to ip ban anyone with CG 4, 5, 6, 7, or 8.
Commands that need these checks:
The text was updated successfully, but these errors were encountered: