DDoS-Protected Spigot Server Hosting

Why choose Spigot over a fork?

Spigot is the reference plugin platform. It carries the largest Bukkit plugin ecosystem of any server type, so almost every plugin you find targets its API first. When a critical plugin misbehaves on a performance fork, Spigot is the compatibility baseline you can fall back to.

Spigot descends from CraftBukkit and implements the Bukkit API that most third-party plugins are written against. A plugin that names Spigot or Bukkit in its requirements will load without surprises, because you are running the exact API surface it was built and tested on. That predictability is the whole reason the platform stays popular for plugin-heavy servers.

Legacy compatibility is the second reason. Plugins abandoned years ago often still load on Spigot, where a fork may have changed the internals those plugins reach into. If your server leans on an old economy, protection or minigame plugin that no one maintains anymore, Spigot is the safe place to keep it running.

The trade-off is performance headroom. Forks such as Paper apply aggressive patches that raise TPS under load, while Spigot stays closest to reference behaviour. Pick Spigot when correctness and compatibility matter more than squeezing out the last few ticks per second.

How do we tune spigot.yml?

We ship every Spigot server with a spigot.yml tuned for tick stability rather than the install defaults. Four settings move the needle most: view-distance, entity-activation-range, the ticks-per hopper and spawner values, and merge-radius. Each trades a little visual range or immediacy for a shorter, steadier tick.

• view-distance — lowered so the server keeps fewer chunks loaded and sends less per player. This is the single biggest lever on a crowded world.
• entity-activation-range — the radius at which distant mobs tick is reduced, so idle animals and monsters stop burning CPU far from any player.
• ticks-per.hopper-transfer and hopper-check — raised so hoppers poll less often, which cuts the cost of large item-sorting builds.
• merge-radius (item and exp) — widened so dropped items and XP orbs combine into fewer entities, shrinking the entity count after big fights and farms.

The exact starting numbers depend on the Minecraft version and your player profile, so we confirm them per build rather than paste a single set for every server:

# spigot.yml — starting point we apply (values confirmed per version)
world-settings:
  default:
    view-distance: {{CONFIRM_ACTUAL_DEFAULTS}}
    entity-activation-range:
      animals: {{CONFIRM_ACTUAL_DEFAULTS}}
      monsters: {{CONFIRM_ACTUAL_DEFAULTS}}
    ticks-per:
      hopper-transfer: {{CONFIRM_ACTUAL_DEFAULTS}}
      hopper-check: {{CONFIRM_ACTUAL_DEFAULTS}}
    merge-radius:
      item: {{CONFIRM_ACTUAL_DEFAULTS}}
      exp: {{CONFIRM_ACTUAL_DEFAULTS}}

Spigot is distributed as a build recipe, not a finished download. Our panel runs BuildTools for you and keeps a jar for each supported Minecraft release, so a version bump is a one-click swap rather than a local compile. When a new 1.21.x point release lands we build it and add it to the installer; your world and plugins stay in place.

How does DDoS protection work for a Spigot server?

Every Spigot plan sits behind 3.2 Tbps of always-on L3, L4 and L7 mitigation at our Frankfurt edge, with detection under one second and no traffic rerouting. We run deep packet inspection tuned for the Minecraft protocol, so malformed and forged game traffic is dropped upstream before it reaches your server. There is no separate DDoS add-on to buy.

That covers the network layer. Bot joins that complete a real handshake are an application-layer problem for your anti-bot plugin and proxy, not the edge. For the full picture across host firewall, server software and edge filtering, read how to protect a Minecraft server from DDoS. If you must keep the server on another host, route its traffic through our scrubbing edge with remote DDoS protection for Minecraft.

What is in the control panel?

Every plan runs on Pterodactyl. You get a one-click jar and version swap, snapshot backups with single-click restore, a free subdomain and full SFTP access to the file system. Subusers with granular permissions let you hand staff exactly the access they need and nothing more.

• One-click swap between Spigot builds and Minecraft releases, straight from the installer.
• Snapshot backups you can restore in a click before a risky plugin or version change.
• SFTP for bulk plugin and config uploads without a web file manager in the way.
• A free subdomain, or point your own domain at a dedicated IPv4 with the native 25565 port add-on.

Should you run Paper instead of Spigot?

Run Paper if raw TPS under load is your top priority; run Spigot if plugin compatibility and predictable reference behaviour matter more. Both share the same world format and most plugins, so the decision is about performance headroom versus compatibility, not a lock-in.

How do you launch a Spigot server?

Three steps take you from checkout to a joinable address. The panel handles the Spigot build and the network handles protection, so there is nothing to compile or firewall by hand.

1. Pick a plan above and check out. Your server is provisioned on the Ryzen 9 7950X3D fleet within seconds.
2. In Pterodactyl, select the Spigot build for your Minecraft version from the one-click installer and start the server.
3. Upload your plugins over SFTP, share your subdomain or dedicated IP, and set subuser permissions for your staff.

Spigot hosting FAQ