Choose around the way your community plays
Vanilla keeps the software stack simple. Paper or Spigot can suit plugin-led communities. Fabric, Forge and NeoForge introduce loader, version and modpack dependencies that need separate validation.
Your waitlist choice records demand. It does not turn an untested setup into a supported product.
- Vanilla
- Paper and Spigot
- Fabric
- Forge and NeoForge
- Other requests for research
Plan guidance will use workload evidence
RAM alone cannot predict server capacity. Version, view distance, world generation, plugins or mods, automation and concurrent activity all affect the result.
Pulse, Core, Forge and Rift are provisional allocation choices, not player-count guarantees. Tested recommendations will include their assumptions and limits.
What must pass before we publish support
We must install, start, stop, restart, back up, and restore each listed combination on the purchased node. We must also record upgrade notes, runtime requirements, known limits, and the last test date.
See the version validation methodRegion and control-panel status
We target Singapore for the first game node. We do not promise a live location or latency. We plan console, file, SFTP, schedule, backup, database, and subuser workflows around Pterodactyl. We still need to deploy and test the stack.