In the web interface under Server → Main server → Plugins you see all MRtechnology plugins as a table: at the top the ones on your server with installed version, channel, latest version in the channel (badge Up to date when it is installed, New when not) and whether an update is waiting, below that the rest. A click on an installed plugin opens its page with "What's new".
Channels: stable, beta, dev
Every plugin follows a channel - switch it in the column Channel (mradmin.versions.install):
| Channel | What comes | For whom |
|---|---|---|
| Stable | stable versions only (STA-…) |
every server - default |
| Beta | also betas (BET-…) - new features earlier, not quite finished |
if you want to try new things early |
| Dev | every development build (after every commit), unfinished | test servers only, only with the release token |
- Without a choice of its own a plugin follows the default channel
versions.channel(stableorbeta); "back to default" removes the own choice. 0.x plugins only exist as beta and always get betas. - Back to stable never downgrades: a running beta or dev build stays until a newer stable version comes (older versions could not handle the settings that were already migrated).
- Protection against steps back - for every channel, also for
versions.auto-download:- If the offered version has a lower
config-version(config.yml) orlang-version(language files) than your server, it is not installed: your settings were already migrated by a newer version. - If the running and the offered build both come from GitHub (all releases and dev builds), the offered one must be a successor of the running one. Important after dev: a dev build carries the number of the last release - a later hotfix would look "newer" but would remove the features of the dev build again. It is offered only once it contains the dev state.
- Blocked versions show "Step back blocked" with the reason on the page. If you really want to go back, do it by hand: put the old JAR in and restore the
config.ymlfrom a backup (config.v<number>.backup.yml).
- If the offered version has a lower
- Stable is greyed out as long as there is no stable version yet (plugins with only betas so far, 0.x). Beta can always be chosen - it also gets the stable versions, so you can stay on beta even while a stable is the newest.
- Dev only appears when a valid release token is in the configuration (
versions.dev-token, you get it from the developer). If it is wrong, dev stays hidden and the page shows a note. The dev builds lie sealed in the GitHub releasemc0-dev; MRadmin opens them with the token and checks the checksum. A plugin that runs a dev build is marked with Dev and the commit (e.g.Dev c44ebd6).versions.auto-downloadfetches dev builds by itself only withall.
Install
You install plugins that are not installed yet with one click (mradmin.versions.install). MRadmin downloads the official release for your Minecraft version (only with a matching checksum) into plugins/ - it is loaded on the next restart. What gets installed is what the channel of the plugin offers (see above); if there are only pre-releases so far (e.g. MRpvp 0.x), the newest of them.
Configure in the browser
Every server has the tab Configuration (Server → Main server → Configuration or Server → Waiting room → Configuration, mradmin.config, in mradmin.groups.admin), with one tab per plugin of that server: all settings of config.yml as a form with explanations (German/English). Saving checks every value, writes the file (comments stay, the old file is kept next to it as config.backup-web.yml) and reloads the plugin right away - without a command, without a restart. Editing by hand still works. Available for MRadmin and all MRtechnology plugins in a current version.
Watching other plugins
Under Plugins every server has two tiles: MRtechnology plugins (managed as above) and Other plugins - all remaining plugins of the server (e.g. LuckPerms, LibertyBans), for the main server and the waiting room each on its own. MRadmin does not update them, but can watch them:
Automatically: MRadmin asks Modrinth with the fingerprint (SHA-1) of every plugin JAR. If Modrinth knows the file, the project shows with "auto" in the column Source - and MRadmin knows exactly which version is installed.
By hand: A click on the source opens a window (permission
mradmin.versions.install): tab Modrinth with a search (results show whether there are versions for your Minecraft version) or GitHub (owner/repoor the github.com address). Below it shows before saving which version MRadmin would compare with. Find automatically goes back to the fingerprint, Do not watch switches the lookup off for the plugin.Matching the Minecraft version: On Modrinth the newest version is the newest one for the server's Minecraft version and a Paper-compatible loader (Paper, Spigot, Bukkit, Purpur, Folia). On GitHub the newest release that names the Minecraft version (name, text or file names) - if none names it, the newest release with the hint Minecraft version not stated. If there is nothing for the version at all, it says No version for Minecraft ….
Channel Stable | Beta: In the window you choose per plugin whether only releases count (Stable, default) or betas too (Beta) - also for plugins found automatically, which stay "auto". If there are only betas for the Minecraft version, Stable says Only betas for Minecraft …. In the table a small Beta next to the source shows the channel.
MRadmin checks every 6 hours (after 15 minutes again on errors) and shows Current or New. Plugins with a newer version are at the top.
Order
The MRtechnology plugins are sorted by urgency: errors and updates at the top, then what waits for a restart, current plugins at the bottom.
Updates
- Download (
mradmin.versions.install) gets the new version from the official release on GitHub - only for your Minecraft version and only if the checksum (SHA-256) matches. It goes toplugins/update/, it is installed on the next restart (Paper does that itself). Nothing is swapped while the server runs. - The file name stays the old one (e.g.
MRsleep-mc26.3-v1.1.5.jarwith version 1.2.0 inside) - only this way Paper knows which plugin is replaced. Which version runs is shown under Server → Main server → Plugins or with/<plugin> version. - Automatically:
versions.auto-download: patchdownloads e.g. hotfixes (1.2.x) by itself,minoralso new features,alleverything. The default isoff. - It is checked every
versions.check-interval-hoursand with Check now (mradmin.versions.install). - Downloads and restarts are recorded in the log and the Discord log (
plugin-update-downloaded,server-restart).
Restarting the server
Easiest with the starter built into MRadmin: it starts the server again after every restart, crash or hang, installs Paper updates and can restart daily. Then you do not need
versions.restart-method; you can also restart at any time with/mradmin restart.
After a download or installation the page shows "Restart needed". A restart button (mradmin.server.restart) with a countdown (versions.restart-delays, default 15, 30 and 60 minutes, announced like /mradmin announce restart; shorter times only through the Emergency button after signing in again and with a reason, versions.emergency-delays) only exists while an update or a newly installed plugin waits for the restart, and only once you set versions.restart-method - because a server cannot start itself again, something outside has to do it:
versions.restart-method |
What happens |
|---|---|
none (default) |
no button |
stop |
The server stops, and your start script with a loop, a watchdog or your host's panel starts it again |
script |
The server restarts via the restart-script from spigot.yml (settings.restart-script) |
Only set
stoporscriptif you know for sure that the server comes back up afterwards - otherwise the button only stops it. Many host panels do not restart by themselves after a normal stop, only after a crash. Try it once before you use the button when it matters.
Example: start script with a loop (for restart-method: stop)
The script starts the server again 5 seconds after every stop. To quit for good, press Ctrl+C during these 5 seconds.
Linux (start.sh, make it executable with chmod +x start.sh, e.g. start it in screen or tmux):
#!/bin/sh
while true; do
java -Xms4G -Xmx4G -jar paper.jar --nogui
echo "Server stopped - restarting in 5 seconds (Ctrl+C to quit)"
sleep 5
done
Windows (start.bat):
@echo off
:loop
java -Xms4G -Xmx4G -jar paper.jar --nogui
echo Server stopped - restarting in 5 seconds (Ctrl+C to quit)
timeout /t 5
goto loop
Adjust the memory (4G) and the name of the Paper JAR to your server.