Resource settings read from the site
Command, key, 911, cadence, animation, debug, clothing events, framework, map and language: the resource reads them at startup and applies your changes live.
Updated on Oct 5, 2026, 1:36 p.m.
On this page
In short. The resource makes a single call to the site at startup to read its settings, then receives your changes live through the presence channel that is already running (no extra request). You set everything in Administration → Configuration → Agora resource.
Opening in game #
| Setting | Effect | Default |
|---|---|---|
| In-game command | Players type /command (letters, digits and _) | agora |
| Opening key | FiveM key name; empty = command only | F2 |
These settings are in the Resource configuration block, saved in one go. The shared secret (which authenticates the game server, generated on demand), the clear-text http permission and the appearance events are folded under Advanced configuration. The resource code is always delivered readable and commented: there is no "Protect the code" option any more.
A new command or key is registered at the next resource restart. The key is only a default: a player who already changed it in Settings → Key Bindings → FiveM keeps theirs.
In-game behavior #
| Setting | When it applies | Default |
|---|---|---|
| Dispatch / in-game 911 calls | Live | off |
| Call command | At the next resource restart | 911 |
| Presence cadence (seconds) | Live (10 to 60) | 30 |
| Opening animation | Live | on |
| Verbose log (debug) | Live | off |
| Appearance events | At the next resource restart | default list |
The presence cadence is the pace at which the resource reports players to Agora. It is capped at 60 seconds: Agora considers the server offline after 90 seconds without a signal, and a slower cadence would make it look broken ("unreachable" status, players left out of dispatch, shifts cut). A higher value saved before this cap is brought back to 60 when read, and the screen refuses a new entry above 60.
Appearance events are the client events of your clothing script after which the portrait is sent back. Empty = the default list (ESX skinchanger, qb-clothing, illenium/fivem-appearance). One per line, under Advanced configuration. Below the list, the screen says what Agora detected ("Clothing detected: …"): if your clothing script is recognised, there is nothing to set.
Strict tablet CSP #
Setting Tablet: restrict pages and forbid replacing the tablet (CSP + sandbox), under Advanced configuration, off by default. Ticked, it adds protection to the in-game tablet:
- the site frame can no longer navigate the tablet page itself (iframe sandbox without
allow-top-navigation); - it can only go to your site, Discord, PayPal and Tebex (CSP
frame-src); - external links open in a separate window.
This setting is written into the resource files: after Save, redeploy then restart. Try it first: tick, save, open the In-game preview (tablet) (it applies the same setting), then check the tablet in game after the redeploy. If it no longer shows, or a payment page refuses to open (a gateway other than PayPal or Tebex), untick and redeploy: the tablet goes back exactly as before.
Rights in the tablet #
There is no "Admin rights in the tablet" setting any more: the tablet always opens in player view, with the player's rights. Administration, the console, moderation, the license and updates stay closed from the game: they are done on the site, in your browser.
Settings read elsewhere #
| Setting | Where |
|---|---|
| Framework | Server → Database |
| Live map (enabled, cadence) | Administration → Configuration → Live map |
| Language | Administration → Configuration → Site identity |
When a setting takes effect #
At the next presence cycle (30 seconds by default), otherwise at the next resource start. After Save, the message tells you the gesture to make: "Applied live: nothing else to do", "restart it" or "redeploy it, then restart it".
If the site is unreachable at startup #
The resource falls back on safe defaults (dispatch off, map on), says so in yellow in the console, and tries again.
What requires a redeployment #
The site address, the secret, "Allow clear-text http", the strict tablet CSP and the tablet frame are in the files: see Update the resource.
Was this article helpful?
Related articles
- config.lua (the address) and config.server.lua (the secret)The resource only keeps two things in its files: the site address and the shared secret; everything else is set on the site.
- The in-game tablet: key, command and rightsThe tablet opens with a command and a key you choose, with the loaded character; admin actions stay on the site.
- Dispatch and 911 callsThe live call queue and on-duty units; in-game 911 is disabled by default and is turned on in Administration → Configuration → Agora resource.
- Supported frameworks: ESX, QBCore, QboxAutomatic or fixed framework, what Agora reads in each framework, how a player is recognised, and the start order to follow in server.cfg.