How to enable OneSync and raise the FiveM player limit above 32

You set sv_maxclients 64 and the server still caps at 32, or it ignores the value, or you get a warning when you try. The 32 limit belongs to the old networking mode. To go higher you need OneSync, and this is how to turn it on and check it.

#What OneSync does

FiveM has two player sync modes. The old one, often called legacy, handles up to 32 players. OneSync moves the entity handling to the server, which is what allows more players, and also what makes server-side entity functions and state bags work.

Many modern resources also expect OneSync. For example, voice resources such as pma-voice rely on it, and some scripts read entities from the server. If one of your resources says it needs OneSync, this is the setting.

#Enable OneSync in server.cfg

Add this line to your server.cfg:

set onesync on

Then set the number of slots:

sv_maxclients 48

Restart the whole server. These are start-up convars, so restart on a resource or a config refresh does not apply them.

If you start the server from the command line or a shortcut, you can pass it as an argument instead:

+set onesync on

Tip: put set onesync on near the top of server.cfg, before the ensure lines, so it is already on when resources start.

#Enable OneSync in txAdmin

Older txAdmin versions have a OneSync dropdown in the settings page, in the FXServer section. If you have it, choose on and save. Newer versions leave it out and expect the line in server.cfg. If you cannot find the option, use the cfg line above, which works with both.

Be careful not to set it in two places with different values. If the txAdmin setting and server.cfg disagree, the final value is hard to predict. Pick one place.

#Set sv_maxclients

sv_maxclients is the slot count:

sv_maxclients 48

Notes:

• It must be a whole number.
• Without OneSync, anything above 32 is not accepted.
• The upper limit with OneSync depends on your license key. Cfx.re ties the number of slots to Element Club tiers on the key's owner. If you ask for more than your key allows, the server will not give you those slots. Read the current limits on Cfx.re before you plan a large server.
• More slots means more CPU and bandwidth. Test with real players, not just the number.

#Check that OneSync is on

The simplest check is a tiny server script. In a resource, add:

-- server.lua
print('onesync: ' .. GetConvar('onesync', 'off'))

When the resource starts, the console should print onesync: on.

If it prints off, the line is in the wrong file, it is commented, or something later sets it back. Search for it:

grep -rn "onesync" server.cfg

On Windows PowerShell:

Select-String -Path server.cfg -Pattern "onesync"

Remember that server.cfg can load other files with exec, so search those too.

#Entity lockdown

With OneSync on, you can control whether clients may create entities (vehicles, peds, objects) on their own. The convar is sv_entityLockdown:

set sv_entityLockdown "strict"

In strict mode, only the server (and resources running on the server) can create entities. Clients that try to spawn vehicles or objects with a cheat or a poorly written script cannot. It is a good defense, but it also breaks any client-side script that creates entities and expects them to sync.

Use it only if you know your resources spawn on the server side. If you turn it on and your shops, vehicles or props stop appearing for other players, set it back and look for scripts that spawn on the client. The values relaxed and inactive also exist. Do not enable strict mode on a live server without testing first.

#Common problems

• The line is ignored: you edited a server.cfg that the server does not load. Check the path in the txAdmin console.
• Resources break after enabling it: a few very old scripts use legacy-only behavior. Check the console for the first error.
• High load with many players: more slots increase the server's work. Look at which resources cost the most, see resmon high ms and how to optimize.
• Voice stops working after the change: check the voice resource order and its settings, see pma-voice not working.

#Checklist