# Set Minecraft player slots without changing plan resources

`max-players` controls a Minecraft Java server's configured player limit. Increasing that number does not add RAM, processor time, storage or network capacity to your hosting plan. Choose the limit from the community size you intend to support, then measure how the server behaves during normal play.

## Check capacity and routing

Record your current plan resources, player limit and typical busy-period performance. Note whether players are exploring new terrain, standing in a lobby or operating farms. Those workloads can differ even when the online count is identical. A quiet test with one player cannot establish that a larger public event will run comfortably.

For a network, identify whether the public entry point is a proxy and whether backend limits are intentionally lower. A proxy may advertise a separate total or route players between several servers. Coordinate those settings rather than copying the same number everywhere. This guide changes one Java server, not the number of slots sold by a third-party listing site.

## Set the limit

Download a private copy of `server.properties`, announce a short restart and stop the server cleanly. Edit the existing `max-players` line. For example, a small group's chosen limit might be:

```
max-players=12
```

This number is illustrative, not a recommendation for a particular plan. Enter a whole positive number and keep only one occurrence of the key. Save, start the server and watch for a normal startup. Do not change the memory startup flags or unrelated network properties at the same time.

Use the reference for the installed release. A current Paper guide may describe options that differ from 1.21.11 or a future 26.x build. If a panel startup variable writes the slot limit automatically, change the supported variable rather than repeatedly fighting the generated file. Ask support if the variable is locked on your plan.

## Verify admission and performance

Refresh the Java multiplayer list and confirm the advertised maximum. Check actual joining behaviour with ordinary accounts. Operator accounts, permission-based bypasses and plugins can alter what happens when the server is full, so a successful administrator connection is not sufficient proof that the limit is being enforced for everyone.

During a representative busy period, record online players, tick performance, memory pressure and any complaints. Compare similar workloads rather than a fresh world with an established map. If lag appears, collect a short profiler report and investigate its cause before assuming that a different slot number will fix it. Avoid stress bots or synthetic connection floods against a live service.

## Lower the limit or recover

To undo the change, restore the previous value during a planned restart. Warn players first when reducing capacity; do not intentionally test a lower limit by disrupting an event. If the server refuses to start after editing, restore the saved properties file and inspect the earliest configuration error.

If you need more resources, request a plan change separately. Keep the distinction clear in staff notes: the admission limit is a configuration choice, while the hosting allocation controls what the server can actually use.

## Related help

- [Diagnose Minecraft lag with TPS, MSPT and spark](https://help.cloudexa-hosting.com/books/game-hosting/page/diagnose-minecraft-lag-with-tps-mspt-and-spark)
- [Understand Minecraft RAM, CPU and storage usage](https://help.cloudexa-hosting.com/books/game-hosting/page/understand-minecraft-ram-cpu-and-storage-usage)
- [Find Minecraft logs and send useful troubleshooting details](https://help.cloudexa-hosting.com/books/game-hosting/page/find-minecraft-logs-and-send-useful-troubleshooting-details)

## Reference

[Paper server.properties reference](https://docs.papermc.io/paper/reference/server-properties/). [Startup arguments that can override properties](https://docs.papermc.io/paper/reference/cli-arguments/).