A public FiveM server can quickly fill up with players who disrupt the atmosphere. A whitelist keeps your community manageable, while a priority queue ensures your core members do not have to wait when the server is full. Both systems are essential for serious roleplay servers. Here is how to set them up.
Why a whitelist?
Without a whitelist, anyone with FiveM can join your server. That sounds great for growth, but on a roleplay server it quickly leads to problems. Random players who do not understand roleplay, trolls who intentionally cause disruption, and a moderation team that cannot keep up. A whitelist filters at the door: only approved players get in.
Most serious RP communities ask potential players to fill in an application. Questions about roleplay experience, character background, and availability help you assess whether someone fits the server. Only after approval is the player added to the whitelist.
Manual whitelist via server.cfg
The simplest whitelist works with Steam Hex identifiers. In your server.cfg, enable the whitelist:
set sv_whitelist_enabled true
Then add players via the server console with add_ace identifier.steam:hexvalue group.user allow. This is workable for small servers with ten to twenty players but becomes impractical as your community grows.
Whitelist via a resource
For larger servers, use a whitelist resource that stores identifiers in a database. Popular options include:
- EasyAdmin: combines whitelist with ban list and moderation tools. You manage players via an in-game menu or Discord commands.
- vMenu whitelist: if you already use vMenu, you can activate the built-in whitelist functionality per submenu.
- Custom Lua script: a simple script that compares the player identifier to a MySQL table on connect. If the ID is not listed, the connection is refused with a clear error message.
The advantage of a database solution is that you can automate whitelist applications. A Discord bot accepts applications, and after approval by a staff member, the identifier is automatically added to the database.
Discord verification as whitelist
Many FiveM servers link their whitelist to Discord. The player must be a member of the Discord server and have a specific role to connect. Resources like Badger_Discord_API or Discord Perms check on connect whether the player has the required Discord role. No role, no access.
This system is particularly effective combined with an application process. New members submit an application via a Discord form. After approval, they automatically receive the whitelist role. It saves manual management, and the link stays current: if someone leaves the Discord, they automatically lose server access.
Setting up a priority queue
If your server is regularly full (for example 64 out of 64 slots), you want your regulars, donors, and staff not to wait in the same queue as new members. A priority queue handles that.
The principle is simple: each player gets a priority value. The lower the number, the sooner your turn. Staff gets priority 1, donors priority 10, and regular players priority 100. On a full server, players with higher priority move forward in the queue.
Common priority systems
The following resources offer priority queue functionality:
- txAdmin priority: if you use txAdmin (the default FiveM server manager), you can set up priority lists in the configuration based on identifiers.
- Adaptive Card queue: shows a visual queue to the player with position and estimated wait time, while handling priorities in the background.
- Custom priority via MySQL: store priority values in the same database as your whitelist. A single Lua script reads the priority on connect and places the player in the correct queue position.
Linking priority to Discord roles
The smartest approach combines priority with Discord roles. Define in your resource which Discord roles get which priority. For example: the "VIP" role gives priority 10, "Booster" gives priority 20, and members without a special role get the default priority. This way you do not need to manage individual identifiers, and priority changes automatically when someone gains or loses a role.
Reserving slots
An alternative to a priority queue is reserving slots. Set your max players to 64 but reserve 4 slots for staff. Regular players can fill up to slot 60; the last four are exclusive to staff members. Various resources support this via a sv_reserved_slots setting or a custom configuration option.
Tips for a smooth waiting experience
- Show the queue position and estimated time to the waiting player. Nothing is more frustrating than a blank loading screen with no information.
- Set an AFK kick so inactive players are automatically removed after a certain time. This frees space for those waiting.
- Communicate transparently about your priority system. Players accept a queue better when they understand how it works.
Can I combine a whitelist with a priority queue?
Absolutely, and that is the recommended approach for serious RP servers. The whitelist determines who can connect; the priority queue determines the order when the server is full. Both systems complement each other without conflicting.
How many slots should I set on my FiveM server?
That depends on your hardware and server type. A roleplay server with heavy scripts runs comfortably at 48 to 64 players. A deathmatch or racing server can often handle more because the scripts are lighter. Start conservatively and increase the slot count as performance allows.
What happens if I turn off the whitelist?
Then anyone with FiveM can join your server, provided there is a free slot. All previously set whitelist data remains in your database, so you can reactivate the whitelist later without starting over.
Looking for a stable FiveM server where you can set this up right away? Check our FiveM hosting with txAdmin, full access, and fast support.
