What Is OneSync?

OneSync is FiveM's server-authoritative synchronization system. It fundamentally changes how player and entity data is synchronized between the server and connected clients, enabling higher player counts, better performance, and more control over game entities.

In 2026, OneSync is the standard for all serious FiveM servers. Understanding how it works helps you build a better, more performant server.

---

How Synchronization Works Without OneSync

In the default GTA V networking model (peer-to-peer), each player's game client is responsible for the entities around them. When player A drives a car, player A's client tells other clients about the car's position. This creates several problems:

• Player limit of 32 — The peer-to-peer model can't handle more connections
• Desync issues — Players may see different states of the same entity
• No server authority — The server can't truly control what happens in the game world
• Cheating vulnerability — Clients have too much authority over game state

---

What OneSync Changes

With OneSync, the server takes control of entity synchronization:

• Higher player limits — Up to 2048 players (with OneSync Infinity)
• Server-authoritative entities — The server decides which entities each player can see
• Scope-based streaming — Players only receive data about entities within their relevant range
• Better performance — Less network traffic because players don't receive data about distant entities

---

OneSync vs OneSync Infinity

OneSync (Standard)

• Supports up to 128 players
• Server-authoritative entity synchronization
• Compatible with most scripts
• Enabled with: set onesync on

OneSync Infinity

• Supports up to 2048 players
• Advanced entity ownership system
• Full server-side entity control
• Better scalability for large servers
• Enabled with:

set onesync on
set onesync_enableInfinity 1

For most servers in 2026, OneSync Infinity is recommended even if you don't plan to have 2048 players. The improved entity management and performance benefits apply at any player count.

---

Routing Buckets

OneSync introduces routing buckets — virtual world instances within the same server:

What Are Routing Buckets?

A routing bucket is an isolated game world. Players in different routing buckets cannot see or interact with each other, even though they're on the same server.

Common Uses

• Instances — Create separate instances for missions, apartments, or events
• Character selection screens — Put players in a private bucket while they choose a character
• Admin areas — Isolate administrators in a separate bucket for testing
• Jail systems — Move jailed players to a separate bucket

How They Work

Each player and entity belongs to a routing bucket (default is bucket 0). Server-side scripts can move players between buckets. When two players are in different buckets, they exist in completely separate game worlds — different traffic, different NPCs, no interaction.

---

Entity Scope and Population

Scope

Scope defines which entities are visible to which players. With OneSync, the server determines scope based on:

• Distance — Entities beyond a certain range are not streamed to the player
• Relevance — The server prioritizes nearby and important entities
• Population budget — Each player has a limit on how many entities they can receive

Population Management

OneSync manages server-side population (NPCs, ambient vehicles) differently than vanilla GTA V:

• The server controls NPC spawning rather than each client
• Population density can be configured per routing bucket
• Ambient traffic and pedestrians are synchronized across players within scope

---

Script Compatibility

Most modern FiveM scripts are designed for OneSync. However, some older scripts may have issues:

Common Compatibility Issues

• Client-side entity creation — Scripts that create entities client-side may not work with entity lockdown
• Player iteration — Old scripts that iterate over all 32 player slots need updating for higher player counts
• Entity ownership assumptions — Scripts that assume a specific client "owns" an entity may behave unexpectedly

Checking Compatibility

• Review the script's documentation for OneSync mentions
• Test the script on a OneSync-enabled development server
• Check the script's community forums or Discord for reported issues

---

Performance Under OneSync

OneSync generally improves server performance compared to the legacy model:

• Less network traffic — Players only receive relevant entity data
• Better CPU usage — Server-authoritative sync is more efficient than peer-to-peer negotiation
• Predictable behavior — Server control eliminates desync-related edge cases

However, very high player counts (200+) require proper hardware and optimized resources. Monitor performance with resmon and txAdmin metrics.

---

Configuration Summary

For a standard roleplay server in 2026, add these lines to your server.cfg:

# Enable OneSync Infinity
set onesync on
set onesync_enableInfinity 1

Population management
set onesync_population true

---

OneSync Enables Modern FiveM

OneSync isn't optional in 2026 — it's the foundation that modern FiveM scripts and features are built on. Scripts like Jobs Creator leverage OneSync's entity management for efficient marker and zone handling across any player count.

→ Browse Premium FiveM Scripts at Alone Studios