Start with the gamemode core

Slimefun is the gameplay core of this technology-style server. Land protection, logging, money and staff tools support it but should not be confused with Slimefun expansions or research.

Research and machines

Start with Slimefun on a supported server build. On a test world, unlock a basic item and run one machine through an input/output cycle. Confirm chunk unloading, world backups and machine persistence, particularly before adding third-party Slimefun addons.

Claims and recovery

GriefPrevention handles claims, CoreProtect logs supported block/inventory actions and InventoryRollbackPlus deals with player inventories. Test whether the protection/logging plugin tracks a chosen Slimefun machine correctly; custom-block data may need the Slimefun database backup.

Money and shops

A shop system can sell Slimefun materials but should not bypass progression by accident. Test purchase/sell prices and whether custom items keep their metadata after a transaction.

Roles and integration

LuckPerms manages commands, PlaceholderAPI exposes supported integrations and PlayerWarps adds travel. Test permissions using a fresh account with no operator privileges. Schedule backups for both world files and Slimefun plugin data.

How to choose the stack

Begin with Slimefun and backups. Add one claim plugin after testing custom machine interactions. Only introduce economy or rewards once you know what should be obtainable without research.

  1. Download each selected plugin from its official publisher and verify the exact server/version requirements.
  2. Start a disposable staging world; inspect startup logs and dependency warnings before inviting players.
  3. Test the main gameplay loop as a non-operator, including failure and restart cases.
  4. Back up plugin data and world files, document ownership of each feature, then expand the stack one component at a time.
Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000