Whitelist a Player
Knowledge base article on Whitelist a Player. Short, actionable steps for Vision Host customers.
By Vision Host Editorial Team - Infrastructure & Hosting Specialists
1. Deep Dive: Whitelist a Player
Whitelist a Player is a top priority for Minecraft server owners running survival SMPs, modded networks, or minigame hubs. Delivering consistent 20.0 TPS (Ticks Per Second) under heavy player traffic requires tuning single-thread CPU performance, chunk loading, entity activation ranges, and Java garbage collection flags.
Vision Host provides paid Minecraft hosting from ₹119/mo on AMD Ryzen 9 7950X / EPYC 9004 processors with pure NVMe storage in India. In this guide, we break down actionable configurations to optimize whitelist a player.
2. Single-Thread CPU Frequency & NVMe Chunk Storage
Minecraft's core game loop relies heavily on a single main thread. As players explore new terrain, generate chunks, or automate mob farms, single-core CPU clock speed dictates whether MSPT (Milliseconds Per Tick) stays under the critical 50ms threshold.
Combining high single-core frequency (5.0+ GHz) with NVMe RAID storage eliminates I/O bottlenecks during world autosaves and player teleports.
- Paper / Purpur: Use paper-world-defaults.yml to adjust entity-activation-range and despawn-ranges
- Fabric / NeoForge: Install Sodium, Lithium, FerriteCore, and Krypton for modpack optimization
- World Pre-generation: Use the Chunky plugin (run /chunky start) to pre-generate world chunks
- Java Flags: Run Java 21 with Generational ZGC (-XX:+UseZGC -XX:+ZGenerational) to stop GC pauses
3. Step-by-Step Server Configuration Example
To optimize whitelist a player, tune entity activation limits and mob pathfinding iterations. Reviewing actual configuration defaults prevents mob farm breakage while saving CPU cycles:
# paper-world-defaults.yml & purpur.yml example tuning world-settings: default: entity-activation-range: animals: 16 monsters: 24 raiders: 48 misc: 8 ticks-per: hopper-transfer: 8 hopper-check: 8
4. Recommended RAM & Hardware Sizing
Sizing RAM and CPU capacity correctly prevents out-of-memory crashes:
| Player Count | Recommended RAM | Server Software | Target Performance |
|---|---|---|---|
| 1 - 10 Players | 3 GB - 4 GB NVMe RAM | Paper / Purpur | 20.0 TPS (MSPT < 25ms) |
| 10 - 30 Players | 6 GB - 8 GB NVMe RAM | Purpur / Pufferfish | 20.0 TPS (MSPT < 35ms) |
| 30 - 60+ Players | 10 GB - 16 GB NVMe RAM | Purpur / Folia | 19.5 - 20.0 TPS |
| Heavy Modpacks | 8 GB - 12 GB NVMe RAM | Fabric / NeoForge | 20.0 TPS (MSPT < 40ms) |
5. Long-term Maintenance & Spark Profiling Strategy
Regular maintenance preserves server health. Run Spark profiler (/spark sampler --timeout 60) weekly to pinpoint lag-causing plugins or tile entities, schedule automated daily restarts during off-peak hours, and maintain off-site backups.
On Vision Host's Pterodactyl panel, automated backups and one-click JAR updates keep your production server secure and performing at its peak.
Quick answers
Featured-snippet style FAQs for this topic.