How to Change the Max Player Count on Arma Reforger

To change the max player count on an Arma Reforger server, edit the game.maxPlayers field in config.json and restart. The Reforger config spec accepts integers from 1 to 128 with a default of 64, and the right number depends on your scenario, your modlist, and your hardware tier. This guide covers the LPV5 panel route, the manual route, and how to pick a sensible cap.

Where the Player Cap Lives

Arma Reforger reads its player cap from a single integer field: game.maxPlayers inside config.json. It is the hard ceiling on concurrent connected players, regardless of scenario role limits. If the scenario has its own role caps, those still apply on top, but they cannot raise the server past game.maxPlayers.

Note: Per the Reforger config spec, valid values are 1 through 128

Note: Loafhosts plans include unlimited slots, so the cap you choose is purely a config and hardware decision

Change It from the LPV5 Panel

The LPV5 Config Editor inside LoafHub at hub.loafhosts.com is the easiest way to change maxPlayers. The editor preserves JSON structure so you cannot accidentally break the file with a misplaced quote.

1. Sign in to LoafHub at hub.loafhosts.com
2. Open your Arma Reforger server in the LPV5 panel
3. Open the Config Editor
4. Find the maxPlayers field under the game object
5. Type your new integer value, with no quotes around it
6. Save the file
7. Restart the server from the Console tab

Tip: maxPlayers is a number, not a string, so do not wrap it in quotes

Tip: In the LPV5 Config Editor, this appears as a friendly Max Players field on the Game tab; editing it writes the same game.maxPlayers JSON, so you never touch raw JSON unless you want to

Change It Manually in config.json

If you prefer to work on the raw file, open config.json from the LPV5 file manager. The field is one integer on one line, but the surrounding JSON must stay valid.

1. Stop the server from the Console tab
2. Open the file manager and edit config.json
3. Locate the line that contains “maxPlayers”:
4. Replace the number with your new value, between 1 and 128
5. Save the file
6. Start the server from the Console tab

Warning: Do not wrap the number in quotes; “maxPlayers”: “64” is invalid

Warning: Values above 128 are rejected by the config spec and the server will fail to start

Picking a Cap That Matches Your Hardware

Reforger leans heavily on single-thread CPU performance because of AI and physics. A 64-player Conflict match with heavy AI is far more demanding than a 64-player Game Master scene with no AI, so the same cap on the same plan can perform very differently scenario to scenario.

Tip: Start conservatively, then raise the cap once you see the server holding good tick rate at peak

Tip: If frame time spikes or AI starts stuttering, lower the cap or move to a higher Loafhosts tier

Tip: Loafbox plans with dedicated CPU threads handle large or modded matches better than Shared

Note: Loafhosts uses AMD Ryzen 9 7950X3D CPUs on both Loafbox and Shared, so even entry tiers perform well at sensible caps

Network Implications of a Higher Cap

Every connected player generates inbound and outbound traffic, and a higher cap means more bandwidth and more packet processing per tick. On Loafbox you have Terabit.io DDoS protection and headroom for spikes; on Shared you have basic protection. Either way, a cap that exceeds what your scenario can render cleanly is a worse player experience than a smaller, smooth match.

Tip: If you raise the cap by 50 percent or more, plan a test session with bots or volunteers before opening publicly

Tip: Watch for inbound network spikes when your server is featured in any community list

Restart and Verify

Arma Reforger reads config.json on boot, so a maxPlayers change only takes effect after a restart. The LPV5 Console tab handles the restart in one click.

1. Open the Console tab
2. Press Restart
3. Wait for the boot log to print the scenario load lines
4. Confirm the panel and the in-game browser both show the new cap
5. Join the server and verify the slot count matches

Tip: If the browser still shows the old cap, refresh the server list rather than retyping the search

Frequently Asked Questions

What is the maximum number of players for an Arma Reforger server?

The Reforger config spec accepts game.maxPlayers values from 1 to 128, with a default of 64. The practical ceiling for a smooth match depends on your scenario, modlist, and hardware.

Does changing maxPlayers require a restart?

Yes. Arma Reforger reads config.json on startup, so a player cap change only applies after a restart from the LPV5 Console or file manager.

Should I write maxPlayers as a number or a string?

As a plain number with no quotes. Writing “maxPlayers”: “64” is invalid JSON for a numeric field and will cause issues. Use “maxPlayers”: 64.

Will Loafhosts charge me more for a higher player cap?

No. Loafhosts plans come with unlimited slots, so raising or lowering game.maxPlayers does not change your bill. Hardware tier still determines how well the server holds up at high caps.

Can I exceed 128 players on a Reforger server?

Not through standard config. The Reforger config spec caps maxPlayers at 128 and rejects higher values. Some heavily modded scenarios may behave differently, but vanilla supports up to 128.

What happens if a player tries to join a full server?

The Reforger client shows a server-full message and does not connect. The player can wait for a slot to open and retry, or use the in-game browser to find another server.