How to make a Minecraft 1.8 PvP server: the old combat players still want

What does Minecraft 1.8 change for a PvP server?

Start with the word itself. PvP means player versus player: two people fighting in game, with swords, bows and potions. A PvP server is a server built around that, with arenas, ready made equipment kits and rules that stop anyone from hitting a player who just spawned in.

What makes 1.8 special fits in one sentence: in that version there is no delay between two hits. You click, you hit, and how fast you click matters. A later version changed that by adding a cooldown on attacks: you have to wait for the weapon to be ready to deal full damage, and hitting too early does less. Combat becomes slower, more measured, more about timing than about speed.

Neither one is better in the abstract. It is a matter of taste, and above all of habit. But people who have been doing PvP for years learned the rhythm of 1.8, they built their movement and their aim around that rhythm, and they do not find it anywhere else. That is why old combat Minecraft is still the reference for fighting, years after the version shipped, while the rest of the game moved on without it.

The consequence for you is direct. If you are building a combat server and you want that crowd, the version is not a technical detail, it is the product. If you are building a survival world for friends, 1.8 gives you nothing and costs you a lot. The rest of this page is here so you can call it with your eyes open.

• 1.8 combat has no delay between two hits: the click decides
• A later version added an attack cooldown, which changes the whole rhythm
• This is not technical superiority, it is a deeply rooted playing habit
• If your server is not built around fighting, 1.8 brings you nothing

Who still runs a Minecraft 1.8 server, and what do you give up?

Look at numbers rather than impressions. A public survey from 24 July 2026, covering 62,948 servers, lists the most used versions: 1.21.11 in front with 36 percent, then 26.1.2 with 15 percent, 26.2 with 7 percent, 1.21.4 with 7 percent and 1.21.8 with 6 percent. In other words, around 60 percent of servers still run the 1.21 branch and around 22 percent run the calendar branch, 26.x. Version 1.8 shows up in none of those top five places.

A word on those odd numbers while we are here. Since 2026, Minecraft Java uses calendar numbering: 26.1, then 26.2. Those are not typos, and the last version of the old series was called 1.21.11. Next to that, a 1.8 server belongs to a generation the game left behind a long time ago.

So what you gain is precise and narrow: the combat, and the players who come looking for it. What you give up is broad. No new content for years: not the blocks, not the mobs, not the biomes, not a single mechanic added since. A plugin catalogue that stopped moving, because developers maintain what runs on current versions. Tutorials and help threads that are dated, when they still exist at all. And a frozen server software, which is the next section.

There is one more consequence, less visible. A frozen version gets no fixes. Whatever was not repaired back then will not be repaired now. That is not a reason to drop the idea, it is a reason to take your moderation and your protections seriously instead of expecting the game to handle it for you.

• Survey of 24 July 2026 over 62,948 servers: 1.8 is not in the five most seen versions
• Around 60 percent of servers run 1.21, around 22 percent run 26.x
• You gain the combat and its crowd, you lose new content and maintained plugins
• A frozen version gets no fixes: your moderation carries more weight

Which Java version do you need for a Minecraft 1.8 server?

First, what Java means here. Minecraft Java Edition carries that name because the game is written in Java, a programming language. To run a server, your computer therefore needs Java installed, the way it needs a player app to open a video. And the Java version matters as much as the Minecraft version.

The rule is easy to remember: the older the Minecraft version, the older the Java it expects. A 26.x server requires Java 25. A 1.21.x server is happy with Java 21. Versions 1.18 to 1.20.4 want Java 17. A server older than 1.17, and 1.8 is one of those, expects Java 8. You download that Java 8 from adoptium.net, the site of the Adoptium project, which hands out a Java build called Temurin: it is free and there is no account to create. That is also the Java that Minax compiles with when a plugin targets this generation.

What happens if you get it wrong? Nothing dramatic, but you lose an evening. The server may refuse to start, or stop again right after launch, and the console, the text window where the server says what it is doing, prints a message about versions. Read it. It tells you what it expected. That is always faster than guessing.

One trap comes up again and again: several Java versions can live on the same computer. You can have Java 8 installed and still not be running it when you type the java command. If that happens, point at the full path of the Java you want instead of the bare word java, or start your server from a script that does it for you.

• A 1.8 server expects Java 8, the Java generation of its own era
• For comparison: Java 21 for a 1.21.x server, Java 25 for a 26.x server
• If the version does not match, the console names the one it wants: read the message
• Several Java versions can coexist: check which one actually runs

Which server software still exists for 1.8: Paper, Spigot or Bukkit?

A server software is the program that runs the world and accepts connections. Several exist, and they do not offer the same things. The official Mojang server, called vanilla, accepts no plugins at all: only datapacks, which are far more limited rule packs. If you want kits, arenas and commands, vanilla is not it.

