Skip to content
SCULKANTICHEAT
Sign up
FiveM documentation§5 In-Game Admin Panel
  1. 1Getting Started
  2. 2Installing the Resource
  3. 3Configuration
  4. 4Commands & Permissions
  5. 5In-Game Admin Panel
  6. 6Rollout Planning
  7. 7Event Policy Worksheet
  8. 8Frameworks (ESX, QBCore & More)
  9. 9Entity Incident Playbook
  10. 10Staff Review Workflow
  11. 11Migrating from Another Anticheat
  12. 12Plans, Billing & the Hard Stop
  13. 13Troubleshooting

Elsewhere

§5

In-Game Admin Panel

The full-screen /sculkpanel dashboard — what it shows, what it can do, and how it stays in step with the website.

On this page6 entries

/sculkpanel (alias /sculkmenu) opens a full-screen monitor inside the game. It is for the times you are already in your server and do not want to alt-tab to the website to check a player, read the feed or issue a ban.

It is gated on the sculk.admin ACE (the list is Config.Panel.Aces):

add_ace group.admin sculk.admin allow

Anyone without it gets a refusal in chat. A client that skips the command and fires the panel's open event directly is refused too, and named in the console with the ACE it lacked.

§5.1What it shows

The panel is a sidebar of views fed by the resource's own live state:

  • Overview — players online, active bans, global bans pending, detections armed, average trust; a breakdown of recent events by type; the armed detections by category; the latest events; and a Sculk Mind summary.
  • Players — the connected roster: id, ping, trust, flag count, linked status, and one-click actions. Searchable.
  • Detections — every detection, grouped by category, with its action, confidence, side and a toggle.
  • Bans — recent bans with reason, detection, staff, duration and a lift button.
  • Global bans — shared ban intelligence: how many of this server's bans are queued to share with other Sculk servers and how many revocations are waiting. Bans shared by other Sculk servers are never enforced here — they arrive as review events for your staff and never block a player automatically.
  • Identity — each connected player's primary identifier, Discord link, trust and flag count, plus recent identity events (connects, bans, flags).
  • Zones — the whitelist zones in force, with add and remove.
  • Triggers — the owner-authored advanced triggers and their state.
  • Sculk Mind — patterns learned, upheld vs cleared, and the top patterns.
  • Console — the live console buffer and the event stream.
  • Settings — server and licence state, and the bulk tools.

§5.2What it can do

Player actions: Warn, Kick, Ban (with a duration), Capture (request a screenshot), Spectate, Teleport to and Exempt.

Server actions: Clear unoccupied vehicles / peds / objects, Broadcast an announcement, and detection toggles.

§5.3It is the same pipeline as the website

Every moderation verb from the panel is turned into a command and handed to the same pipeline the website dashboard uses. That means an in-game ban is:

  • written to the same local ban store as a dashboard ban;
  • posted to the same webhooks, in the same format;
  • queued for ban sync, so it appears on the website's bans view;
  • subject to the same subscription hard stop and the same exemption checks; and
  • attributed to In-game: <your name>, so the website shows who did it and from where.

Nothing in the panel writes a ban by hand or drops a player directly, so the two surfaces cannot drift apart.

§5.4Detection toggles are session-local

Switching a detection on or off in the panel applies for the current session only. The website's saved settings are authoritative and are re-applied the next time the server syncs — which is deliberate: an in-game toggle is a convenience for a live incident, not a second place policy can be edited that then silently disagrees with the website. For a change that sticks, edit it on the anticheat dashboard.

§5.5Security

The panel is a privilege surface, and it is built assuming the client is hostile:

  • Opening the panel and every action require the ACE, checked server-side.
  • The client names a player by their server slot, never by an identifier. The server resolves the slot to an identity at execution time, so a modified client cannot name an arbitrary account to ban.
  • Actions are rate-limited per admin.
  • The panel has no authority of its own: it is a view and a set of buttons over the same pipeline every other surface uses.

§5.6Known limits

  • The Identity view shows the primary identifier and trust status. Hardware tokens and fingerprints are matched server-side but not listed in the panel.
  • The Global bans view shows this server's outgoing queue. Bans shared by other Sculk servers are not listed there as enforced bans; read them as review events.
  • Webhook configuration is shown on the website, not in the panel.