A frequent question: how many plugins can I install on my package? The answer is more flexible than you’d think.

The count limit is gone; guidance remains

There is no hard cap on how many plugins or mods you can install. The panel shows a recommended number for your package and RAM; go past it and you only see a reminder that performance may suffer — nothing is blocked.

In the Plugins section that recommendation is an information line; once your installed count passes it, the line turns into a warning naming how many are installed. Going over does not disable the Install button. On 8 GB and above the line never appears, because there is no recommendation there.

The system files we install — speed measurement and the cross-play bridge — don’t count and aren’t shown in the list.

Why show a recommendation at all?

Every plugin uses memory and adds work to each tick. The recommendation marks the range where holding 20 TPS is comfortable on that package’s resources; load grows with the player count, so going over is usually paid for on your busiest evening.

What really matters: weight, not count

Focusing on the number is misleading: one badly written or heavy plugin can cost more than ten light ones. Plugins that run constant scheduled work, hold large datasets or render maps fall into that group.

So when the server gets heavy, don’t blindly cut the count — find which one generates the load: disable the suspect and watch TPS. Disable several at once and the result is unreadable.

The power button in the installed list doesn’t delete anything; it turns the file off and back on. The change lands on the next restart, and a restart inside the same hour is not charged a second hour upfront.

Where the real ceilings are

Instead of counting files, watch what genuinely runs out: RAM, the cores allocated to you and disk. A plugin that renders map tiles or grows a database can fill your package’s disk quota (Starter 10 GB, Standard 20 GB, Pro 30 GB). One setting is genuinely hard-capped: view distance. The view and simulation distance fields under Settings are capped per package — a higher value won’t save — and the cap rises with the package. The player-count field is not: a value above the recommendation still saves, with a warning.

Where to measure

Live TPS is on the panel’s Overview screen; the figure is the average of the last minute. Right after a start it reads as warming up for a few minutes. If the last minute held a stall longer than one second, the longest stall appears under the same tile — one long stall drops players even when the average looks fine.

TPS is measured on plugin-capable software (Paper, Purpur, Spigot, CraftBukkit); on Vanilla and the mod loaders the gauge stays empty. TPS is the server’s own speed, unrelated to your internet connection. For a look back, search log records in the Logs section.

The diagnostic order and the highest-impact settings are in the performance guide.

If the server got heavy, check in this order

  1. On Overview, is CPU climbing or RAM filling? High CPU alone usually means a plugin doing constant work; full RAM, one holding a large dataset.
  2. Read the startup lines in Logs: a plugin built for another version may have failed to load quietly.
  3. Disable the one you added most recently, restart, watch for ten minutes. If the problem goes away, you have your answer.
  4. If not, turn it back on and repeat with the previous one — one at a time.
  5. If none is guilty, drop the view distance one step — usually the cheapest win.
  6. If it really is a resource shortage, grow the package from Resources; your world stays as it was.

Common mistakes

  • Skipping the restart. A file you installed, deleted or disabled takes effect only after a restart; steps in the plugin install guide.
  • Leaving the software in the wrong family. Vanilla runs neither plugins nor mods: plugins need Paper, Purpur, Spigot or CraftBukkit, mods need Fabric, Quilt, Forge or NeoForge — change it from the Software section.
  • Reading idle sleep as a crash. With no players for 15 minutes the server sleeps; the reason is written into History, details in the sleep mode article.
  • Installing two plugins that do the same job. Two protection or two economy plugins overwrite each other’s settings.

The real threshold, on the mod side

Plugins have no count threshold, but mods have a package threshold: mod and modpack installs unlock from 8 GB. On 2 and 4 GB you install plugins, not mods.

The store changes with the family too: plugin searches scan SpigotMC and Modrinth, plus PaperMC Hangar on Paper and Purpur; mod and modpack searches come from Modrinth.

Which way to go

  • A few friends on a survival world: the entry package is comfortable and won’t reach the recommendation.
  • Busy evenings with protection and economy stacked up: look at cores before RAM — plugin work runs on the main thread.
  • Planning mods or a modpack: start at 8 GB directly; below that the section doesn’t open.
  • Friends joining from a phone, tablet or the Windows edition: you need software from the plugin family, Minecraft 1.20.5 or newer, and at least 4 GB.