Server List Shows the Wrong Player Count

Direct answer

Compare the count returned by the public hostname/proxy with the counts on the backend and any status plugin. A proxy or server-list plugin can override the player sample or count; a mismatched list number does not necessarily mean players cannot join.

What it means

Minecraft’s server list is a status-query response. The proxy, MOTD/status plugins and backend can report different counts, especially in a multi-server network. A cached status response can also be temporarily stale.

If you are a player

• Refresh the list and record the hostname, displayed online/max count and time.
• If you can join, report the actual in-game count separately; do not assume the server is broken simply because the list is wrong.

If you run the server

1. Test the same public address used by players, then compare with the proxy and each backend. Distinguish online count from maximum slots.
2. Check enable-status in the backend server.properties. When disabled, the server can appear offline in the list even though joining still works.
3. Review Velocity ping-passthrough/server-list configuration and any MOTD/status plugin on proxy and backend; avoid two systems rewriting the same ping response.
4. Temporarily disable one status customization at a time on staging, test the public address and verify the count reflects the intended network rather than one backend.

# On a Paper backend, check server.properties:
enable-status=true
max-players=20
# Proxy networks may report a different aggregate count.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

• PaperMC: Basic troubleshooting
• PaperMC: server.properties reference
• Velocity documentation

Related fixes and guides