On current versions the answer would be immediate: Paper. It is the most widely used server software, clearly faster than vanilla, and it accepts plugins written for Bukkit and Spigot, its ancestors. It is also the one Minax targets first. Except that Paper publishes nothing for versions 1.0 to 1.15, and 1.8 falls inside that range.

For a 1.8 server you are left with the older members of that family, Spigot and Bukkit, in the builds released at the time. They take the same plugins, they are slower than Paper, and above all they do not move any more. Purpur, a Paper variant with more settings, and Folia, another Paper variant that spreads the world across several processor cores, follow the same logic: what Paper does not publish, its variants do not publish either.

Two words to clear up a classic mix up. Fabric and NeoForge are for mods, and a modded server forces every player to install the same mods at home. That is not the same thing as a plugin server, which asks nothing of its players. Velocity is a proxy, a switchboard that links several servers together into a network, with a hub in front and game servers behind. Waterfall and BungeeCord, which used to do that job, are at the end of their life.

• Vanilla accepts no plugins, so it cannot become a custom PvP server
• Paper publishes nothing for versions 1.0 to 1.15, so nothing for 1.8
• That leaves Spigot and Bukkit in their 1.8 builds, frozen, with the same plugins
• Purpur and Folia are Paper variants: the same version limits apply
• Velocity links several servers into a network, it does not replace the server software

How do you set up your 1.8 server step by step?

Everything happens inside a single folder. You can start over by deleting it: nothing installs itself elsewhere on your computer, apart from Java. Here is what you see on screen, in order.

Once the server is running, your players get in with an address and a port. The address is either the public address of your connection, the string of numbers that identifies your router on the internet, or a domain name pointing at it. The port is the numbered door Minecraft knocks on: 25565 by default. Both are typed together, separated by a colon, under Multiplayer and then Add Server.

• 1. Install Java 8 and check that it really is the one running when you type the java command.
• 2. Create an empty folder, MyPvP for example, and put the .jar file of your 1.8 server software in it. A .jar is the format Java programs come in: here it is the whole server.
• 3. Run it once from a terminal, the window where you type commands, opened in that folder, with the java -jar command followed by the file name. The server stops straight away, which is normal: it just created a file called eula.txt asking you to accept the Mojang terms. Open it, replace false with true, save.
• 4. Run the same command again. The server generates the world and announces in the console that it is ready. Type stop to shut it down properly, never the window close button: a brutal cut can damage the world.
• 5. Open server.properties, the settings file created on first launch. Set pvp to true, then choose difficulty, maximum players and view distance. Leave online-mode on true, we come back to it in the mistakes.
• 6. Drop your plugins, .jar files made for 1.8, into the plugins folder the server created, then restart. Every plugin that loads announces itself in the console at startup, and an error shows up there too.
• 7. Join your own server from the same computer by typing localhost, the address that means this computer. Test your kits and your arenas alone before you open anything to anyone.

1.8 server hosting: where do you run it, and how much RAM?

Three families, with no brand ranking and no prices, because offers change all the time. On your own computer it costs nothing, but the machine has to stay on while the others play, and you have to open port 25565 on your router, which is called port forwarding. Tunnel tools such as playit.gg or ngrok get around that by handing you a public address. Hamachi, the old method, forces every player to install it too, so skip it.

With a host you pay every month and the server stays online when your computer is off. For a 1.8 server, two criteria come before all the others: the control panel has to offer old versions, and you need file access so you can upload your own plugins. Then add what matters for everyone: RAM that is genuinely dedicated, a fast processor core, a machine close to your players, downloadable backups, and protection against flooding attacks.

Free online services exist as well, with limits they own up to: a queue before the server starts, an automatic shutdown when nobody is playing, shared performance and a limited plugin catalogue, with file uploads allowed depending on the service, never on Aternos, which refuses plugins uploaded by hand. Above all, check that 1.8 is offered at all before you commit to anything.

On the hardware side, RAM is the working memory your server is allowed to use. On a combat server it is not what decides smoothness: one fast processor core often counts for more, because that core computes every hit and every step. Smoothness is measured in TPS, the number of game ticks per second, and the target is 20. The estimate below is an order of magnitude, never a guarantee.

ViaVersion, ViaBackwards, ViaRewind: which one lets who in?

This is where almost everyone gets it wrong, and it is worth reading twice. These three plugins have similar names and do different jobs. None of the three changes the version of your server: they only translate the conversation between a player's game and the server.

ViaVersion lets a newer client join an older server. That is exactly your case: installed on your 1.8 server, it lets in someone whose game is on 1.21 or on 26.x, without that person changing anything at home. The world, the blocks and above all the combat stay 1.8 for everyone, including for them.

ViaBackwards does the opposite: it lets an older client join a newer server. And ViaRewind reaches further down still. On top of the other two, it is what you need to welcome 1.8 and 1.7 clients onto a server running 1.9 or above. If you ever move your server to a current version and want to keep your 1.8 players, that trio is what you need, not ViaVersion on its own.

