Before You Start: What You Need to Decide

Before downloading anything, answer these three questions. They will shape every other decision you make:

1. What version and game mode do you want? Minecraft has a huge number of versions, and different players often have different versions installed. If you are playing with a friend group, agree on the version before you set anything up. Java Edition and Bedrock Edition are separate and cannot play together on the same server without special software.

2. How many players will be on at once? A casual server for 2 to 5 friends needs very little RAM (2 GB is fine). A server expecting 20+ simultaneous players needs significantly more. Start with your realistic peak and size accordingly.

3. Do you want plugins or mods? Vanilla survival is simplest to set up and maintain. Plugins (running on Paper or Spigot) add server-side features like economy, permissions, and anti-grief without requiring players to install anything. Mods (running on Forge or Fabric) add new content but every player must install the same modpack. For beginners, plugins are easier to start with.

Have clear answers before you proceed. Changing your mind later (especially switching from vanilla to a modded setup) often means starting from scratch.

Choosing Where to Host (Home vs Free Hosting)

You have two practical options as a beginner with no budget:

Home hosting means running the server on a computer at your house. The hardware is free but you need to configure port forwarding on your router (to let players connect), ensure your computer stays on whenever players want to join, and share your home IP address with players. If you are only playing with close friends who you trust and you play on a fixed schedule, home hosting is viable.

Free hosting services run the server on their hardware. You do not need to touch your router. The server address is not your home IP. The server stays available around the clock regardless of what your PC is doing. NetSkyway offers free Minecraft server slots with no queue system and no artificial sleep timers. You request a slot via Discord and get panel access within a short time.

For most beginners, free hosting is the better starting point. It removes the most technically complex parts of self-hosting (port forwarding, dynamic DNS) and gets you to a running server faster.

Picking Your Server Software (Vanilla for Beginners, Paper for Most)

The server software determines what features and plugins you can use:

Vanilla is the official Mojang server software. Download it from minecraft.net. It has no plugin support but is the simplest setup. Use vanilla if you want a pure survival experience with no extra features, or if you are running a modded server with Forge or Fabric (which replace vanilla with their own server).

Paper is the most popular choice for most servers. It is compatible with Spigot plugins, runs faster than vanilla, and fixes dozens of bugs and exploits. Download it from papermc.io. Paper is the right choice for 90% of servers that want to add plugins.

Fabric is the right choice if you want to run mods (especially newer technical mods). It requires all players to have the same Fabric mods installed on their client.

Forge is another mod platform, better for older modpacks (1.12.2 packs, many popular Technic-era packs). Same requirement: all players need the matching mods.

For a first server with friends, Paper is the recommendation. It works out of the box for survival, handles more players with less lag than vanilla, and lets you add plugins when you are ready.

Your First Five Minutes After Getting the Server

When you first start the server, it generates a world and writes out a set of default configuration files. Here is what to do in the first five minutes:

  1. Op yourself. Run /op YourUsername in the server console. This gives you operator (admin) status, letting you run commands in-game.
  2. Edit server.properties. Open the file in the panel's file editor. Set a meaningful motd (the description shown in the server list), set difficulty to your preference, and set max-players to something sensible for your group.
  3. Accept the EULA. On first start the server creates a file called eula.txt. Open it and change eula=false to eula=true. The server will not run until you do this.
  4. Restart the server to apply all changes. Use the Restart button in the panel, not Stop then Start, to ensure a clean reload.

Once the server is back up, join with your Minecraft client using the server address from the panel. You should spawn in the world and be able to play. That is your baseline: a working server. Everything from here is optional customisation.

Inviting Players and Setting Up a Whitelist

To invite friends, just share the server address shown in your panel. They add it to their Minecraft client's server list, and if you are on the same version they can connect immediately.

If you want to restrict access so only specific players can join, enable the whitelist. Run these commands in the server console:

/whitelist on
/whitelist add FriendUsername

Add each friend's username with /whitelist add before they try to connect. Players not on the whitelist will see a "Not whitelisted on this server" error when they attempt to join. This is the simplest form of access control. There is no password system in vanilla Minecraft; whitelist is the standard method.

If you are using Paper and want more control (different permissions per player, ranks, etc.), look into EssentialsX and LuckPerms. But for a small friends-only server, the vanilla whitelist is all you need to start.

Common Beginner Mistakes and How to Avoid Them

A few mistakes come up almost universally for first-time server owners:

Version mismatch: The server version and your Minecraft client version must match exactly. If your server runs 1.21.4, everyone connects with 1.21.4. Check the version before you send the address to anyone.

Not opping yourself: The first time you join your own server, you are a regular player with no admin permissions. Run /op YourUsername in the server console (not in the game chat) to give yourself operator status.

Editing server.properties while the server is running: Changes to server.properties only take effect after a restart. If you edit the file and wonder why nothing changed, restart the server.

Using too little RAM: The default memory allocation on most hosting panels is fine for 2 to 3 players but may cause lag with more. If you notice chunk loading delays or entity lag, ask about increasing your RAM allocation.

Skipping backups: Worlds get corrupted. Griefers happen. Set up automated backups early. Most panel interfaces including NetSkyway's have a built-in backup system. Enable it and schedule a daily backup before you discover why backups matter the hard way.