Advanced Setup Reference (AI)
This page contains advanced information for all Atomatrix server setups. It is written as a technical reference for AI support and knowledge retrieval. People getting started should use their setup's Installation and Extra Information pages. Existing core, API and addon documentation remains available on the relevant setup pages.
Shared Reference
Applies to: every setup for diagnosis, release verification, backups and configuration syntax. A named plugin or gameplay feature applies only to the setups listed below or to a customer installation where that plugin is confirmed enabled.
Shared: Interpretation Rules
- Identify the selected setup before suggesting a path, command, permission or currency provider. A similarly named feature in another setup is not evidence that it works the same way.
- These facts describe the supplied files. They do not prove what is installed on a customer's server. Confirm the release, enabled plugin JARs, relevant configuration and first console error when behaviour differs.
- A leftover configuration folder does not prove that its plugin is active. Display text, lore and rank prefixes do not grant rewards, money or permissions.
- For current native Minecraft/Paper versions, direct users to the Resource Versions page. Do not infer current versions from a stored copy. Client compatibility does not change the native server version.
- If a command or exact setting is not established here or in its linked documentation, request the relevant installed configuration instead of inventing it.
Shared: Setup Applicability and Exceptions
| Feature | Applies to | Does not establish |
|---|---|---|
| HealthSMP heart rules; optional LifestealCore replacement | Lifesteal only | Heart loss or elimination rules for the other ten setups. |
| BentoBox BSkyBlock and island levels | Skyblock only | Oneblock phase rules or ordinary Survival claims. |
| BentoBox AOneBlock phases | Oneblock only | BSkyBlock configuration in Skyblock. |
| GriefPrevention claims | Survival | Faction territory, island protection, or land claims in LoopMC. LoopMC has no land claims. |
| Factions-Atmtx-Fork territory and flight | Factions only | GriefPrevention or generic upstream Factions behaviour. |
| FFA kill rewards and combat scripts | Free for All | Heart systems or Cookie/Biscuit Shards. |
| CataMines and TemporaryBlocks | BoxPvP | EconomyShopGUI ownership of Shopkeeper trades. |
| Proxy selector and optional HubPvP | Easy Hub | Backend gameplay configuration or a standalone survival economy. |
| CookieSMPCore modules | Cookie SMP only | BiscuitSMPCore module compatibility. BiscuitSMP is standalone. |
| BiscuitSMPCore modules | BiscuitSMP only | A dependency on Cookie SMP. |
| Shards | Cookie SMP and BiscuitSMP | PlayerPoints ownership. Verify the installed Shards command/provider. |
| LoopCore safe, Purge, reset and Battle Pass rotation | LoopMC only | Seasonal reset behaviour in any other setup. |
| PlayerPoints premium currency | Lifesteal, Skyblock, Survival, Oneblock, Factions, Free for All, BoxPvP; Gems in LoopMC | Cookie/Biscuit Shards or an Easy Hub currency. Normal money is separate. |
| AxAFKZone | Lifesteal, Skyblock, Survival, Oneblock, Factions, Free for All, BoxPvP and LoopMC supplied releases | Availability in Easy Hub, Cookie SMP or BiscuitSMP, or in older releases. |
| AxRewards | Lifesteal, Skyblock, Survival, Oneblock, BoxPvP and LoopMC supplied releases | The reward provider in Factions and Free for All; those use DailyRewards. |
| DailyRewards | Factions and Free for All supplied releases | AxRewards paths, claim-command fields or cooldown units. |
Shared: Before editing
Back up the file you will change. Before a plugin update, world change or season reset, make a complete backup that includes worlds and plugin data. Stop the server for a consistent file backup, or use a backup method supported by your host and database. Store a copy outside the server's own disk and check that it can be restored.
Check the Resource Versions page for the required native server version. Client compatibility plugins do not change the version that runs your server. If you are on an older setup release, establish which release your files came from before applying current instructions.
Shared: Keep configuration syntax intact
Use spaces for YAML indentation. Keep setting names, list markers and quotation marks in place. For example, this is an illustrative message setting, not a complete plugin configuration:
message: 'Welcome to my server!'
Text colours containing #, colons or special characters should retain the quoting style used by the original file. JSON files use different syntax: preserve commas, braces and double quotes. Do not paste a YAML example into JSON.
Shared: Follow the whole feature
A menu button can have a label, a requirement, a cost and several commands. If you change the amount charged, update the visible description and the command or requirement that actually deducts it. For a reward, check which plugin owns the currency, kit or item. A successful menu click does not prove every reward command succeeded.
Permissions and display text are separate too. Changing a rank name in TAB does not grant a LuckPerms group. Test permissions with a normal account; operator bypass can hide a missing permission.
Shared: Reload and test
Use a plugin-specific reload only when documented. Otherwise restart the server. Avoid the general /reload command. Read the first relevant error in the console, then test the exact action that you changed. For a paid action, compare the balance and received item before and after one test transaction.
If a change fails, restore the previous file and repeat the same test. Do not delete player data or regenerate a world as a first troubleshooting step.
Shared: Report a reproducible problem
Provide the setup name and release, actual server and plugin versions, the world, the command or action, and what you expected. Include the relevant config section and console error. Remove API tokens, passwords, database connection details and private player records before sharing. A screenshot of the symptom helps, but the first error and the exact file path are usually more useful than a full configuration dump.
Shared: AFK Zones and Claimable Rewards
Applies to: Lifesteal, Skyblock, Survival, Oneblock, Factions, Free for All, BoxPvP and LoopMC supplied releases. Does not apply by default to: Easy Hub, Cookie SMP or BiscuitSMP. Older releases may use a different implementation.
In plugins/AxAFKZone/zones/afk.yml, reward-time-seconds sets the wait, rewards contains the reward choices and commands, and zone.location1 / zone.location2 define the cuboid. Both corners must name the intended world. The message describing the reward is separate from the command that grants it.
Test the reward command with a test account, then wait through a complete interval inside the zone. Moving a WorldGuard region alone does not move this AxAFKZone cuboid. If a reward is currency or Battle Pass XP, its provider must be enabled as well.
AxRewards applies to Lifesteal, Skyblock, Survival, Oneblock, BoxPvP and LoopMC; it does not describe Factions or Free for All. AxRewards keeps claimable rewards in plugins/AxRewards/menus/default.yml. Each entry can define a cooldown, a permission and claim-commands. Update the claimable and unclaimable descriptions along with the commands; test both an eligible player and one without the rank.
DailyRewards applies to Factions and Free for All; it does not describe the six AxRewards setups above. Its file is plugins/DailyRewards/config.yml. The supplied cooldown is 86400000 milliseconds (24 hours), and named entries under rewards have permission, random, claim-message, broadcast and commands fields. Do not paste AxRewards claim-commands into this file. Preserve player claim state separately from configuration.
Lifesteal
Applies to: Lifesteal only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Lifesteal server folder.
Lifesteal Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Heart rules | plugins/HealthSMP/config.yml | Health gain/loss and elimination settings for the standard HealthSMP installation. |
| Optional heart plugin | plugins/LifestealCore/config.yml | Settings for the optional LifestealCore replacement. A folder alone does not mean that plugin is enabled. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Shop prices | plugins/EconomyShopGUI/shops | Per-category buy and sell entries. Keep item identifiers and values consistent when balancing prices. |
| Shop navigation | plugins/EconomyShopGUI/sections | Category names, icons and menu ordering. This is separate from the items sold inside each category. |
| Crate rewards | plugins/ExcellentCrates/crates | Crate definitions and their reward configuration. |
| Crate keys | plugins/ExcellentCrates/keys | Key definitions. A key and the crate accepting it need matching identifiers. |
| Claimable rewards | plugins/AxRewards/menus/default.yml | Daily and rank reward cooldowns, permission requirements, display text and claim commands. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
Lifesteal Operational Relationships
Lifesteal: Choose the active heart system
The standard setup uses HealthSMP. LifestealCore is an optional replacement described in the installation guide. Do not run both heart plugins together. Existing configuration folders may remain after switching, so confirm the enabled JAR in the startup log before editing either file.
For HealthSMP, plugins/HealthSMP/config.yml contains default-health, lose-amount, gain-amount, max-health, mobs-lose and death-command. The supplied values are 20 starting health, 2 lost or gained, and a maximum of 40. Minecraft has two health points per displayed heart; the administration command's <hearts> argument is a separate input and should be checked on a test player before bulk changes.
The configured command usage is /lifesteal <add/remove/set/setmax> <player> <hearts>, with the configured permission lifesteal.admin. The supplied elimination command is ban %playerName% 1d &cYou died. Review that command before changing your elimination policy; its final behaviour also depends on the command handler installed on your server.
Change one rule at a time, restart, then test PvP death, non-player death and the maximum-health limit with disposable test accounts. A health reward in a shop or crate must use the command for your active heart plugin.
Lifesteal Diagnostics
Lifesteal: Hearts do not change as expected
Check which heart JAR enabled at startup. Then inspect that plugin's gain/loss rules and the exact reward command. Test one PvP death and one environmental death before changing every reward.
Lifesteal: AFK text appears but no reward arrives
Check reward-time-seconds, the zone corners and the command under rewards in AxAFKZone. Test the reward command independently with a test player.
Lifesteal Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied Lifesteal release. Check the enabled plugin before applying this to older downloads.
Skyblock
Applies to: Skyblock only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Skyblock server folder.
Skyblock Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Island rules | plugins/BentoBox/addons/BSkyBlock/config.yml | Island world, spacing, protection and default island flags. |
| Island scoring | plugins/BentoBox/addons/Level/config.yml | Level calculation, scoring scope and recalculation timing. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Shop prices | plugins/EconomyShopGUI/shops | Per-category buy and sell entries. Keep item identifiers and values consistent when balancing prices. |
| Shop navigation | plugins/EconomyShopGUI/sections | Category names, icons and menu ordering. This is separate from the items sold inside each category. |
| Crate rewards | plugins/ExcellentCrates/crates | Crate definitions and their reward configuration. |
| Crate keys | plugins/ExcellentCrates/keys | Key definitions. A key and the crate accepting it need matching identifiers. |
| Claimable rewards | plugins/AxRewards/menus/default.yml | Daily and rank reward cooldowns, permission requirements, display text and claim commands. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
Skyblock Operational Relationships
Skyblock: Island worlds and protection
Skyblock uses BentoBox with the BSkyBlock addon. Start in plugins/BentoBox/addons/BSkyBlock/config.yml, rather than changing unrelated global server settings. The supplied command aliases include /island, /is, /skyblock and /sb.
The world section names bskyblock_world, with distance-between-islands: 400 and protection-range: 50 in the supplied configuration. World names and island spacing should be decided before players create islands. Changing them on an established server is a migration, not a cosmetic edit; test on a restored copy first.
default-island-flags and default-island-settings control separate parts of island protection and behaviour. Test as an island owner, a team member and a visitor. An operator account can bypass restrictions and give a misleading result.
Skyblock: Island levels
The Level addon has its own plugins/BentoBox/addons/Level/config.yml. In the supplied configuration, levelcost is 100, level-calc is blocks / level_cost, levelwait is 60, and chest contents are excluded with include-chests: false. The Nether and End are excluded from that calculation by their respective settings.
If levels appear wrong, check the scoring settings and recalculate using the installed addon's supported command before changing the scoreboard. The scoreboard displays a result; it does not calculate island value. Keep BentoBox's island database and the island worlds together in backups.
Skyblock Diagnostics
Skyblock: Players cannot build on their island
Check the island owner/team and the relevant BSkyBlock flag. Compare owner and visitor behaviour with non-operator accounts, and check overlapping WorldGuard protection.
Skyblock: The displayed island level seems wrong
Check the Level addon scoring scope and its recalculation timing. Confirm the underlying level before changing TAB or a leaderboard placeholder.
Skyblock Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied Skyblock release. Check the enabled plugin before applying this to older downloads.
Survival
Applies to: Survival only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Survival server folder.
Survival Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Land claims | plugins/GriefPreventionData/config.yml | World claim modes, claim-block accrual, claim tools and protection rules. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Shop prices | plugins/EconomyShopGUI/shops | Per-category buy and sell entries. Keep item identifiers and values consistent when balancing prices. |
| Shop navigation | plugins/EconomyShopGUI/sections | Category names, icons and menu ordering. This is separate from the items sold inside each category. |
| Crate rewards | plugins/ExcellentCrates/crates | Crate definitions and their reward configuration. |
| Crate keys | plugins/ExcellentCrates/keys | Key definitions. A key and the crate accepting it need matching identifiers. |
| Claimable rewards | plugins/AxRewards/menus/default.yml | Daily and rank reward cooldowns, permission requirements, display text and claim commands. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
Survival Operational Relationships
Survival: Configure land claims
Survival uses plugins/GriefPreventionData/config.yml for claim rules. Under GriefPrevention.Claims.Mode, the supplied configuration enables Survival claims in world, world_nether and world_the_end, while claims are disabled in spawn and arena. Check the exact world name when claims work in one world but not another.
The supplied claim defaults include 100 initial blocks, 100 accrued blocks per hour for the default allowance and an 80,000 accrued-block cap. These are configured values, not a promise that every player receives the same allowance after rank permissions or other changes.
The claim inspection tool is STICK and the modification tool is GOLDEN_SHOVEL. Protection options include container access, creatures, doors, pearls and explosions. Edit the relevant protection setting instead of disabling claim protection globally to solve one interaction problem.
Survival: Test protection and purchases together
Use two non-operator accounts: one owns the claim and the other is a visitor. Test the interaction that matters, such as opening a chest, trading or placing a block, both inside and outside the claim. Also check WorldGuard regions at spawn; the claim configuration requires WorldGuard build permission for claim creation.
The claim-block shop menu is plugins/DeluxeMenus/gui_menus/coinshop-claimblocks.yml. If changing a package, check the displayed quantity, the price requirement and the reward command together. Back up GriefPrevention data before changing plugins or migrating worlds; copying only config.yml does not preserve player claims.
Survival Diagnostics
Survival: Claims work in one world but not another
Check GriefPrevention.Claims.Mode for the exact world name. Claims are deliberately disabled in spawn and arena in the supplied configuration.
Survival: A player bought claim blocks but sees no change
Check the purchase menu's price requirement, deduction and reward command. Compare the balance and block allowance before/after one controlled purchase, and inspect the console.
Survival Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied Survival release. Check the enabled plugin before applying this to older downloads.
Oneblock
Applies to: Oneblock only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Oneblock server folder.
Oneblock Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Oneblock rules | plugins/BentoBox/addons/AOneBlock/config.yml | Island commands, world settings and phase-related options. |
| Phase progression | plugins/BentoBox/addons/AOneBlock/phases | Block phases and companion chest reward files. Keep the phase sequence coherent. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Shop prices | plugins/EconomyShopGUI/shops | Per-category buy and sell entries. Keep item identifiers and values consistent when balancing prices. |
| Shop navigation | plugins/EconomyShopGUI/sections | Category names, icons and menu ordering. This is separate from the items sold inside each category. |
| Crate rewards | plugins/ExcellentCrates/crates | Crate definitions and their reward configuration. |
| Crate keys | plugins/ExcellentCrates/keys | Key definitions. A key and the crate accepting it need matching identifiers. |
| Claimable rewards | plugins/AxRewards/menus/default.yml | Daily and rank reward cooldowns, permission requirements, display text and claim commands. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
Oneblock Operational Relationships
Oneblock: Island creation and commands
Oneblock uses BentoBox with the AOneBlock addon. Its settings live in plugins/BentoBox/addons/AOneBlock/config.yml. The configured player aliases are /ob and /oneblock; new players default to island creation, while returning players default to going to their island.
The config defines count-command: count and phases-command: phases, so /ob count and /ob phases are the configured progress and phase entry points. If a command differs on your server, check the aoneblock.command section and the installed addon version before changing menus.
Oneblock: Edit phase progression
The phase files are in plugins/BentoBox/addons/AOneBlock/phases/. Examples include 0_plains.yml, 700_underground.yml and 2000_winter.yml, with companion files such as 0_plains_chests.yml for chest rewards. The supplied sequence includes later Nether, Deep Dark and End phases, plus 12000_goto_0.yml.
Back up the entire phases folder before changing progression. Keep the block-phase settings and associated chest rewards together, and test progression from a fresh island and an existing island near a phase boundary. Changing a displayed phase name in a menu alone does not change the block progression.
The configured world is oneblock_world. Avoid renaming that world or moving islands by hand; world data and BentoBox's stored island records must remain consistent. If the regenerating block disappears, inspect the startup log and the configured respawn-block-command before recreating or deleting the island.
Oneblock Diagnostics
Oneblock: The regenerating block or a phase is wrong
Check AOneBlock startup errors, the current phase and the matching phase/chest files. Compare a fresh island with the affected island. Preserve the island database before attempting recovery.
Oneblock: A menu runs an unknown island command
Compare its click action with aliases under aoneblock.command in the addon config. The supplied player command is /ob, not the Skyblock setup's /is.
Oneblock Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied Oneblock release. Check the enabled plugin before applying this to older downloads.
Factions
Applies to: Factions only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Factions server folder.
Factions Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Faction rules | plugins/Factions-Atmtx-Fork/config.yml | Faction flight, warps, relation checks and interface settings. Use the supplied fork's actual folder. |
| Faction core settings | plugins/Factions-Atmtx-Fork/conf.json | Additional faction configuration. Edit as JSON; do not confuse it with player, faction or board data files. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Shop prices | plugins/EconomyShopGUI/shops | Per-category buy and sell entries. Keep item identifiers and values consistent when balancing prices. |
| Shop navigation | plugins/EconomyShopGUI/sections | Category names, icons and menu ordering. This is separate from the items sold inside each category. |
| Crate rewards | plugins/ExcellentCrates/crates | Crate definitions and their reward configuration. |
| Crate keys | plugins/ExcellentCrates/keys | Key definitions. A key and the crate accepting it need matching identifiers. |
| Claimable rewards | plugins/DailyRewards/config.yml | Reward behaviour for releases using DailyRewards. Do not replace its player data with a template. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
Factions Operational Relationships
Factions: Use the supplied faction fork
This setup stores its faction settings in plugins/Factions-Atmtx-Fork/. Begin with config.yml and conf.json. The neighbouring players.json, factions.json and board.json are live state, not example configuration to overwrite during an update.
The supplied YAML includes max-warps: 5, optional warp costs under warp-cost, and faction flight under enable-faction-flight and ffly. The ffly section includes an enemy-radius check, a combat cooldown and separate switches for disabling flight after damage. Change the relevant rule before changing a menu that only displays flight availability.
Factions: Diagnose territory and flight behaviour
Reproduce the problem in wilderness, friendly territory and enemy territory using a normal player. Check the player's faction relation, combat state and permissions. If faction flight stops near an enemy, compare that with enemies-near-disable-flight before treating it as a fault.
For a warp problem, check whether the configured maximum was reached and whether warp-cost.enabled is set. Do not copy settings from another faction plugin or replace this fork's data with a fresh template. A complete backup should include faction records, claim-board data, player records and the matching worlds.
Factions Diagnostics
Factions: Faction flight switches off unexpectedly
Check combat state, nearby enemies and ffly settings in the supplied faction fork. Test away from enemies before changing flight permissions.
Factions: A config change seems ignored
Confirm you edited Factions-Atmtx-Fork, not a folder left by another plugin. Check both YAML syntax and JSON syntax, then read the startup log after a controlled restart.
Factions Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied Factions release. Check the enabled plugin before applying this to older downloads.
Free for All
Applies to: Free for All only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Free for All server folder.
Free for All Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Arena kit entry | plugins/Skript/scripts/giveKit.sk | Sends a player into the arena, clears their inventory and gives the chosen Essentials kit. |
| Kill income | plugins/Skript/scripts/moneyOnKill.sk | The economy command run on a player death. |
| Death drops | plugins/Skript/scripts/noDeathDrops.sk | Clears death drops. Check this before assuming lost items are an Essentials setting. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Shop prices | plugins/EconomyShopGUI/shops | Per-category buy and sell entries. Keep item identifiers and values consistent when balancing prices. |
| Shop navigation | plugins/EconomyShopGUI/sections | Category names, icons and menu ordering. This is separate from the items sold inside each category. |
| Claimable rewards | plugins/DailyRewards/config.yml | Reward behaviour for releases using DailyRewards. Do not replace its player data with a template. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
Free for All Operational Relationships
Free for All: Follow the arena entry chain
Arena entry is coordinated by plugins/Skript/scripts/giveKit.sk. Its /sendplayer <player> <kit> command requires ffa.sendplayer. The script asks BetterRTP to send the named player into arena, waits briefly, clears that player's inventory and gives an Essentials kit.
This inventory clear is intentional. Test changes with an empty test account rather than a player carrying valuable items. A menu or NPC that calls this command must use the exact kit name from plugins/Essentials/kits.yml.
If the player teleports but receives no kit, check the kit name and the console error after the teleport. If they never teleport, check the arena world and BetterRTP first. Check Skript's startup or reload errors before editing more files.
Free for All: Kill money and death drops
plugins/Skript/scripts/moneyOnKill.sk runs essentials:eco give %attacker% 5 on a player death in the supplied script. It does not explicitly guard against a non-player attacker. Test fall, fire and other environmental deaths as well as PvP if you change this script; a reward command that receives an invalid attacker should not be mistaken for a broken economy.
plugins/Skript/scripts/noDeathDrops.sk clears drops on death. Changing an Essentials keep-inventory setting alone will not remove that script's effect. Keep the kit, inventory-clear and death-drop rules consistent so a player cannot duplicate kit equipment or unexpectedly keep it between rounds.
Free for All Diagnostics
Free for All: Arena teleport works but the kit is missing
Follow giveKit.sk: BetterRTP teleport, inventory clear, then Essentials kit. Verify the requested kit exists and read errors from that command sequence.
Free for All: A death gives no money or an invalid-player error
The supplied money script inserts the attacker into an economy command. Reproduce with PvP and environmental damage separately; not every player death has a player attacker.
Free for All Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied Free for All release. Check the enabled plugin before applying this to older downloads.
BoxPvP
Applies to: BoxPvP only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the BoxPvP server folder.
BoxPvP Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Mine definitions | plugins/CataMines/mines | Mine cuboids, block composition and reset settings. |
| Block expiry | plugins/TemporaryBlocks/config.yml | Default expiry time and material-specific overrides for placed blocks. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Crate rewards | plugins/ExcellentCrates/crates | Crate definitions and their reward configuration. |
| Crate keys | plugins/ExcellentCrates/keys | Key definitions. A key and the crate accepting it need matching identifiers. |
| Claimable rewards | plugins/AxRewards/menus/default.yml | Daily and rank reward cooldowns, permission requirements, display text and claim commands. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
BoxPvP Operational Relationships
BoxPvP: Balance and relocate mines
CataMines stores each mine under plugins/CataMines/mines/. For example, donator-vip.yml contains Mine.region, Mine.composition, resetMode, resetDelay and player-teleport options. The supplied VIP mine uses a timed reset with resetDelay: 300 and a composition of 50% iron blocks, 20% gold blocks, 20% diamond blocks and 10% emerald blocks.
When balancing a mine, keep composition chances coherent and test several resets. When relocating it, check both cuboid corners, their world names and the teleport settings. A mine reset replaces blocks in its configured region, so use a test copy before changing boundaries near builds.
BoxPvP: Temporary arena blocks
plugins/TemporaryBlocks/config.yml sets default-expire-time: 120. Material-specific values under expire-time-overrides take precedence; the supplied cobblestone override is 45 seconds and obsidian is 600 seconds.
Use a normal account when testing expiry. An administrator with the temporary-block bypass can place blocks that do not expire, which can look like a configuration failure. Changing the mine reset delay does not change the lifetime of player-placed arena blocks.
BoxPvP: Trades and progression
Mine rewards, Shopkeeper trades, kits and crate rewards form one progression system. After changing a high-value material, check whether it can be traded back into something more valuable without a cost. Test the actual trade with the intended rank rather than relying on the menu's description alone.
BoxPvP Diagnostics
BoxPvP: A mine resets to unexpected blocks
Check the selected mine file, world, cuboid and composition. Do not fix the wrong mine by changing global defaults; test a reset on a backup first.
BoxPvP: Some placed blocks never disappear
Check material overrides and whether the test account has temporary-block bypass enabled. Mine reset timing and temporary-block expiry are separate systems.
BoxPvP Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied BoxPvP release. Check the enabled plugin before applying this to older downloads.
Easy Hub
Applies to: Easy Hub only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Easy Hub server folder.
Easy Hub Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Server selector | plugins/DeluxeMenus/gui_menus/servers.yml | Visible server names, player counts and proxy connection targets. |
| Hub PvP | plugins/HubPvP/config.yml | PvP activation delays, allowed worlds, messages and the PvP item. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
Easy Hub Operational Relationships
Easy Hub: Connect the selector to your proxy
The selector file is plugins/DeluxeMenus/gui_menus/servers.yml (plural). Each item has visible text and a connection action. The supplied actions include [connect] survival, [connect] lifesteal and [connect] skyblock; those targets must match the server names configured on your proxy.
For each destination, update the display name, the %bungee_<server>% player-count placeholder and the [connect] <server> action together. A pretty label does not create a backend server or change its proxy name.
NPC actions are separate, in plugins/FancyNpcs/npcs.yml; floating labels are in plugins/FancyHolograms/holograms.yml. Check all three when removing or renaming a backend. Test by joining through the proxy, opening the selector and using each NPC. A direct connection to the hub does not reproduce the same network path.
Easy Hub: Configure optional hub combat
plugins/HubPvP/config.yml controls the PvP item, enable/disable delays and allowed worlds. The supplied enable and disable cooldowns are five seconds. With whitelist: true, the configured worlds list contains world.
If you rename the lobby world, review this list and any NPC/hologram locations. Edit message text and numeric reward settings separately: a message saying a player gained health does not itself determine health-on-kill.
Easy Hub Diagnostics
Easy Hub: The selector opens but cannot connect
Check [connect] targets against proxy server names, then confirm the target backend is running and reachable from the proxy. Test through the public proxy address.
Easy Hub: An NPC goes to the old server
Update the NPC action in FancyNpcs as well as the selector. FancyHolograms changes only the display text and position.
Cookie SMP
Applies to: Cookie SMP only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the Cookie SMP server folder.
Cookie SMP Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Core modules | plugins/CookieSMPCore/configs | Separate module files for auctions, homes, combat, payments and other core features. |
| Item worth | plugins/CookieSMPCore/itemworths.yml | Values used by the core worth feature; check the active economy path when changing sale behaviour. |
| Kill Shards | plugins/Skript/scripts/give_shards_on_kill.sk | The configured Shards command and kill message. Verify its currency provider is installed. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
Cookie SMP Operational Relationships
Cookie SMP: Find the module that owns a feature
CookieSMPCore separates features into files under plugins/CookieSMPCore/configs/, including auctionhouse.yml, homes.yml, combat.yml and pay.yml. Check the core reference for module commands and permissions, and the API reference if you are writing an integration.
For an auction issue, inspect the auction module before changing generic economy settings. For a home or teleport issue, check the relevant module and combat restrictions. Update one module at a time and test with a normal player; operator permissions can bypass limits.
Cookie SMP: Verify Shards before changing rewards
The documented Shards command is /coinsengine:shards give <name> <amount> -s. The kill-reward script, plugins/Skript/scripts/give_shards_on_kill.sk, also calls that command through its shard_command option. Its message is a separate kill_message value; keep the displayed reward and the command amount consistent.
If that command is unknown, check that the currency provider required by your release is installed and enabled. The presence of a PlayerPoints folder does not make /points an interchangeable Shards command. Identify the active provider before issuing refunds or changing a store package.
plugins/CookieSMPCore/itemworths.yml supplies core item values. After changing value-related features, test the worth display and actual sale result, rather than assuming a changed label alters every selling system.
Cookie SMP Diagnostics
Cookie SMP: A Shards grant is an unknown command
Check the currency provider for your release. The supplied script calls coinsengine:shards; do not substitute /points just because PlayerPoints is present.
Cookie SMP: One core feature fails while others work
Read the core status and the affected module's configuration using the core reference. Check command permissions and console errors for that module before replacing the full plugin.
BiscuitSMP
Applies to: BiscuitSMP only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the BiscuitSMP server folder.
BiscuitSMP Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Core modules | plugins/BiscuitSMPCore/configs | Separate files for each core feature; use the BiscuitSMP files rather than CookieSMP examples. |
| Item worth | plugins/BiscuitSMPCore/itemworths.yml | Core item values. |
| Shards | plugins/CoinsEngine/currencies/shards.yml | The Shards currency definition; separate from any PlayerPoints installation. |
| Kill Shards | plugins/Skript/scripts/give_shards_on_kill.sk | Kill reward command and message. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
BiscuitSMP Operational Relationships
BiscuitSMP: Keep BiscuitSMP modules together
BiscuitSMPCore's module files are in plugins/BiscuitSMPCore/configs/. The core reference describes the available commands and permissions; the API reference is intended for developers.
Use the module matching the feature you are changing, such as auctionhouse.yml, homes.yml, combat.yml or crate.yml. CookieSMP and BiscuitSMP share some concepts, but their files and enabled features are not interchangeable.
BiscuitSMP: Shards and kill rewards
Shards are configured in plugins/CoinsEngine/currencies/shards.yml. The documented grant command is /coinsengine:shards give <name> <amount> -s. PlayerPoints may also be present; it is not the Shards balance managed by this command.
Kill rewards come from plugins/Skript/scripts/give_shards_on_kill.sk. Adjust shard_command and kill_message together so the message matches the currency actually granted. Test with two ordinary accounts and verify the balance before and after the kill.
For a menu purchase, follow the balance requirement, deduction command and reward command. They must refer to the same currency and amount. Check the console if the menu closes without granting the item; the visible click response does not prove every command succeeded.
For a public statistics page, follow the separate Stats Website Addon guide. Treat its public read-only data separately from any administration API credentials.
BiscuitSMP Diagnostics
BiscuitSMP: A purchase charges the wrong balance
Check whether each menu action uses CoinsEngine Shards or PlayerPoints. Review the requirement, deduction and reward as one transaction.
BiscuitSMP: Core config changes affect the wrong feature
Match the problem to its module in BiscuitSMPCore/configs. Use BiscuitSMP's core reference rather than copying CookieSMP module settings.
LoopMC
Applies to: LoopMC only. Does not apply to: the other ten setups unless explicitly covered by Shared Reference. Paths below are relative to the LoopMC server folder.
LoopMC Configuration Reference
| What you want to change | File or folder | What to check |
|---|---|---|
| Season systems | plugins/LoopCore/config.yml | Safe slots, Purge tickets, event controls and reset settings. |
| Battle Pass seasons | plugins/BattlePass/season_rotation.yml | Season progression used by the reset flow. |
| Free rewards | plugins/BattlePass/BattlePassFREE.yml | Rewards on the free Battle Pass track. |
| Premium rewards | plugins/BattlePass/BattlePassPREMIUM.yml | Rewards on the premium Battle Pass track. |
| Branding | plugins/AtomatrixCore/placeholders.yml | Server name, public links and shared branding text. Apply with /atomatrixcore reload. |
| Server list | plugins/MiniMOTD/main.conf | The two lines shown before a player joins. This is separate from the in-game scoreboard. |
| Scoreboard and tab list | plugins/TAB/config.yml | Scoreboard layout, header/footer and display features. Check referenced placeholders before replacing them. |
| Rank display | plugins/TAB/groups.yml | Group-specific prefixes and display formatting. This does not grant LuckPerms permissions. |
| Player menus | plugins/DeluxeMenus/gui_menus | Menu text, icons, requirements and click commands. A displayed price and the command that charges it must agree. |
| Starting and rank kits | plugins/Essentials/kits.yml | Kit contents and cooldowns. Menu buttons may refer to these kit names. |
| General player settings | plugins/Essentials/config.yml | Essentials settings such as home limits and command behaviour. Back up userdata separately before plugin updates. |
| Shop prices | plugins/EconomyShopGUI/shops | Per-category buy and sell entries. Keep item identifiers and values consistent when balancing prices. |
| Shop navigation | plugins/EconomyShopGUI/sections | Category names, icons and menu ordering. This is separate from the items sold inside each category. |
| Crate rewards | plugins/ExcellentCrates/crates | Crate definitions and their reward configuration. |
| Crate keys | plugins/ExcellentCrates/keys | Key definitions. A key and the crate accepting it need matching identifiers. |
| Claimable rewards | plugins/AxRewards/menus/default.yml | Daily and rank reward cooldowns, permission requirements, display text and claim commands. |
| AFK rewards | plugins/AxAFKZone/zones/afk.yml | AFK cuboid, waiting time and reward commands. The zone uses its own configured locations. |
| Announcements | plugins/Infiniteannouncements/announcements.yml | Automatic chat announcements. Match the exact folder spelling on Linux hosts. |
| NPC actions | plugins/FancyNpcs/npcs.yml | NPC definitions and actions. Check the destination or command as well as the visible name. |
| Hologram text | plugins/FancyHolograms/holograms.yml | Floating text and display locations. Changing text alone does not change an NPC action. |
LoopMC Operational Relationships
LoopMC: Plan a season change before editing it
LoopMC combines plugins/LoopCore/config.yml with Battle Pass configuration and several economy and reward plugins. Use the safe, Purge and reset runbook before editing the underlying paths. The reset configuration is operational: it decides which live data is archived.
Battle Pass track rewards are in plugins/BattlePass/BattlePassFREE.yml and plugins/BattlePass/BattlePassPREMIUM.yml; season_rotation.yml controls the configured rotation. Changing a reward is different from advancing a season. Choose the reset option that matches whether you have already advanced the season manually.
Safe slots, rank access and item rules belong to LoopCore's safe section. Test ordinary items, custom rewards and filled containers before advertising what players can carry over. Keep safe-transactions recovery files with the safe data; do not clear them as if they were cache files.
The Stats Website Addon is optional and has its own configuration. It does not replace the reset archive or provide a backup of players' safe contents.
LoopMC Diagnostics
LoopMC: A safe transaction is pending
Preserve the safe data and recovery journals, stop further reset attempts and inspect the console. Do not delete safe-transactions files to clear the warning.
LoopMC: A season reset did not complete
Keep the server stopped and preserve the matching archive and manifest. Inspect plugins/LoopCore/reset-runtime/supervisor.log and restarted-server.log; follow the reset runbook before attempting recovery.
LoopMC: Purge admission changed but the event did not start
/loopcore purge on only enables admission checks. Read the full Purge procedure before triggering the border, whitelist and teleport sequence.
LoopMC Rewards and AFK Zones
The shared AFK and reward-provider details apply to the supplied LoopMC release. Check the enabled plugin before applying this to older downloads.