Update the FiveM resource

In short. Most resource settings live on the site and apply on their own. You only need to redeploy the resource in three cases: a new version, a new site address, a new secret.

When to redeploy #

After every Save on the page, the site tells you the right gesture: "redeploy it, then restart it", "restart it", or "Applied live: nothing else to do".

Is it up to date? #

• Server → Players, Game server box: the version announced by the resource.
• Administration → Configuration → Live map, Position feed status: if the resource is older than the one Agora provides, a message asks you to redeploy it.
• In the game server console, at startup: [agora] v0.3.3 — ….

Version 0.3.3 keeps the 0.3.2 changes (the resource's calls to Agora no longer follow any redirect, so the shared secret never goes to another address; a strict tablet CSP setting, off by default: see Troubleshoot the FiveM resource and Resource settings read from the site) and makes the resource sturdier:

• an error no longer freezes it: if processing Agora's answer fails, the resource no longer stays stuck "sending" (which made the site see the server as offline until the next restart): the error is reported and sending resumes, and a send with no answer for 30 seconds is resumed;
• the framework has the last word: the state announced by a framework event (character, job, grade) is only a hint; if it differs from what the framework knows, the framework wins. So a badly ordered event or one forged by a third-party resource sets no false state;
• changing character clears the former character's call alerts and the portrait delay;
• a booking photo whose target leaves the server releases the agent, who is told ("The target left the server");
• the presence cadence is capped at 60 seconds (see Resource settings read from the site);
• opening the tablet is limited per player (10 per minute) so that a few modified clients can no longer prevent everyone else from opening it.

Redeploy it after the Agora update to benefit.

The resource's numbering started over from zero: any resource announcing a 1.x (1.0.0 to 1.10.x) is older than 0.3.3, and Agora offers to redeploy it.

Redeploy #

Same procedure as the install, your choice:

• Deploy through the panel (Administration → Configuration → Agora resource, Installation block, or Server → Panel), or Redeploy in the "The resource points to …" banner: files replaced and resource restarted (under txAdmin, restart it through txAdmin);
• Deploy over SFTP, then refresh and ensure agora in the server console;
• Download agora.zip (Administration → Configuration → Agora resource), then replace the whole resources/agora folder, and refresh + ensure agora.

No need to touch server.cfg: the ensure agora line is already there.

After redeploying #

Check in Server → Players that the last signal is recent and the version shown is the right one.