This guide walks you through setting up a Minecraft Java Edition server on Legion Hosting -- from choosing a server type to configuring your world and connecting with friends.
1. Choosing a Server Type
When you first set up your Minecraft server, one of the most important decisions is which server software to run. Each type offers different capabilities depending on whether you want plugins, mods, or a clean vanilla experience.
| Server Type | Best For | Plugin Support | Mod Support | Notes |
|---|---|---|---|---|
| Vanilla | Pure, unmodified Minecraft | None | None | Official Mojang server JAR. No customisation beyond server.properties. |
| Paper | Performance-optimised survival/SMP | Bukkit & Spigot plugins | None | Fork of Spigot with significant performance patches. Recommended for most servers. |
| Spigot | Plugin-based servers | Bukkit & Spigot plugins | None | The original high-performance Bukkit fork. Paper is generally preferred over Spigot today. |
| Forge | Modded Minecraft (large modpacks) | Limited (some via Sponge) | Forge mods | The classic mod loader. Clients must install the same Forge version and mods. |
| Fabric | Lightweight modding, newer mods | Limited | Fabric mods | Faster updates to new Minecraft versions. Growing mod ecosystem. Clients need Fabric + matching mods. |
2. First Start
- Log in to GPanel.
- Select your Minecraft server from the server list.
- Navigate to the Startup tab.
-
Choose your desired Server Type (Paper, Vanilla, Forge, etc.) and Minecraft Version from the dropdown menus.
Important: Make sure the version you select matches the version your players will be running. Mismatched versions will prevent clients from connecting.
- Click Start on the Console tab to launch the server for the first time.
-
The first startup will automatically:
- Download the selected server JAR
- Generate
server.properties,eula.txt, and other default configuration files - Generate the initial world (this may take a minute or two)
- Once you see
Done!in the console, your server is running and ready to configure.
eula.txt.
3. Configuring server.properties
The server.properties file controls most of your server's core behaviour. You can edit it directly from GPanel's File Manager -- click on the file in the root directory to open the built-in editor.
server.properties. Changes made while the server is running will be overwritten when it shuts down.
| Property | Default | Description |
|---|---|---|
server-name |
A Minecraft Server |
The name displayed in the server list (Bedrock only; Java uses motd instead). |
gamemode |
survival |
Default game mode for new players. Options: survival, creative, adventure, spectator. |
difficulty |
easy |
Server difficulty. Options: peaceful, easy, normal, hard. |
max-players |
20 |
Maximum number of players that can be connected simultaneously. Set this to match your hosting plan's player slot limit. |
pvp |
true |
Whether players can damage each other. Set to false for PvE-only servers. |
online-mode |
true |
Verifies player accounts with Mojang. Keep this set to true unless you have a specific reason to disable it -- disabling it allows cracked clients to join. |
motd |
A Minecraft Server |
Message of the Day shown in the Java Edition server list. Supports colour codes with \u00A7 (section sign). |
view-distance |
10 |
Render distance in chunks (1 chunk = 16 blocks). Lower values (6-8) improve performance; higher values (12-16) give a better visual experience at the cost of more RAM and CPU. |
spawn-protection |
16 |
Radius (in blocks) around the world spawn where non-operators cannot build or break blocks. Set to 0 to disable. |
level-seed |
(blank) | World generation seed. Leave blank for a random seed, or enter a specific seed to generate a particular world. Only applies when a new world is created. |
level-type |
minecraft\:normal |
World type. Options: minecraft\:normal, minecraft\:flat, minecraft\:large_biomes, minecraft\:amplified, minecraft\:single_biome_surface. |
white-list |
false |
When true, only players listed in whitelist.json can join. See the Whitelist section below. |
enable-command-block |
false |
Whether command blocks can be used. Required for many adventure maps and some minigame setups. |
After editing, save the file and start your server. The new settings will take effect immediately on startup.
4. Operator (Admin) Access
Operators (ops) have access to server commands such as /gamemode, /tp, /ban, /kick, and more. There are two ways to grant operator status.
Method 1: GPanel Console (Recommended)
From the Console tab in GPanel, type the following command while the server is running:
op YourPlayerName
You will see a confirmation message in the console. The player is now an operator.
Method 2: Editing ops.json
You can also manually edit the ops.json file in the server's root directory. Each entry looks like this:
[
{
"uuid": "player-uuid-here",
"name": "YourPlayerName",
"level": 4,
"bypassesPlayerLimit": false
}
]
The level field controls what the operator can do:
| Level | Permissions |
|---|---|
1 |
Can bypass spawn protection |
2 |
Can use cheat commands (/gamemode, /tp, etc.) and command blocks |
3 |
Can use player management commands (/ban, /kick, /op) |
4 |
Full access, including /stop and /save-all |
op grants level 4 by default. If you need a lower permission level, edit ops.json directly.
To remove operator status, use the console command:
deop YourPlayerName
5. Whitelist
The whitelist restricts your server to only approved players. This is useful for private servers or communities where you want to control who can join.
Enabling the Whitelist
Set the following in server.properties:
white-list=true
enforce-whitelist=true
The enforce-whitelist setting will kick any currently connected players who are not on the whitelist when it is reloaded.
Managing the Whitelist
Use these commands in the GPanel console while the server is running:
| Command | Description |
|---|---|
whitelist add PlayerName |
Add a player to the whitelist |
whitelist remove PlayerName |
Remove a player from the whitelist |
whitelist list |
Show all whitelisted players |
whitelist reload |
Reload the whitelist from whitelist.json |
whitelist.json in the server's root directory via GPanel's File Manager. Remember to run whitelist reload from the console after making manual changes.
6. How to Connect
Once your server is running, follow these steps to connect from Minecraft Java Edition:
- Find your server's IP address and port in GPanel under the Network tab.
- Open Minecraft Java Edition and click Multiplayer.
- Click Add Server.
- Enter a name for your server in the Server Name field (this is just a label for your server list).
-
In the Server Address field, enter your IP and port in the format:
your.server.ip:portFor example:
192.168.1.100:25565 - Click Done, then select the server from your list and click Join Server.
7. World Management
World Save Location
By default, the Minecraft world is stored in a folder called world in your server's root directory. This folder contains all of the world data including terrain, player data, and structures. You will also see world_nether and world_the_end folders for those dimensions (on Paper/Spigot servers; Vanilla stores them as subfolders inside world).
Uploading an Existing World
To upload a world from singleplayer or another server:
- Stop your server in GPanel.
- Delete or rename the existing
worldfolder using GPanel's File Manager (or via SFTP). -
Upload your world folder via SFTP. Make sure the folder is named
world(or update thelevel-nameproperty inserver.propertiesto match your folder name).Tip: For large world uploads, SFTP is much faster than the browser-based File Manager. See our SFTP guide for setup instructions. - Ensure the world folder structure is correct -- the
level.datfile should be directly inside theworldfolder, not nested in a subfolder. - Start the server. It will load your uploaded world.
%appdata%\.minecraft\saves\YourWorldName on Windows. Rename the folder to world before uploading.
Backups
It is strongly recommended to keep regular backups of your world, especially before making major changes like updating the server version or installing new mods/plugins.
To create a manual backup:
- Run
save-allin the GPanel console to flush all data to disk. - Stop the server.
- Download the
worldfolder (andworld_nether/world_the_endif they exist) via SFTP or the File Manager. - Store the backup in a safe location on your computer or cloud storage.