Three focused server choices
Minecraft is one catalog game with three server-software choices. Paper is the recommended Java option for most groups because it keeps normal Java gameplay while supporting compatible server plugins and practical performance improvements. Java Vanilla is Mojang’s official server for groups that want the unmodified baseline. Bedrock Dedicated Server is Microsoft’s official server for Bedrock Edition players.
The editions use different network protocols. Paper and Java Vanilla listen for Java clients over TCP, while Bedrock uses its RakNet protocol over UDP. GHosting checks the real public protocol before calling an install ready, rather than treating an open process as proof that players can connect.
Current stable releases and authenticated play
Every new server targets the current stable Java release or latest Bedrock release. Managed updates preserve the world and customer configuration while replacing downloadable runtime files. Snapshots, previews, arbitrary versions and managed downgrades are not offered at launch.
Java online mode and Bedrock Xbox Live authentication stay enabled. Cracked or offline-mode servers are not supported. Before the first installation, the dashboard asks the customer to accept the Minecraft EULA and records that acceptance for the specific server.
Plugins, datapacks and Bedrock packs
Paper plugin JARs, Java Vanilla datapacks, and Bedrock resource or behavior packs can be uploaded through the browser file manager or SFTP. Runtime downloads are kept separate from worlds, configuration, permissions and uploaded content so a managed update does not treat customer data as disposable.
The scope is intentionally clear. There is no one-click plugin or modpack catalog, Fabric, Forge, NeoForge, proxy network, third-party plugin debugging or legacy-version matrix. Managed Paper-to-Bedrock crossplay is also not advertised until both sides of that path pass the same real protocol checks as the native variants.
Choose headroom for the world, not a headline player count
Minecraft can be CPU-sensitive before memory is exhausted. Generating chunks, several players exploring in different directions, mob farms, redstone, high view distances and plugins all change the load. That makes one universal players-per-gigabyte promise misleading.
Start with the entry plan for a new small world with ordinary distances. Choose a middle tier when several players explore independently or when Paper plugins become part of the server. Use the largest tier for an established busy world or more demanding automation, and upgrade before sustained lag appears.
