RZ Arena setup guide

What it is

A redzone PvP mode pack for FiveM

A rotating-mode arena: GunGame, Team Deathmatch, Juggernaut, Kill Confirmed, Infected and One in the Chamber, on a mode chain you control. GunGame runs by default, the rest are staged behind flags until you turn them on. Squads and parties, per-weapon camo challenges, a weekly operations track and persisted leaderboards sit on top of the modes.

# the mode chain, each flag a server-side toggle
GunGame  ->  TDM  ->  Juggernaut  ->  KillConfirmed  ->  Infected  ->  OIC
# default: GunGame on, the rest staged off until you flip them

It is built standalone for a redzone, so it does not require a full RP framework: drop it in, set your config, it manages its own state. Modes, timers, rewards and loadouts are all configured server-side. It also includes lightweight soft-flag heuristics that surface obvious abuse for staff review; for full server-authoritative protection across the rest of your server, pair it with Nightward.

Standard vs open source

Two ways to buy

Both tiers ship the exact same full source and the same six modes. RZ Arena, standard binds to one server. RZ Arena, open source raises the activation cap to three servers, for a network that wants to own and extend the code. Both validate on boot against the same license API.

Install

Install on FiveM

Buy a tier, then extract the zip from your delivery page into your server's resources folder and add an ensure line for it in server.cfg, using the folder name from the zip.

-- server.cfg
ensure <resource-folder-name-from-the-zip>

On first boot the resource validates its license against the license API below. The first successful call binds that activation to the server, so the key is now tied to this install.

License

Activate and move a key

The resource validates through the same license API as the rest of the catalog. The first call from a server binds an activation; to move it to a new server, free the old slot first.

POST /api/license/validate
{ "key": "...", "product": "al-rzarena", "fingerprint": "my-server-ip-or-cfx" }

# moving servers: free the old slot, then validate from the new one
POST /api/license/deactivate
{ "key": "...", "fingerprint": "old-server-fingerprint" }

Product SKUs: al-rzarena (standard, one activation), al-rzarena-src (open source, three activations).

Troubleshooting

License and start-up issues

• over-limit the key already has an activation on another server. Deactivate the old fingerprint, then validate from the new one.
• revoked the key has been revoked. Contact support.
• Resource not starting: confirm the ensure line is present in server.cfg and check the server console for the specific error it prints.