Context
Within a PocketMine-MP environment, regulating simultaneous connections constitutes a fundamental pillar of network administration and infrastructure performance management. The maximum number of users capable of connecting concurrently is determined by a simple yet highly critical configuration directive.
Adjusting this parameter allows you to efficiently correlate network load and hardware resource allocation (CPU/RAM) with your Winheberg game hosting plan or VPS instance.
Locating the Configuration File
All global directives governing your PocketMine-MP instance are centralized within a single text configuration document:
server.properties
This file is located at the root of your storage directory (/). To access it and modify its configuration variables, two methods are available:
- The File Manager: Accessible directly from the web interface of your panel.winheberg.com.
- A Third-Party SFTP Connection: By utilizing a specialized client such as FileZilla or WinSCP.
Modifying the Maximum Player Count: Step-by-Step Guide
Riggorously apply the following steps to resize your connection slots while preventing any risk of data inconsistency or loss.
1. Terminate the Server Process
Before editing any system or configuration file, you must imperatively stop your game instance from running. If the process remains active in the background, the PocketMine-MP engine will automatically overwrite your changes during its next write cycle or when the server shuts down.
2. Edit the server.properties File
Open the document using the text editor integrated into your panel or via a local development environment (such as VS Code or Notepad++). Locate the max-players directive. By default, the instruction appears as follows:
max-players=20
3. Adjust the Numerical Value
Replace the default integer value with the restrictive threshold you wish to enforce on your application infrastructure:
- Private or Restricted Configuration (Staff / Testing):
max-players=10 - Standard Community Configuration:
max-players=50 - Optimized High-Load Infrastructure:
max-players=100
4. Save Changes
If you are using the web editor on the Winheberg panel, validate your changes by clicking the Save Content button or use the standard keyboard shortcut Ctrl + S (Cmd + S on macOS). If transferring via SFTP, ensure you upload and overwrite the file in your remote space.
5. Initialize the Server
Return to the Console tab of your management panel and click the start button. Your modifications are instantly applied by the core engine and become visible from the server index menu on the Minecraft Bedrock client interface.
Resource Allocation and Performance
Artificially increasing the max-players variable does not guarantee that your hardware resources can absorb the influx of users without performance degradation (TPS drop or lag).
Each connected profile continuously generates entity calculations, network refresh requests, and world segment allocations (chunks). The actual performance of your instance depends on the following critical factors:
| Component / Impact Factor | Role and Influence on System Load |
|---|---|
| Processor (CPU) | Critical element affected by in-game physics calculations, entities (mobs/projectiles), and synchronous plugin logic. |
| Random Access Memory (RAM) | Required to maintain chunks loaded in memory and process temporary database information (player sessions). |
| Extensions (Plugins) | Heavy, obsolete, or poorly optimized scripts drastically reduce the machine's raw capacity. |
| World Optimization | The rendering distance (view-distance) exponentially multiplies CPU/RAM usage per connected player. |
Troubleshooting
❌ The Max Player Slot Count Reverts to Default Upon Startup
- Process Termination Failure: The server was not completely stopped when editing the file. Use the Stop button on the console, wait for the background process to end, and then re-edit the
server.propertiesfile. - Syntax Error: Ensure that no spaces are present around the
=sign and that no alphabetic characters have been inserted (e.g., entermax-players=50and notmax-players = 50 slots).
❌ The Server Experiences Severe Lag When the Limit is Reached
- Hardware Saturation: Your hosting plan or current plugin configuration cannot sustain such a load. Reduce the
max-playerssetting or optimize your general engine configuration files (pocketmine.yml).
Administrative Best Practices
- Incremental Scaling: We recommend increasing the number of slots gradually (in increments of 5 to 10 slots) to analyze the performance impact on the Winheberg panel's CPU and RAM utilization graphs.
- Correlation with View Distance: If you significantly increase the maximum player count, proportionally lower the
view-distancevariable in your configuration files to limit the volume of chunks loaded simultaneously. - System Restore Points: Form the habit of generating a manual backup via the Backups tab before altering configuration files to quickly restore your environment in case of a mishap.
Need Help?
Regulating the max-players parameter remains the most direct mechanism to safeguard your PocketMine-MP architecture against system overloads. Finding the optimal balance will ensure a smooth gaming experience for your community.
If your modifications are not being registered or if you encounter capacity planning challenges, our technician teams are at your disposal. You can submit a support ticket to our Technical department from your client area at billing.winheberg.com by attaching your PocketMine-MP subscription for personalized expert assistance.
Happy administration and have a great game on your Winheberg infrastructure! 🎮
