Meet NusaSpigot
Set up your server, understand its settings, and look after your players’ worlds.
NusaSpigot is a Minecraft Java Edition server built on Paper. The current project targets Minecraft 1.21.11 and Java 21. Existing Bukkit, Spigot, and Paper API signatures are preserved. Each plugin build and combination still needs testing.
Start your first server
Follow these steps until your server starts and you can test it privately.
- Prepare your machine. Check the requirements and install Java 21.
- Start the server. Get the official JAR, create a start script, and complete first startup.
- Review your settings. Use the setup wizard, read the changes, then restart.
- Check before inviting players. Complete the launch checklist and test a backup restore.
Already running Paper?
Start with the migration guide. Read the zstd rollback limits before replacing your JAR.
Jump to a reference
| What you need | Where to look |
|---|---|
| Find a YAML setting | Configuration index |
| Check commands and permissions | Command reference |
| Understand server load | TPS, MSPT, heap, and module timings |
| Investigate a plugin | Doctor and plugin troubleshooting |
| Fix a failed startup | Startup troubleshooting |
How the server works
NusaSpigot keeps one real main server thread. World, entity, player, and block-entity changes happen there. Workers handle permitted I/O or computation on detached immutable snapshots. Results affecting game state return to the main thread.
Some controls change visibility, movement update smoothness, or gameplay. Start with the defaults, change one thing at a time, and measure your own workload. There is no universal player-capacity or TPS guarantee.
Using these docs
The sidebar groups guides by task. Use Search the docs or Ctrl K to find commands, settings, and terms. The table of contents helps you move through longer pages.
Console examples omit /; in-game commands include it. File names, YAML keys, and permissions match the implementation. The glossary explains terms such as tick, heap, and snapshot.
Access links and activation instructions are provided to licensed buyers. Public docs do not contain the customer portal address, credentials, or internal test archives.