Leaving your staff out

What this gives you: the activity map shows where your players go, not where your admins stood.

Staff characters are dropped from the heatmap samples and from the playtime ranking. Their sessions are still written down — when an admin was on the server is exactly what the admin log is for — and the roster still lists them like anybody else.

config.staff = staffConfig:build({

    ---@type string[]
    aceGroups = {
        "admin",
        "support",
    },

    ---@type string[]
    citizenIds = {
        "ABCDEFGH",
    },
})

A heatmap sample can land before the character behind it is known, so aceGroups answers for anyone holding the permission rather than only for a listed character. citizenIds is added to the shared list in REC_Library, which covers every RE : CORD resource at once; aceGroups replaces its default instead, because widening a permission boundary should never happen by accident.

A convar does the same as the list without touching a file:

  # every RE:CORD resource
  set REC:staffCitizenIds "ABCDEFGH, K3PQ81ZR"

  # this resource only
  set REC_PlayerManager:staffCitizenIds "ABCDEFGH"

Set enabled = false to count staff like anybody else.