OneSync changed FiveM forever by replacing GTA V's peer-to-peer networking with server-authoritative entity sync. But choosing between Infinity and Legacy modes confuses many server owners.
What OneSync Does
Without OneSync, GTA V's networking is peer-to-peer. Each client tells others where they are and what's happening. This creates problems:
- Easy to cheat (client controls game state)
- Entity limits per player (~128)
- Poor scalability beyond 32 players
- Desync between clients
OneSync makes the server the authority. The server tracks all entities and distributes state to clients.
OneSync Legacy
The original OneSync implementation.
Player limit: 64 players Entity model: Server manages entities but uses some client-side processing for compatibility
Pros:
- More compatible with older resources
- Lower server CPU usage
- Tested and stable
Cons:
- Limited to 64 players
- Older synchronization approach
- Some entity types still use client-side handling
OneSync Infinity
The next generation. Removes the player cap.
Player limit: Up to 2048 (practical limit depends on hardware and resources) Entity model: Fully server-authoritative with entity culling
Pros:
- Supports 100+ players (with proper hardware)
- Better entity management
- Improved anti-cheat capabilities
- Distance-based entity culling reduces bandwidth
- Better vehicle and NPC synchronization
Cons:
- Higher server CPU usage
- Some older resources incompatible
- Requires more development discipline (proper entity management)
Configuration Comparison
Legacy Setup
onesync legacy
sv_maxclients 64
Infinity Setup
onesync on
sv_maxclients 128
set onesync_distanceCullVehicles true
set onesync_forceMigration true
Performance Impact
OneSync Infinity uses more CPU because the server processes more entity state. At 64 players:
| Metric | Legacy | Infinity | |--------|--------|----------| | Server CPU (64 players) | ~35% | ~45% | | Memory usage | ~4GB | ~5GB | | Network bandwidth | Higher per player | Lower per player (culling) | | Entity capacity | ~1024 | ~2048 |
Infinity uses more CPU total but less network bandwidth per player thanks to distance culling. Clients only receive entity data for things within their visibility range.
Which to Choose
Choose OneSync Legacy if:
- Your server runs 64 players or fewer
- You use many older resources that haven't been updated
- CPU resources are limited
- You want maximum compatibility
Choose OneSync Infinity if:
- You want more than 64 players
- You're using modern resources (ESX v1 Final, QBCore, ox_core)
- Your CPU can handle the extra load
- You want better anti-cheat through server authority
Migration from Legacy to Infinity
- Audit your resources: Test each resource with Infinity on a staging server
- Update frameworks: Ensure your framework version supports Infinity
- Fix broken resources: Common issues are entity creation without proper ownership and client-side entity manipulation
- Test at scale: Invite 20+ players to your test server
- Monitor performance: Compare CPU usage and player count
Resource Compatibility
Resources that commonly need updates for Infinity:
- Vehicle spawning scripts (need proper entity ownership)
- NPC scripts (must handle entity migration)
- Custom weapon systems (entity state synchronization)
- Map loading scripts (streaming and entity scope)
Resources that usually work fine:
- UI scripts (NUI-based)
- Chat and communication
- Economy and banking
- Menu systems
On Space-Node's FiveM plans, the Ryzen 9 7950X3D handles OneSync Infinity's CPU demands efficiently. The single-thread performance advantage is particularly valuable here since entity processing is primarily single-threaded.
