Mods and plugins let you shape a Minecraft server around the way your group likes to play. Before installing one, match it to your server software and Minecraft version, back up the world, then test the change before inviting everyone back.
Start with the server runtime
Check the server software shown in your settings. Paper is the plugin-oriented option. Fabric, Forge, NeoForge, and Quilt use their own mod-loader ecosystems. Vanilla runs the standard server and does not load those mods or Paper plugins.
Choose an extension released for your Minecraft version and server software. Read its release notes and dependency list before installing it: a Fabric mod will not necessarily work with Forge, and plugins are different from mods.
Know whether players need it too
Some mods run only on the server. Others require every joining player to install the same mod, loader, Minecraft version, and sometimes the same dependency versions. Explain that requirement before a group update. A client mismatch is a frequent cause of a connection failure even when the server is healthy.
Back up before consequential changes
Create a backup before installing, removing, or updating extensions, especially when a change affects world generation, items, blocks, or player data. A backup gives you a recovery point if you need to return to the previous setup.
Use the Minecraft Java Backups guide for backup instructions. Keep important backup copies somewhere you control.
Install in small, verifiable steps
For supported mod-loader servers, open Mods to find compatible Modrinth results, install a selected mod and dependencies when offered, update or remove mods, or upload a `.jar` file. Search results are filtered for your server software and Minecraft version. Check each mod’s details as well, especially whether players need to install it on their own computers.
For Paper, use the Plugins area and choose plugins made for Paper and your Minecraft version. Keep plugins in that workflow rather than adding them as mods.
The Mods guide walks through the manager’s mod controls.
Restart and validate
After adding, removing, or updating an extension, restart the server. Check Console and Logs for startup errors, then join using the same client setup your players will use. See the Console and Logs guide for help reading server output.
Check a small set of real actions: join the world, load an existing area, use the changed feature, and confirm any dependent content is present. For a community server, test before announcing the update.
Troubleshooting common failures
The server will not start. Review the earliest relevant error in the console. A missing dependency, wrong Minecraft version, or wrong loader is more likely than a random hardware issue. Remove the most recent change only after preserving logs and a backup.
Players cannot join. Compare their Minecraft version, loader, required client mods, and mod versions with the server. Server-side-only and client-required extensions have different expectations.
Blocks or items are missing. Do not keep playing through it. A removed or incompatible content mod can affect a world. Restore a known-good backup or return to the compatible extension set after checking the documentation.
The server becomes slow. Observe CPU and memory under normal activity. A problematic extension, entity-heavy build, or new-world generation may be involved. The Resources guide explains how to review usage before changing an allocation.
Updating safely over time
Before using Update All, check the release notes for your Minecraft version and server software, make a backup, and plan time to test. For a major Minecraft upgrade, update the server software, extensions, and clients as a coordinated change; they may not all support the new version at the same time.
For current server-creation options and an estimate based on your own resources and running time, see Minecraft Java hosting.
