Introduction
Introduction
Rivo Queue is a queue and priority system for FiveM. When your server is full,
players wait in line on a branded loading card instead of being refused. Staff
and supporters get through first, and a live admin panel shows you everything
that is happening.
It is standalone and works with any framework. No database, ox_lib or Discord
bot is required. oxmysql is used automatically if it is running.
Features
Queueing. Players see their position, time waited and an estimated wait
based on how fast people are actually getting in. A plain-text mode is available
if you prefer it over the card.
Stacking priority. Points can come from several places at once: rows you
grant from the panel or console, Discord roles, ACE permissions, txAdmin staff, a
hardcoded list, or your own resources. Rows can expire.
Tiers. A tier such as Staff or VIP can skip the queue entirely, use reserved
slots, ignore the restart hold, and show a badge on the card.
Fair ordering. The player at the front can't be bumped by someone who joins
later. Waiting players slowly gain points so nobody waits forever, capped below
your cheapest tier so paying supporters still come first.
Crash recovery. A player whose game crashes gets their place back when they
reconnect. A player who crashes while loading gets their slot held.
Smooth restarts. A startup hold gives your resources time to load, then a
staged release lets players in a few at a time.
Gates. Bans, required identifiers, whitelist, Discord server membership,
connection throttling and optional alt detection.
Operations. Console commands, Discord webhook logging, live metrics,
maintenance mode, and a web admin panel served from your server's own port.
Quick start
- Put the
rivo_queuefolder in yourresourcesdirectory. - Add
ensure rivo_queuetoserver.cfg. - Stop any other queue resource.
- Restart the server.
That is a working queue. Everything else is optional.
Where to go next
| Page | What it covers |
|---|---|
| Installation | Setup, priority, Discord bot, database, admin panel and troubleshooting |
| How it works | The connection flow, slots, ordering, tiers, restarts and crash recovery |
| Configuration | Every option in config.lua, theme.lua and the locale files |
| Commands | Every queue console command |
| Admin panel | What the panel does and how to secure it |
| Developer API | Exports, server events and custom priority sources |
| Migrating from n4_queue | Switching over with your existing data |