Direct answer

The “Server is full” message can originate from a backend max-players limit, proxy/queue plugin or reserved-slot policy.

Identify the failing layer

An advertised proxy slot count does not guarantee that any specific backend has room or performs acceptably at that population.

First checks and evidence

  • Check live player count and max-players on the server that rejected entry.
  • Compare backend and proxy limits, queue plugins and reserved-slot configuration.

Admin diagnosis and repair

  1. If legitimate capacity needs to increase, measure MSPT, CPU memory and network headroom during peak activity.
  2. Increase only the restrictive limit that actually applies, then test from a normal non-OP account.

Verify the fix: Test at the limit with staff and ordinary accounts; confirm rejection behavior and stable tick time match the intended policy.

References

References used to verify the settings and troubleshooting steps in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000