Extra Information
Once LoopMC starts successfully, use this page for branding and external services. Start with branding, then use the sections below for currencies and other setup features.
For the current native Minecraft/Paper version, use the Resource Versions page.
Add your branding
The visible server name, IP, store link, Discord link, vote links, and branding colours are controlled by AtomatrixCore. Edit /plugins/AtomatrixCore/placeholders.yml, then run:
/atomatrixcore reload
Only replace the values after each setting. Keep the setting names and YAML punctuation intact.
Change the server list appearance
Edit /plugins/MiniMOTD/main.conf to change the two lines shown in the multiplayer server list.
Replace server-icon.png in the server's main directory to change the icon. The replacement must be a 64×64 PNG with the same filename.
Configure external services
Voting
Configure NuVotifier with the token, address, and port supplied by your voting sites or proxy. Then update the public vote destinations in /plugins/AtomatrixCore/placeholders.yml.
DiscordSRV
Add your bot token and channel IDs to /plugins/DiscordSRV/config.yml. If you do not want Minecraft–Discord chat integration, remove the DiscordSRV JAR while the server is stopped.
Tebex
Create a server on Tebex, connect its secret key, then create packages for the three LuckPerms rank commands shown above. Test purchases with a non-staff account before opening the store.
Anti-cheat and EULA
The setup does not include an anti-cheat because server owners have different performance and moderation requirements. See Installing an Anti-Cheat for options.
Review EULA Compliance before selling ranks, Gems, keys, or other benefits. Recheck your store whenever you change rank perks or competitive rewards.
Essential player commands
| Command | Purpose |
|---|---|
/guide | Opens the main server guide |
/rtp | Teleports into the survival world |
/shop and /sell | Opens the shop or sells items |
/teams | Manages a team |
/safe | Stores eligible items that survive a season reset |
/purge | Shows Purge requirements and ticket availability |
/achievements | Shows seasonal achievements and claimable Battle Pass XP |
/rewards | Opens daily and rank rewards |
/ranks | Displays supporter rank perks |
Manage money and Gems
Normal money is managed through the Vault economy. EssentialsX provides the administration commands used by this setup:
/eco give <player> <amount>
/eco take <player> <amount>
/eco set <player> <amount>
Gems are the premium currency and are managed by PlayerPoints:
/points give <player> <amount>
/points take <player> <amount>
/points set <player> <amount>
/points look <player>
PlayerPoints data is deliberately preserved by the standard season reset, so players keep their Gems between seasons.
Configure the shop and rewards
- Edit shop categories and prices in
/plugins/EconomyShopGUI/shops/. - Edit the daily and weekly rank rewards in
/plugins/AxRewards/menus/default.yml. - Edit automatic announcements in
/plugins/Infiniteannouncements/announcements.yml. - Edit crate contents in
/plugins/ExcellentCrates/crates/and crate keys in/plugins/ExcellentCrates/keys/. - Edit Battle Pass rewards in
/plugins/BattlePass/BattlePassFREE.ymland/plugins/BattlePass/BattlePassPREMIUM.yml.
After editing a plugin, use that plugin's supported reload command or restart the server. Avoid /reload, which is unsafe for many Paper plugins.
Supporter ranks
Every player starts with three homes, 15 auction listings, five active market orders, and two safe slots. The paid ranks are permanent and inherit the perks of the rank below them.
| Rank | Homes | Auction slots | Order slots | Safe slots | Extra commands | Weekly reward |
|---|---|---|---|---|---|---|
| Drifter | 5 | 20 | 10 | 3 | /craft, /recipe | $300 and 5 Gems |
| Reclaimer | 6 | 25 | 15 | 4 | /disposal, /near, /hat, /feed | $750 and 15 Gems |
| Loopbreaker | 7 | 30 | 20 | 5 | /enderchest, /heal, /ptime, /pweather | $1,500 and 25 Gems |
Use LuckPerms to assign or remove a rank:
/lp user <player> parent add/remove drifter
/lp user <player> parent add/remove reclaimer
/lp user <player> parent add/remove loopbreaker
The seasonal safe
Players use /safe to protect a small number of eligible items from the next reset. The default setup provides two slots to everyone, then unlocks one additional slot at each supporter rank.
Each slot accepts one item by default. Items such as Elytra, blaze materials, Eyes of Ender, Ender Pearls, Wither Skeleton Skulls, Netherite Upgrade templates, Maces, Heavy Cores, shulker boxes, bundles, spawn eggs, and operator-only blocks are blocked. Filled containers and unsafe custom items should not be allowed to bypass the intended carryover limit.
Safe contents are stored separately in /plugins/LoopCore/safes/ and are protected from the standard reset. Configure the slot count, rank permissions, item rules, and messages under safe in /plugins/LoopCore/config.yml.
The supplied safe.slots value is 5. safe.gui-slots assigns their inventory positions, and safe.slot-rules defines the permission and text for each numbered slot. Slots 1 and 2 have an empty permission and are available to everyone; the remaining rules use loopcore.safe.slot.drifter, loopcore.safe.slot.reclaimer and loopcore.safe.slot.loopbreaker. Keep a rule and GUI position for each configured slot. safe.max-stack-size controls how many items fit in a slot.
Test /safe with the actual custom items sold or rewarded on your server. Add their names or persistent-data keys to the blacklist where necessary. Do not delete files from /plugins/LoopCore/safe-transactions/; they are recovery journals for interrupted item transfers.
Configure Purge tickets
Purge settings are under purge in /plugins/LoopCore/config.yml. The supplied defaults are:
| Setting | Default |
|---|---|
| Total tickets | 150 |
| Ticket price | $10,000,000 |
| Minimum playtime | 60 minutes |
| Minimum level | 0 |
| Tickets per player | 1 |
| Starting border | 10,000 blocks |
| Final border | 500 blocks |
| Border closing time | 3,600 seconds (one hour) |
| Elimination | Players are removed when they die |
Players can inspect and buy a virtual ticket with /purge. Tickets expire at the reset and do not occupy an inventory slot.
Administrators can grant and revoke tickets with:
/loopcore ticket give <player-or-UUID>
/loopcore ticket revoke <player-or-UUID>
The player must have joined before if you use their name. Use their UUID when they are not in the server's player cache. Administrator grants still consume one of the 150 available tickets.
Host the Purge
/startpurge is the complete event command. With the supplied configuration it:
- Whitelists all ticket holders and staff with the bypass permission.
- Enables the whitelist and ticket-only admission.
- Removes online players who do not have a ticket or bypass permission.
- Starts the survival world border at 10,000 blocks and shrinks it to 500 blocks over one hour.
- Randomly teleports eligible online players to safe locations within the final play area.
- Removes a participant from the event after their death.
Before running it:
- Make a complete off-server backup.
- Confirm the Purge world, border centre, sizes, duration, whitelist, random teleport, and death settings in
/plugins/LoopCore/config.yml. - Confirm staff who need to observe have
loopcore.purge.bypass. - Announce the final
/safedeadline and stop ticket sales at the time you have advertised. - Use
/purge infoand a non-staff test account to verify eligibility. - Run
/startpurgeonly when the event should begin.
/loopcore purge on only enables ticket admission. It does not run the whitelist, border, or random-teleport sequence. /loopcore purge off only disables ticket admission; it does not restore the whitelist or border changed by /startpurge. A normal season reset restores both when the supplied reset settings remain enabled.
Reset the season
The /reset command opens a preview instead of deleting data immediately. It lists the selected paths, file count, data size, and estimated downtime, then requires a second confirmation.
The final screen has two choices:
- Reset + advance season archives the seasonal data and advances
season_rotation.ymlto the next Battle Pass season. - Reset — season already set archives the seasonal data without changing the Battle Pass season. Use this only if you already changed it manually.
With the supplied configuration, the reset archives the survival terrain and player state, Essentials userdata and balances, Battle Pass database, leaderboards, bounties, RTP data, coinflips, CoreProtect history, market data, virtual crate data, survival-world edit history, spawners, ender chests, Purge tickets, and Purge state.
The following are retained:
- Spawn, arena, datapacks, world-generation settings, gamerules, and required Paper world metadata.
- LuckPerms ranks and permissions.
- PlayerPoints Gems.
- LoopCore safe contents, permanent statistics, and past achievement history.
- Plugin configuration files and crate definitions.
The reset reuses the existing world seed. It regenerates the seasonal terrain; it does not choose a new random seed.
Recommended reset runbook
- Create and verify a full off-server backup.
- Confirm every player has had the advertised opportunity to use
/safe. - Finish the Purge and wait for any important logs or recordings to save.
- Check the console for LoopCore warnings. Do not continue while an unresolved purchase receipt or safe transaction is reported.
- Run
/resetin game and carefully review every listed path. - Select the correct Battle Pass season option on the final confirmation screen.
- Let the countdown, shutdown, offline archive, and restart complete without manually starting a second server process.
- After restart, verify spawn, the fresh terrain, Gems, ranks, safe contents, Battle Pass season, shops, and player access before announcing the new season.
Reset archives are kept in /plugins/LoopCore/reset-backups/<reset-UUID>/; the selected data is moved there rather than permanently deleted.
If the reset fails, keep the server stopped and inspect:
/plugins/LoopCore/reset-runtime/supervisor.log/plugins/LoopCore/reset-runtime/restarted-server.log- The pending reset file and the matching archive manifest
Do not overwrite or selectively restore live data while the server is running. Restore a season only from a complete, consistent backup or contact support with the logs and manifest.
LoopCore administration commands
| Command | Purpose | Permission |
|---|---|---|
/loopcore reload | Reloads LoopCore configuration and regenerates pause-menu data | loopcore.admin.reload |
/loopcore ticket give <player-or-UUID> | Grants a virtual Purge ticket | loopcore.admin.tickets |
/loopcore ticket revoke <player-or-UUID> | Revokes a virtual Purge ticket | loopcore.admin.tickets |
/startpurge | Starts the complete configured Purge event | loopcore.admin.purge |
/loopcore purge on | Enables ticket-only admission | loopcore.admin.purge |
/loopcore purge off | Disables ticket-only admission | loopcore.admin.purge |
/reset | Previews and confirms a season reset | loopcore.admin.reset |
The parent permission loopcore.admin grants all LoopCore administration permissions. Operators receive it by default.
After changing the quick-menu buttons or dialog configuration, run /loopcore reload followed by /minecraft:reload, or restart the server.