How to Make a Modded Minecraft Server

For two or three people on the same continent, self-hosting is perfectly reasonable. The server runs beside your game, you already own the hardware, and there is nothing to pay.

Past that, the economics shift. A modded server needs 4GB to 8GB of RAM entirely to itself, which is memory your own game no longer has. Your upload bandwidth — usually a fraction of your download speed — is what every other player's connection quality depends on. And the world only exists while your PC is on.

Renting solves all three for roughly the price of a coffee per month, and the modpack installs with one click rather than a manual file copy.

Download the server files for your loader. NeoForge and Forge both publish a server installer alongside the client one; Fabric offers a server launcher from its download page. Put it in its own empty folder — the server generates a dozen files on first run and you do not want them loose in Downloads.

Run the installer with the server option, which produces a start script and a jar. Run that once. It will stop immediately and write a file called eula.txt.

Open eula.txt, change false to true, and save. This is Mojang's licence acceptance and the server refuses to start without it. Run the start script again and the world generates.

Now stop the server and add your mods to the server's own mods folder — a different folder from your client's. Server and client mod lists must match for anything that adds content.

Anyone on your own network can connect immediately using your local IP. Getting people in from outside requires port forwarding: log into your router, forward TCP port 25565 to your computer's local IP, and share your public IP with your friends.

This is where self-hosting most often stalls. Router interfaces are inconsistent, some ISPs use carrier-grade NAT which makes port forwarding impossible without paying for a static IP, and getting it wrong exposes more than you intended.

Playit.gg and similar tunnelling services sidestep the whole problem by giving you a public address without touching your router. They add a little latency and are the pragmatic choice if your router is fighting you.

Memory is the resource that decides whether a modded server feels good or terrible, and it scales with mod count far more than with player count.

A vanilla server is comfortable on 1GB. A light mod list of thirty or forty mods wants 3GB. A mid-size modpack in the hundred-mod range needs 4GB to 6GB. Large kitchen-sink packs — the three-hundred-mod ones — want 8GB and will use more if you give it to them.

Add roughly 500MB per concurrent player beyond the first four. The symptom of being short is not a crash but a slow degradation: chunks load late, mobs stutter, and the console fills with warnings that the server cannot keep up.

Every player needs the same mods at the same versions as the server for anything that adds content. Mismatches produce a connection error naming the offending mod, which is at least informative.

The clean way to manage this is a modpack. Publish yours to CurseForge or Modrinth, or export it as a file and share it — each player imports it once and their setup matches by construction.

The manual way is to zip your client mods folder along with a text file listing versions and send it round. It works for four people and stops working around eight.

Client-only mods are the exception and do not need to match. Shaders, minimaps and performance patches live entirely on the player's machine and the server neither knows nor cares.

Ignore the marketing and check three things. First, whether the host offers one-click installs for the pack you want — this turns an evening of file copying into thirty seconds. Second, how much RAM the plan includes, using the table above rather than the host's own player-count estimates, which are generous. Third, where the servers physically are, because latency is geography.

Billing is usually monthly with no contract, so a bad choice costs one month rather than a year.

Modded worlds break in ways vanilla worlds do not. Removing a mod that added blocks leaves holes; a mod update can change how its data is stored and corrupt a save.

Rented servers almost always include automated backups — find the setting and confirm it is on rather than assuming. Self-hosted servers back up nothing by default, so copy the world folder on a schedule.

The habit worth building: back up before every mod change, not on a timer. The moments that destroy worlds are almost always the moments you edited the mod list.

A modded server that feels bad usually is not short of raw power — it is spending its time badly. Before upgrading anything, look at what the console is telling you.

The message 'Can't keep up! Is the server overloaded?' means a tick took longer than the 50ms it is allowed. Occasional instances during world generation are normal. Continuous ones mean something is wrong.

The first lever is view distance. It is set in server.properties and it is quadratic — dropping from 12 to 8 chunks removes more than half the work. On a modded server, 8 is usually plenty and the difference is barely noticeable in play.

The second is simulation distance, which controls how far away entities and blocks keep ticking. Lowering it to 6 stops the server simulating farms nobody is standing near.

Only after those two should you look at mods. Profiling tools like Spark identify which mod is consuming the time, and the answer is frequently a single chunk-loading or worldgen mod rather than the pack as a whole.

A server with an open port will eventually be found. Automated scanners sweep the default Minecraft port continuously, and an unprotected modded server is an attractive target because griefing it destroys a lot of work.

Whitelisting is the answer and it takes one command. Set white-list to true in server.properties, then add each player with the whitelist add command from the console. Nobody not on the list can connect, regardless of whether they know your address.

Set op status deliberately too. Operators can do essentially anything, and handing it out casually to friends is how servers get accidentally flattened. There is no undo for a creative-mode misunderstanding.

If you self-host, remember the port you forwarded points at your home network. Whitelisting protects the game; it does not make the exposure disappear, which is a reason to prefer a tunnelling service or a rented server if that bothers you.