Staff mode

#Why Hydra needs to know

If your staff have their own admin mode with godmode, noclip or invisibility, Hydra flags it like a cheat until it knows who is on duty. A list of script names cannot solve this: a cheat menu's godmode looks exactly like your staff mode's. So your staff script tells Hydra instead, on the server, where players can never fake it.

Choose which detections are excused on duty in Settings › Staff mode. The defaults cover godmode, noclip, invisibility, teleports, speed and spectating. Then connect your staff script in one of these ways, best first.

#A. A line in your staff script

In the staff script's server file, where it turns duty on and off after its own permission check, add (use the variable that holds the player's id there, often source or src):

pcall(function() exports.HydraAC:SetStaffMode(source, true) end)   -- on duty
pcall(function() exports.HydraAC:SetStaffMode(source, false) end)  -- off duty

#B. The duty event of an escrowed script

Most staff scripts announce duty changes to other resources with a server event; their documentation lists it, for example:

TriggerEvent('admin:server:dutyChanged', source, true)

Enter it in Settings › Staff mode › Escrowed script: the event name, the resource it comes from, which argument is the player, and whether another argument says on or off (or the event itself means on or off duty). No code to change. Hydra only accepts the event from that resource, on the server.

#C. Staff permission (last resort)

For scripts that announce nothing, turn on Staff permission on the same page and give your staff the ACE in server.cfg:

add_ace group.admin hydraac.staffmode allow

See also: SetStaffMode export.