Spigot Server Hosting

What is Spigot, and who should choose it?

Spigot is a Minecraft Java server built on CraftBukkit that adds performance and configuration improvements while running the Bukkit API. It is developed by the SpigotMC community and has sat at the center of the plugin ecosystem for years: a large share of plugins are still written against the Spigot API first and published on SpigotMC.

To be straightforward about it, Paper is the better choice for most new plugin servers today. It runs the same plugins and copes with crowds more efficiently. There are still solid reasons to pick Spigot. If you develop plugins and want to prove your code works on the plain Bukkit/Spigot API, Spigot is the right test bed. If you want a server where vanilla mechanics stay as untouched as possible, Spigot leaves alone several vanilla behaviors that Paper disables by default. And if you're migrating a long-running server whose settings and plugins have been stable on Spigot for years, staying on the same software keeps the move simple.

What can you tune in spigot.yml and bukkit.yml?

Spigot's real strength is gathering settings vanilla never had into two files. The world-settings section of spigot.yml works per world. entity-activation-range decides how often animals, monsters and villagers beyond a certain distance from players get processed; lowering it relieves the CPU noticeably, although going too low can break farms. merge-radius combines dropped items and experience orbs to cut entity counts. mob-spawn-range controls spawn distance, and the percentages under growth set how fast wheat, sugar cane and other crops grow.

The messages section of the same file lets you rewrite the whitelist, unknown-command and server-full messages in your community's language. Under settings, timeout-time controls when the watchdog shuts down a frozen server.

bukkit.yml handles broader behavior: spawn-limits caps monsters and animals per chunk, ticks-per sets how often spawn attempts and autosaves happen, and allow-end toggles the End dimension. Restarting after changes is the safest way to apply them.

How much RAM does a Spigot server need?

Spigot spends more main-thread time than Paper on the same work, so set capacity targets a little more conservatively. For a light-plugin survival server, Bronze 4GB suits 5–10 players and Silver 6GB suits 10–20. With economy, land-claim and logging plugins, Gold 8GB fits 20–35 players and Platinum 10GB fits 35–50.

Past that point the CPU sets the ceiling, not memory. Chunk generation and loading on Spigot are far less parallel than on Paper, so TPS falls faster when several players explore new land at once. Pre-generating the world with a plugin like Chunky and pulling entity-activation-range to sensible values will do much more for a Spigot server than adding RAM.

If you're aiming beyond 50 players, consider moving to Paper before climbing to the Diamond and Emerald plans; your plugins will very likely keep working and you'll get more out of the same hardware. Xtreme 32GB offers far more than a single Spigot instance can put to meaningful use.

How do SpigotMC plugins and BungeeCord networks fit together?

SpigotMC's Resources section is the oldest and largest plugin archive in Minecraft, hosting premium plugins for sale alongside free ones. Always check the supported versions listed on a plugin's page before downloading: plugins that reach into Spigot internals (NMS) need an update for every major Minecraft release, and an outdated jar can throw errors the moment the server starts.

To gather several servers under one address, Spigot works natively with BungeeCord. Set bungeecord to true in spigot.yml and the server takes each player's real IP and UUID from the proxy; online-mode in server.properties is then turned off and the proxy handles authentication. If you prefer Velocity, note that Spigot doesn't support Velocity's modern forwarding, so choose legacy forwarding on the Velocity side. For security, make sure backend servers accept connections only from the proxy, otherwise someone could bypass it and log in under any name.

Can you move from Spigot to Paper, or back again?

Moving from Spigot to Paper is easy. Paper reads Spigot's config files and world format, and nearly all plugins keep working as they are. Back up first, swap the jar, start the server and check the console for warnings; Paper adds its own files to the config folder and spigot.yml and bukkit.yml stay in place.

The opposite direction is rougher. Paper hard-forked from Spigot at 1.21.4, and PaperMC has stated plainly that going back from Paper to Spigot is not guaranteed from that version on. Paper-only plugins won't load on Spigot at all. So before moving a world that has run on Paper for a while onto Spigot, take a backup and try it in a test environment.

Version upgrades call for the same care: confirm every plugin supports the new Minecraft release before you upgrade. Worlds only move forward: once opened on a newer release, they can't safely return to an older one.