The thing never to forget: a plugin is compiled, meaning turned into a program, for one generation of server. A plugin built for 26.x does not load on a 1.8 server, and a 1.8 plugin does not necessarily load on a current one. No member of the Via family fixes that, because it is not their job: they handle players, not plugins.

• ViaVersion: a newer client joins an older server, which is your case on 1.8
• ViaBackwards: an older client joins a newer server
• ViaRewind: on top of the other two, for 1.8 and 1.7 clients on a 1.9 or newer server
• None of the three changes the server version or makes a plugin compatible

Which plugins make a kitpvp 1.8 server, and how do you ask Minax?

A brand new 1.8 server is an empty world with PvP switched on. What turns it into a combat server is the plugins you drop into the plugins folder. Ready made plugins, the Via family for example, come from two sites: SpigotMC, and Hangar, the plugin library of the team behind Paper. Mods are a different thing and do not belong in that folder: you find those on Modrinth and on CurseForge. The most requested format is called kitpvp: every player picks a ready made equipment kit, goes to fight, dies, respawns, starts again. No chests to fill, no preparation, just the fight.

A kitpvp 1.8 server stands on four bricks. Kits, with a waiting time between two pickups so nobody stockpiles them. A protected spawn point, where nobody can hit anybody, because otherwise new arrivals die before they have moved. Statistics, because a killstreak on screen makes people want one more round. And moderation, which counts double on a combat server.

Be clear eyed about that last one. An anticheat is a plugin that spots players who cheat. On a version as old and as picked apart as 1.8, cheaters know the ground by heart, and no plugin replaces moderators who are actually there. Plan the commands you will really use: warn, kick, freeze a player while you check.

With Minax you describe your plugin in plain English, the way you would explain it to a friend, and you get back a .jar compiled for your version, 1.8 included. From 1.12.2 to 26.2, you can then try it in game on an online test server, and a robot player can replay your scenario to check that the plugin does what you asked for; on 1.8, you try it on your own server. To create, a credit pack paid once, with no subscription: 50 credits for €17.99. At today's rates, we estimate that half of plugins come to between 15.4 and 30.7 credits, edits included, and that one in ten goes over 42 credits (estimate from 25/09/2026, not a guaranteed price). Here are three requests ready to copy.

Stay on 1.8 or move on: how do you decide honestly?

The right answer does not depend on fashion, it depends on your players. Ask yourself one question: do they come for the fighting, or do they come to play together? If they come for the fighting and they talk about click speed, stay on 1.8, you are giving them exactly what they are looking for. If they come to build, explore and discover, a current version gives them far more.

There is a middle road: run a server on a current version, then tune the combat with a plugin that recreates the no delay behaviour. That road gives you the new content, maintained plugins and an up to date server software, at the cost of tuning that you keep adjusting until the feel convinces your regulars. More work at the start, less upkeep afterwards.

If you do migrate one day, keep two things in mind. First, your 1.8 plugins will not follow as they are: you will need builds compiled for the new generation. Second, the players who stayed on 1.8 will need ViaBackwards and ViaRewind on your new server to keep getting in. Set both up before the announcement, not after.

And if you are still torn, there is a slow, sensible option: open a small 1.8 server for friends first, see whether the combat really is what brings you together, then decide. A server you close after a month costs less than a server you open in the wrong place.

• Your players come for the fighting: 1.8 is a coherent choice
• Your players come to build and explore: a current version gives them more
• Middle road: a current version plus a plugin that recreates combat with no delay
• If you migrate, plan ViaBackwards and ViaRewind for the players who stayed on 1.8

The mistakes that waste an evening on a 1.8 server

Almost every 1.8 server that refuses to start, or that disappoints, falls into one of these mistakes. They are quick to fix once you know where to look, and the console stays your best clue: it always writes down what went wrong.

• Starting a 1.8 server with a Java that is too recent: the server refuses to boot or stops right away. Read the console message, it names the version it expected.
• Hunting for a Paper build in 1.8: there is none, Paper publishes nothing for versions 1.0 to 1.15. Go through Spigot or Bukkit in their 1.8 builds.
• Dropping in a plugin compiled for a recent version: it does not load, and the console shows an error at startup. You need a plugin made for 1.8.
• Believing ViaVersion changes the server version: it does not. It lets players on another client in, nothing more. Your server stays 1.8, with 1.8 combat.
• Forgetting to protect the spawn point: on a combat server, newcomers get killed before they have moved, and they do not come back.
• Flipping online-mode to false so friends without an account can join: it is common, but it opens the door to name spoofing, where anyone can connect under somebody else's name. If you do it, know what you are taking on.
• Counting on an anticheat alone to hold the server together: on a version this old and this well known, nothing replaces moderators who are present and clear sanction commands.

Frequently asked questions