Gameplay

Game modes, skills, classes, mobs, mechanics, pets, jobs, homes and world rules.

Tag #

Tag (Tag → Tag, permission tag.manage): everything for Tag servers (skript/tag/).

  • Settings: which modes players can vote for (Last One Standing, Freeze Tag, Infection, Classic Tag), players needed and the most per round, voting time, the tag timer (Last One Standing, default 30s), round length (the other modes), the taggers' head start, the runners' speed bonus (default +10%) and the taggers' (default +25%), how far ahead taggers are always kept (default 5% faster than the fastest runner, counting speed skills, speed boosters and panic mode, so they can always catch up; a slowness booster on a tagger still slows them; 0 turns it off), panic mode (when 3 or fewer are left, everyone +100%), taggers per player count, coin rewards (200 / 100 / 50 for the top 3 in Last One Standing, per winner in the other modes, and for everyone who played), how many active and passive skills a player can equip, and the particle effect around the tagger (from Cosmetics and text → Particle effects; none by default) for maps that don't choose their own.

  • Skills: create, edit and delete skills without restarting anything. Each has a name, description, type (active: a hotbar item used with right-click; passive: works on its own), rarity, menu item, effect (speed boost, invisible with a decoy, nausea on whoever you tag, speed after being hit, taggers miss you), the effect's numbers (speed %, seconds, nausea, invisibility, miss chance), cooldown, price, level needed, and upgrades (highest level, price × current level, % stronger per level). Five come ready: Blinder, Adrenaline, Shadow Clone, Perilous and Luck Roulette (level 50, 10,000 coins). Pick Custom (your own code) as the effect to write the skill yourself in Skript: choose when it runs (right-click, when you tag someone, when you get tagged, or at round start) and write the code, which gets {_p}, {_target}, {_level} and {_skill} plus helpers such as TagSkill_Mod, TagSkill_Boost and Tag_Potion (listed on the form). Saving checks the code for mistakes. Custom skills are published with the Tag category's Projects (choose the category under Settings), as addons/tag-custom-skills/TagCustomSkills.sk, so they reach servers within a minute without a restart.

  • Boosters (on the Tag page under Boosters, /manage/tag/boosters/create): buffs and nerfs placed on maps with signs. Each has a unique name (not only a number), buff or nerf (green or red in-game), up to 4 effects (speed, slowness, jump boost, blindness, glowing, invisibility, nausea, levitation, slow falling, darkness or weakness, each with a level 1 to 5 and seconds), who it affects (runners, taggers or both; a sign can say otherwise), a cooldown (seconds it's gone after a pickup, 0 to 600) and a pickup radius (0.5 to 8 blocks; 1.5 is touching it), and can be turned off (its signs then show nothing). Four come ready: Speed (runners, Speed II 5s), Jump (both, Jump boost II 6s), Slowness (taggers, Slowness II 4s) and Blindness (taggers, Blindness I 3s). Changes are in the audit log (tag.booster_*).

  • Maps: built from a schematic, like dungeons. Each map has a WorldEdit 7 .schem (//schem save), a fall-out height, an optional jump pad block and power, and the particle effect around the tagger (the settings' default, none, or a chosen effect). Signs in the schematic mark spawn points and are taken out of the build (App\Support\TagMapBlocks, which reads sign text in every shape, old JSON lines and Minecraft 1.21.5+ text components alike):

    • [runner] or [spawn]: a runner spawn point. A map needs at least one.
    • [tagger]: a tagger spawn point. With none, a tagger starts on a random runner spawn point; with fewer than there are taggers, the ones left over do; with more, each tagger gets one at random.
    • [center]: the block that goes on the server's map spawn point (at most one). Without one, the middle of the schematic's bottom layer does. Signs are found on their own blocks whether the schematic saved their positions from its corner (WorldEdit) or from where it was copied (some FastAsyncWorldEdit versions). A schematic whose marker sign isn't on a sign block either way is refused, so a map can't be built in the wrong place. Maps uploaded before November 2026 with FastAsyncWorldEdit may have their [center] and spawn points shifted (the map's corner lands on the map spawn point): upload the schematic again.
    • [booster]: a booster. The next line is the booster's name (any case) or ID. The other lines can say who it affects (tagger, runner or both; otherwise the booster's own choice) and how it looks: player (an armour stand wearing a random online player's head), mob ZOMBIE (a still mob of that type) or block GOLD_BLOCK (a floating block; the default, an emerald block for a buff and a redstone block for a nerf). A sign naming no booster refuses the schematic (the old one is kept); the upload message and the map's page list the boosters it has.

    Players start in the middle of the sign's block, facing the way the sign faced. Other signs are built with their words. After an upload the message says how many runner and tagger spawn points it found, whether it has a [center] sign, and the words on the ordinary signs it kept (so a mistyped marker shows up); the map's page shows the same as a summary. A schematic with no runner sign, or more than one [center] sign, is refused (the old one is kept). For a schematic map the fall-out height counts from the map's bottom layer (-5: five blocks under it). Maps without a schematic still work the old way: spawn points saved in-game with /tag setspawnpoint <map ID> (/tag clearspawns <map ID> removes them, single ones on the map's page). Only maps with a schematic with runner spawn points, or with in-game spawn points, are played.

  • Leaderboard: the last 7 days' most wins. It's posted to Discord every Monday at 00:00 (the "tag-leaderboard" scheduled task) to webhooks with Tag: weekly top players ticked, or straight away with the button.

Pets #

Pets (/manage/pets, permission pets.manage). Staff add pets (mob, baby, price in global coins, on or off sale), give and take them away. Players buy and choose one with /pet, the lobby or the portal, and can rename it. The pet follows them on every server where pets are on. Pets can't be hurt, be ridden or drop anything.

Two rules control where pets work, set per category and overridable per server (Servers → Groups, or edit a server): Pets follow players (off: pets are put away there, players keep them) and Pet abilities work (off: pets still follow but don't fight, blast, heal, block or give potion effects). Both are on by default, and changes apply within about 15 seconds. The portal's Pets page lists each pet's abilities in words (at the player's level for pets they own, plus what they reach at the top level) and where they work: "All servers", or the categories and servers (switched on) that have both rules on. The /pet menu says when either is off.

Pet settings (Pets → Settings, /manage/pets/settings, permission pets.manage; App\Support\PetSettings, used by network/Cosmetics/Pets.sk). How pets behave on every server, sent with the group settings (pet_settings), so changes apply within 15 seconds:

  • Following: how close pets follow (2.5 blocks), how far behind before they catch up by appearing behind their owner (14 blocks), their walking speed (1.1) and their speed when more than 7 blocks behind (1.6).
  • Name tag: on or off, and its text (&e{lv} {level} &b{name} &7({owner}): {lv} is "Lv" in the owner's language, {level} the pet's level, {name} its name or the owner's nickname for it, {owner} the owner).
  • Put pets away in combat (off): while the owner is combat tagged their pet is put away, fight abilities included, and it comes back when the tag ends.
  • Renaming (on): whether players can rename pets on the portal, and the longest name (24 characters).
  • Following through teleports (on): when the owner teleports (/spawn, /home, portals, another world) the pet appears behind them straight away.
  • Put pets away while flying (on): flying (creative or /fly) or gliding with an elytra; it comes back when they land.
  • When the owner stands still or is AFK (Sit, after 5 seconds): pets that can sit do (wolves and cats; parrots and foxes on modern servers) and the rest stay put; or Wander nearby (short walks around the owner every few seconds); or nothing. AFK is the Anti-AFK rule's, where it's on. They stand up and follow again as soon as the owner moves.
  • Gifting (on): on the portal's Pets page (Gift or sell back under a pet), to a player who doesn't have that pet. It keeps its level and XP; its nickname goes. The new owner is told, and it's in the audit log (pet.gift).
  • Selling back (50% of the price; 0 turns it off): on the same page, after a warning that the pet's level, XP and name are gone for good (even if they get it again) and a ticked I understand, then a confirm. The price shown is the price paid: one changed since is refused. Pets staff gave sell for nothing. In the audit log (pet.sell).
  • Refund when staff take a pet away (0%): a share of the price for a pet the player bought (or was gifted, if it was bought). Shown in the staff message and the audit log.
  • Premium pet looks (on), on the portal's Pets page under Pet looks for players with Premium or Pets Premium (bought in /store or the website store; see Items and economy → Island subscription and Pets Premium in the store): size (small, normal or large: babies and slimes on every server, and any mob on servers with the scale attribute, 1.20.5 and up), a particle trail (a particle effect from Cosmetics and text → Particle effects, puffed behind the pet every second; staff can limit which ones under Particle trails Premium players can pick, empty for every effect that's on), glow (modern servers) and gold level stars over its name (more stars as it levels, up to Most level stars, 5). Saved per player (players.pet_looks) and sent with their pet only while they have Premium or Pets Premium, so they stop when it ends.

Until a server has them it uses the same values, so nothing changes until staff do. Saving is in the audit log (pet.settings). Whether pets and their abilities work at all stays a game rule per category (Pets follow players, Pet abilities work).

Pet abilities #

Unlock levels and what levels change (on each ability of a pet's page). Unlocks at pet level (1): the ability only works from that pet level; until then servers don't get it, and /pet and the portal show it as locked ("Unlocks at pet level 5: ..."). Levels change picks which of the ability's numbers each level above 1 changes (damage for fights and blasts, healing, block chance and potion level unless you pick another, like the cooldown or the radius), By picks a % of it or a fixed amount, and Change per pet level how much: negative lowers it (a cooldown 0.5 seconds shorter each level). Numbers stay within the field's limits. Abilities saved before keep working as they did (2% stronger a level; potions don't change).

Pet abilities (a pet's page → Abilities; network/Cosmetics/Pets.sk). Without any, a pet only follows. Each pet can have: fights for its owner (for a set damage in hearts give or take a %, every few seconds, up to a distance from the owner; players only where PvP is on; owners turn it off and on with /pet attack), blast (an active ability, /pet use: damages everything within a radius, with a cooldown), potion effect on the owner while it's out (speed, jump boost, night vision, strength...), heals the owner every so often, and blocks hits (a % chance). Hits count as the owner's, so kills, combat tags and PvP protection work as normal. The /pet menu lists each pet's abilities, one line per option.

Combat options on fights for its owner: when it joins in (assists and fights back, only fights back, only assists, or also attacks monsters near the owner), how far away it hits from, chase speed, and how many seconds it keeps going after the last hit. Fights and blasts can both choose what they attack (mobs, monsters, peaceful mobs, players, or mobs and players), scale damage to players, have critical hits, set targets on fire, knock them back and leave crew mates alone. Fights can also heal the owner for a % of the damage. Pets saved before these options existed behave as they did. Friends can't be spared, only crew mates: servers don't keep a player's friend list.

Downsides #

Downsides (any ability, up to 4, all off until staff add them). What the owner pays when an ability activates: hunger, health (stops at half a heart, never kills), XP levels, money, items from their inventory, a bad potion effect (slowness, weakness, mining fatigue, nausea, blindness, hunger, poison or wither, with a level and seconds), being set on fire, or the pet resting (no abilities at all for some seconds). Fights can pay each hit or each second of fighting, potion effects pay each second they're on, and blasts, heals and blocks pay each use. A pet can't rest after a potion effect. "Only works while the owner can pay" stops the ability when they don't have enough hunger, health, XP levels, money or items; without it, whatever can be taken is taken and the ability carries on. The /pet menu lists each downside.

Conditions #

Conditions (any ability, up to 3, all must be true): only while the owner's health (hearts or %), hunger, level, XP bar level, kill streak or money is above or below a number. "Above" and "below" don't include the number itself. Level, kill streak and money count as 0 on game modes without them. When a condition stops being true a fight ends, a blast is refused without using its cooldown, and a potion effect from the pet comes off.

Pet levels #

Pet levels and XP (/manage/pets/levels, Pets → Levels and XP; network/Cosmetics/Pets.sk). Every pet a player owns has its own level, from 1 up to the level cap (20 by default; a pet's page can give it its own cap, empty uses this one). A pet earns XP only when one of its abilities actually works in-game: a fight hit lands, a blast hits at least one target, a heal heals, a block blocks, or a potion effect is put on its owner. A pet without abilities never levels, unless it's fed pet treats (custom items with Pet XP set, see Items and economy).

  • XP per use is set per ability type (defaults: fight 1, blast 5, heal 2, block 3, potion 0). Potion effects work on their own while a pet is out, so they give no XP unless you change it; otherwise a pet would level while its owner stands still.
  • It can't be farmed. Servers count uses and send them every 30 seconds; the panel decides the XP. Each ability of each pet counts at most "Most uses that count a minute" times a minute (20 by default), and never more often than its cooldown allows. Uses only count for the pet the player has out, for abilities it has, on servers where pet abilities are on, and stop at the cap. If the panel can't be reached the uses are queued.
  • The curve is how much XP each level needs, and is hard by default: exponential (each level needs "growth" times the one before; default 100 XP from level 1 to 2, growth 1.35, about 85,000 XP in all to reach 20) or polynomial (level n needs base × n^growth: steadier). Preview the table shows the XP for each level, in all, and the least time a pet that only fights would take, before you save. Changing the curve doesn't change anyone's XP, only the level it makes.
  • Levels make pets stronger. Each level above 1 makes a fight's and a blast's damage, a heal's amount and a block's chance stronger by the ability's Stronger per pet level (%) (on the pet's page, 2% by default, up to the field's maximum). Servers get the numbers already scaled, and the /pet menu shows them.
  • Players see it over the pet's head ("Lv 3"), in /pet (level, an XP bar and XP to the next level; "Gets 2% stronger each level" with the abilities) and on the portal's Pets page. Levelling up tells the player and respawns the pet with its new strength. Staff see each owner's level on the pet's page and on a player's page (Settings and pets).

Every change on this page is in the audit log (pet.levels), as are changes to a pet's own cap (pet.update).

World and gameplay rules #

World and gameplay rules (Servers → Groups → edit, and Servers → edit a server). Each server group sets: instant respawn, difficulty, PvP, fall damage, hunger, health regeneration, natural mob spawning, weather (normal / always clear / always rain), time (normal / always day / always night / stopped at a set time, in ticks), fire spread, explosions breaking blocks (off: they still hurt; dungeons and islands keep their own setting), building (staff with network.build can always build), void rescue (on by default: anyone who drops below the bottom of the world is taken to spawn, checked twice a second and again when the void hurts them, so they keep everything they carry; if something still kills them in the void they keep their items and XP; /kill still works, since only players below the world are rescued; they're told on the action bar, msg.rules.void_rescued; in a dungeon they go back to its start instead of spawn, so they stay in the raid, msg.rules.void_rescued_dungeon), game mode on join, and join/leave and death messages. A server can override any rule or leave it on "Same as group". Rules arrive with the heartbeat and are applied within 15 seconds by network/World/Rules.sk. Rules nobody has set stay vanilla. Staff with network.worldinfo can run /worldinfo in-game to see what the world they're in is really doing: time, rain and thunder, the daylight, weather and mob spawning game rules, difficulty, mob caps, the panel's rules, and how many monsters, slimes and animals are loaded.

Per-world rules #

Per-world rules (Servers → Groups → edit → Per-world rules, and Servers → edit a server → Per-world rules) set rules for one world by its folder name, like an always-day spawn with no PvP or hunger, or a pvp_arena with no building. Add a world, type its name and change only what it needs: every rule left on "Inherit" follows the rest. The rules a world can set are time (including a set time in ticks), weather, difficulty, natural mob spawning, PvP, fall damage, hunger, health regeneration, fire spread, explosions breaking blocks, building, void rescue, instant respawn, death messages and keep inventory (which otherwise comes from the category's Keep inventory setting).

  • Order (the first that sets a rule wins): the world on the server, the world on the category, the server's rules, the category's rules. In one list an exact name wins over a pattern, and a longer pattern over a shorter one.
  • Patterns: * stands for any characters, so arena_* covers arena_1 and arena_red, and * covers every world. Names aren't case-sensitive. Up to 50 worlds per category or server.
  • Worlds that don't exist yet get their rules as soon as they're made or loaded (on world load in network/World/Rules.sk), so making a world called spawn later picks up the spawn rules. Changes on the panel apply within 15 seconds, like the other rules.
  • Player rules (hunger, PvP, fall damage, building, void rescue, instant respawn, keep inventory) follow the world the player is in. /worldinfo shows the rules of the world you're standing in.
  • Each saved world shows a summary of what it ends up with once everything is merged.
  • Dungeons and islands aren't touched. Dungeon worlds (dungeon_<raid>) and player islands make their own worlds and set their own time, mob spawning, explosions and the rest, so per-world rules never apply to them, not even through *. Islands skip the server's world settings as before; dungeon worlds take the server's difficulty, PvP and the like, but not its time, weather or mob spawning (the dungeon stops the clock at day or night itself).

The heartbeat sends the rows as group.world_rules, already in the order they apply (App\Support\WorldRules::wire): world, match (a Java regular expression), source (category or server) and rules (only the rules that row sets).

Fishing loot #

Fishing loot (Servers → Groups → edit → Fishing loot). Extra drops per category when a fish is caught. Each drop has a chance (a percentage, decimals allowed) and is rolled on its own, so one catch can win several. A drop can be an item (material, data, amount range, custom name, enchantments like LURE:3), a custom item by its ID, in-game money (money_give_command in config.sk), global coins (paid by the panel, only for real coin drops, at most once every 2 seconds per player), XP levels, or a console command ({player}). Each can have its own message and be announced to the server. "Replace the vanilla catch" removes the normal catch when something is won. Wins count towards the Fishing loot won stat.

Survival #

The survival scripts are the old ones with their storage swapped for the network panel, the same way Pit was done:

  • Saves. The player cache (player_cache_<uuid>, with its data and global parts) is loaded from the panel when a player joins and saved with every autosave and on quit, as data.survival and data.survival_global in the Survival category's save. All survival servers share it. Quests, dialogues, levels, class buffs, fragments, the scoreboard and action bar read it exactly as before.
  • Network stats. Level, XP, kills and kill streak are mirrored both ways into the network's variables, so /stats, leaderboards, the portal, name tags and staff edits on the panel all see them. New stats: survival quests and dialogues completed, ores mined whole or shattered, fragments combined.
  • Money stays in your economy plugin. Anything the network does to {coins::} (/pay, Item Shop, rewards, staff edits) is applied to it, and economy changes go back to the panel.
  • No old cloud provider: everything is saved on the panel. A player with no survival save there yet starts fresh.
  • Replaced by network modules (so not copied): the old connector, /stats, /language, /email, /settings, /profile, titles and chat colours (badges now).
  • Secrets. The old Server/Variables.sk had the old cloud API token and the /neutine-worker key written in it. Both are gone from the scripts: the worker key is read from plugins/Skript/survival-worker-key.txt (NPC commands keep working once you put the same key there). Treat the old ones as leaked and change them. /alchemist now opens the fragments menu directly, so the key no longer shows up in command logs.
  • /back (Player/Commands/Back.sk). After a death, /back takes the player to where they died, once, within 10 minutes (not a death in the void). Otherwise it opens a menu of their last 10 teleports: every teleport is logged (where they were before /home, /spawn, /tpa, a portal or another plugin's teleport; ender pearls, chorus fruit and hops under 10 blocks aren't), newest first, with the world, coordinates, how long ago and what moved them, and they click one to go back. /back list always opens the menu, with the death spot at the top while it's open. Going back means standing still for 3 seconds, out of combat; being hit cancels it. The log survives restarts. It replaces EssentialsX's /back (as well as /eback, /return and /essentials:back). Change the times and the number kept in the options: at the top of the file.
  • Essentials can't answer these. /back, /spawn and /tpa (and the rest) are run straight from PlayerCommandPreprocessEvent whatever form is typed (/eback, /essentials:spawn...), and every form of /home, /homes, /sethome, /delhome and /renamehome is rewritten to Skript's own /skript:home and so on, before any plugin sees it. The server's command map isn't touched.

Homes #

survival/game/Player/Commands/Homes.sk replaces Essentials' homes. Homes are kept on the panel and belong to one server, so Survival US and Survival EU each have their own. Limits are per server.

  • Commands: /home or /homes opens the menu (click to teleport, right click for rename and share, shift right click twice to delete). /home <name>, /home <owner>:<name> for a shared home, /sethome [name], /delhome <name>, /renamehome <name> <new>, /home share|unshare <name> <player>.
  • Sharing: /home share <name> <player|crew|friends> [time] (time like 30m, 12h, 7d, 2w; none = until stopped), /home unshare <name> <player|crew|friends>. Crew and friend shares are for whoever is in the owner's crew or friends at the time: leaving the crew, being kicked or being unfriended ends access straight away, and a player who leaves or is kicked from a crew stops sharing their own homes with it. Players can drop a home shared with them by name; crew and friend shares are the owner's to end. Shared homes show in /homes with how they're shared and how long is left.
  • Codes and links: /home code <name> [uses|unlimited] [time] [access time] makes a code (default: 1 use, works for a day, access until removed; at most 30 days and 1000 uses). The owner gets [Copy code] and [Open link] buttons; others type /home accept <code> on that server or open the link (/account/homes/code/<code>) on the portal and press "Add it to my homes". A home can have several codes. /home secret <name> [player] is a one-use code for 24 hours; with a player online it's sent to them with a clickable [Accept].
  • Portal: under Homes, each home's sharing panel shares with a player, the crew or friends (no end, 1 hour, 1 day, 7 days or 30 days), lists who it's shared with, and makes, lists and stops codes and links. "Shared with you" says how and until when. Tables home_shares.expires_at, home_group_shares, home_codes.
  • Limits (/manage/homes, permission homes.manage): set by the player's main rank (Players → Ranks), 5 by default. Someone who drops to a lower limit keeps their homes but can't add more. The same page sets an override for one player, higher or lower than their rank's, on one server or on every server. An override for a server comes before one for every server, and both come before the rank. A server can be chosen once its Homes.sk has talked to the panel, or once it has homes.
  • Teleport delay (same page): how long players stand still before /home takes them there, 3 seconds by default, and a separate delay for Premium players, 2 by default (used when it's shorter). 0 teleports straight away. Moving or taking damage cancels it. It's sent with each player's home list (warmup), so a change applies the next time they use /home; until a server has had a list for them, home_warmup in its config.sk is used.
  • Icons: each home can show as any item in /homes. In-game, hold the item and press Q on the home in /homes, or type /home icon <name> (/home icon <name> reset goes back to the default: grass, netherrack or end stone by its world). On the portal, players pick from a list of common items under Homes (with the pictures from Items → Item icons where there are some). Shared homes show the owner's icon. Stored as homes.icon.
  • Portal: players rename, delete and stop sharing homes under Homes. Homes of a deleted server stay there until they delete them.
  • Islands: /sethome is refused on an island (its world is the owner's UUID, or <uuid>_<n>), in game and by the panel (HomeService::set), since islands are rebuilt in a new world each time they load and /island already gets players back. Homes set on an island before this still show in /homes and on the portal so they can be deleted, but teleporting to one is refused with a message saying to use /island. The portal can't set homes, only rename, share and delete them.
  • Moving from Essentials: each player's homes in plugins/Essentials/userdata are copied once when they join, even over the limit. Names are cut to letters, numbers, - and _, 16 at most. Add essentials:home, essentials:sethome, essentials:delhome and essentials:homes to the survival category's blocked commands, or those forms still reach Essentials.
  • Importing everyone at once: on /manage/homes, choose the server and upload a zip of its plugins/Essentials/userdata folder, or a text file with lines like player-uuid = home, world, x, y, z (yaw and pitch can follow). Repeat for each server. Homes a player already has aren't changed, but one they've deleted comes back if you import it again. If the zip is over the upload limit, copy it to the panel's host and run php artisan network:import-essentials-homes SURVIVAL_US_1 /path/to/userdata.zip. The last argument can also be the folder or a text file. A home saved with only a world UUID and no world-name can't be matched to a world, so it's counted under "Couldn't be read".
  • If the panel is down: teleporting still works from the last list seen on that server. Changes wait until it's back.
  • In config.sk: {-net::cfg::home_warmup} is the seconds to stand still before teleporting (3 by default, 0 for none). {-net::cfg::home_blocked_world::<world>} set to true stops homes being set in that world.

Islands #

Islands (survival/game/Server/Game/Islands/Island.sk, panel: Survival → Islands, permission islands.manage): each player's own island on survival, in a world named after their UUID. Turn on the Islands rule for the survival category.

  • Schematics: upload a WorldEdit .schem (//copy, then //schem save <name>; Sponge versions 2 and 3, up to 256 blocks a side), or add the built-in starter island (grass, a tree and a chest). New islands are built from the default one, centred on 0, 0 at the build height. Chests in the schematic keep their items. Each schematic can be seen in 3D.
  • Settings: how far out saves look (only for islands built wider before sizes existed; saves always cover the widest size), the build height, minutes before an empty island is put away, minutes between saves, and whether players can share islands at all.
  • Rules belong to each island and can be changed by the owner in game (/island rules), by the owner on the portal (Play → Island), or by staff on the island's page: PvP, monsters spawning, fire spreading, explosions breaking blocks, keeping items on death, time of day, weather, and whether shared players can build and open chests. While the island is loaded, changes reach its server straight away. Otherwise they apply the next time it loads.
  • Rules menu in game (Survival → Islands → Rules menu in game): staff can change the /island rules menu's title and each button's icon (a material name such as IRON_SWORD, or one with data like WOOL:14; a name the server doesn't know shows as stone), name and description (up to 6 lines; colour codes work). Empty fields keep the default text and its translations, and Put back the defaults undoes it all. The on/off or current value and the "Click to..." lines are always added under the description. Servers get it with the island settings, within a minute.
  • Sharing with the owner's crew and/or friends is off until the owner turns it on. Shared players visit with /island visit <player>. Anyone no longer shared with is sent to spawn, and nobody else can teleport onto an island. Staff with network.island.admin can go anywhere.
  • Saving: the panel keeps every island: its blocks (with every block state), chest contents (exact items), mobs and spawn. Each time an island is needed, the server builds it in a brand-new, empty world from that copy, so an island is never built on top of an old copy. Every new world gets a name no world on that server has had (<uuid>_<number>), so even if bits of an old world are still on disk (the server can still be writing one just after it's unloaded), they're never loaded as the new island. Old island worlds are unloaded and their folders deleted a few minutes later by a cleanup that runs every 2 minutes. While it's loaded, a copy goes to the panel every few minutes when it changes. The save covers just the blocks that are there, so it doesn't creep outwards from save to save. Before a save is sent, the server checks it has every block exactly once; if not, it isn't sent and the survival console says so (Islands: ... walked N blocks instead of M). A build whose data doesn't add up is logged the same way. An island saved with extra copies by an older script keeps them: reset it from its staff page (it's built again from the schematic), or let the player clear the copies in game.
  • Putting away: an island is put away when its owner leaves the server, or when nobody has been on it for a few minutes (the setting). Everyone on it is sent to spawn (or the main world's spawn if there's no spawn), it's saved to the panel, and the world is deleted. If that last save doesn't reach the panel, or the server stops with it loaded, the world folder is kept and the island is loaded from it next time, then saved again. A player who quit while on an island is put back where they were when they rejoin.
  • Staff can see every island (where it's loaded, last save, sharing), change its rules, view it in 3D, reset it from a schematic, or delete it. A reset or a delete wipes the island, never builds over it: if it's loaded, everyone on it is sent to spawn (kicked if they can't be moved within a few seconds), the world is unloaded without saving and its folder deleted, and its saved copy on the panel goes. Then a new one is built from the start, straight away if the owner is on that server, else the next time they type /island. Saves still on their way from the old copy are ignored (each copy carries the panel's reset time it was built from), and a new island never picks up a world folder left from an old one.
  • Portal (Play → Island): a three.js 3D model of the player's island from its last save (drag to turn, scroll to zoom), its rules and sharing, and who can visit.
  • Showing it on the profile: under Show it on your profile on the same page, players can turn on showing that 3D model on their public profile (/player/<name>, islands.show_on_profile, off by default). Visitors only get the model's blocks and colours (/player/<name>/island, 30 requests a minute): no coordinates, chest contents, rules or who can visit. A private profile hides it from everyone but the player and staff, and a profile only ever shows its owner's island.
  • No portals: nether and end portals can't be made on islands. Lighting obsidian with flint and steel or a fire charge, and putting eyes of ender in end portal frames, are refused with an action bar message, and PortalCreateEvent stops every other way (fire spreading, dispensers). Nobody is let off, staff and server operators included (a rank with every permission would always be).
  • Players resetting their own island: only on the portal (Play → Island → Reset your island), never in game. Email me a code sends a 6-digit code to the account's verified email (it lasts 15 minutes; 5 wrong tries and it's gone; 3 codes per 10 minutes). Entering it wipes the island exactly like a staff reset (above). Both steps are in the audit log. A save already on its way from the old copy is ignored by the panel (servers send when their copy was built), so it can't undo the reset.
  • Block textures: the 3D views (staff and portal) draw blocks as plain colours until staff upload the website's resource pack (Items and economy → Resource pack). Blocks use their _top, _side and _bottom textures, stairs, slabs and walls use the block they're made of, and grass, leaves and water are coloured as in game (App\Support\BlockTextures). Animated textures show their first frame, and blocks with no matching texture keep their colour. Non-cube blocks (flowers, torches) are still drawn as cubes. The Islands page says which pack is in use and links to it.
  • Island sizes (Survival → Islands → Island sizes; App\Support\IslandSizes, column islands.size_level): each level is a width (the island's world border, blocks across) and a height (how many blocks above the island's level, the build height setting, blocks can be placed), and a price in global coins. Every island starts at level 1, which is free. Until staff change them there are 5 levels: 32 × 64, 48 × 72 (5,000), 64 × 80 (10,000), 80 × 88 (15,000) and 96 × 96 (20,000). Each level must be at least as big as the one before; up to 20. Fill up to 5 levels adds levels that go up by the same step as the last two (16 wide, 8 tall and 5,000 coins when there's only one), and Use the defaults puts them back. Owners buy the next level for good with /island upgrade (shows their size and the next one's price) then /island upgrade buy, or on the portal (Play → Island → Size). Either way the price paid is the one they were shown: a price changed since is refused, never charged. A loaded island gets the new border at once. Placing a block above the height limit is refused with an action bar message (staff with network.island.admin can). Upgrades are in the audit log (islands.size). API: size and upgrade actions on POST /api/v1/server/islands. Islands built before sizes existed get level 1's border (32 wide by default): set level 1 bigger first if your islands are wider than that.
  • In-game: /island (alias /is): the island menu when the player's island is already loaded on that server; otherwise it loads the island (making it the first time) and takes them there. /island go (or /island home) always takes them there. /island menu (alias /island gui), /island visit <player>, /island rules, /island setspawn, /island upgrade [buy], /island subscribe [buy] (see below).
  • Menus: /island menu opens one chest menu with Go to your island, Rules and sharing (the rules menu), Size and Subscription. /island upgrade and /island subscribe open those last two straight away. Size shows the island's size now and the next size up with its width, height and price; Subscription shows whether it's active, with its end date and time (UTC) and the time left (like 29d 4h, counted by the panel's clock from until_text and seconds_left, so a wrong clock on the game server can't change it), and the coins offer. /island subscribe says the same in chat. Clicking the offer buys it at the price shown (a barrier means they're short, and by how much), then the menu opens again with the new size or days. Every island menu has a Back arrow to the main one. Adding buy (/island upgrade buy, /island subscribe buy) still pays from chat. Texts are msg.island.gui_* under Translations.
  • The server's own world rules (Rules.sk) leave island worlds alone. The group's Players can break and place blocks rule still applies.

Durability warning #

Low durability (network/Items/Durability.sk; rules under Servers → Groups → edit, overridable per server). Each time a tool, weapon or piece of armour loses durability and has no more than Warn at this much durability left (10%) left, the shared action bar shows ⚠ Tool low, ⚠ Weapon low or ⚠ Armour low with the item's name and what's left (source durability, priority 55, 3 seconds), next to the other info there rather than replacing it. Low durability warning (on) turns it off. Sound when durability drops plays a sound Only while it's low (default), Every time it drops or never, and Durability sound picks it: a low note (default), a high note, a click, an anvil or an item breaking. Texts are msg.durability.* under Translations. Works on 1.8 Pit and modern servers.

Dungeons #

Dungeons (Survival → Dungeons, /manage/dungeons, permission dungeons.manage; App\Services\DungeonService, in game /dungeon in survival/game/Server/Game/Dungeons/Dungeon.sk). Raids for up to a few players in a world built from a schematic. Turn on the Dungeons game rule for the category (off by default; survival servers, which build them). Each dungeon has Turn off / Turn on on the Dungeons page (and On on its form): off, it leaves the menus, nobody can start it and raids still forming are dropped; raids already running finish. Each dungeon's Where it's on picks categories and single servers to have it only there (tick nothing: every server with the rule on); daily and weekly rotations pick from the dungeons each server has, so different servers can have different ones open. The Dungeons page shows where each is and which servers it's open on now; the portal's Open now says which servers.

  • A dungeon has a name, menu icon and description; when it's open (Always, Daily rotation or Weekly rotation); the most players in a raid (4); a time limit (30 minutes); attempts per day, or per week for a weekly one (3; 0 for no limit), and whether only clears use up an attempt; who can start or join it (the same requirements as joining a server: play time, network level, a level in a category, rank, quests, badges...); and the rewards every player in the raid gets for clearing it (global coins, items, badges, global values, commands, Premium, Crew: Premium and island access days).
  • The schematic is a WorldEdit 7 .schem (//schem save). Put signs in it: one with a spawner's code (DSP-XXXXX, on any line) marks where that spawner spawns, and one saying [start] is where players arrive (without one, they arrive at its middle). A number on the [start] sign ([start] 5, or 5 on another line; up to 32) makes a start area: players arrive, and come back after dying, on a safe spot (room to stand, over a solid block) anywhere within that many blocks of it, and no spawner places a mob inside it (a spawner whose own sign is in the area still spawns there). A [wall] sign with a spawner code ([wall] DSP-ABCDE) makes a wall that stops players hiding from that spawner's mobs or boss and hitting them from cover: it goes up when the spawner spawns its first mob and comes down once every spawner with that code has spawned all its mobs and they're dead. Dungeon mobs show their health over their heads, after any name they have, in hearts: ❤ 7.5/10 (green over half, yellow over a quarter, then red), updated as they're hurt or healed. Bosses with a boss bar show it on the bar instead (Name ❤ 120/400; on every server, not just dungeons), and a boss without one shows it over its head like the rest. When a wall (or a zone wall) comes down, everyone in the dungeon gets a WALL OPENED title on screen ("The way ahead is clear"; both under Translations, msg.dungeon.wall_open_title and msg.dungeon.wall_open_sub) and the action bar line. On its own the sign is one block; two signs saying pos1 and pos2 make a box between them (up to 2,048 blocks; give each pair a name for more than one: pos1 a, pos2 a). It's bedrock unless the sign names a block (IRON_BARS, GLASS...). A spot where a player stands when it goes up is left open, so nobody is stuck in it. The upload is refused if a [wall] sign has no spawner code, its code has no spawner sign in the schematic, or a pos1 has no pos2. Every other sign (“Built by …”, directions) is built as it is, with its words (the front of the sign; & colour codes work), and so is a [wall] sign without a spawner code, which is left alone rather than refused. Signs are read whichever way the Minecraft version that saved the schematic stores their words (JSON text, or since 1.21.5 the text itself), and the upload message lists what it read on the signs it kept as ordinary signs, so a mistyped code (DSP-ABCD) shows up straight away. Signs are read when the schematic is uploaded, so after a fix to how they're read, upload the schematic again. When it's uploaded the panel finds those signs, takes them out of the build (they become air) and keeps their spots as markers. The dungeon's page lists the codes it found and warns about codes no spawner has.
  • Difficulty (Dungeons → Difficulty settings): staff make the difficulties dungeons can have (a name and a colour each, easiest first), and each dungeon picks one on its page. A dungeon with none is Unrated (the default). Players see it in /dungeon (“Difficulty: Hard”, in its colour) and on the portal's Dungeons page; staff see it in the dungeon list. Renaming a difficulty keeps its dungeons on it; deleting one makes them Unrated.
  • Testing (a dungeon's page): tick Testing and list Testers (usernames of players who have joined before). While it's on, only those players see the dungeon in /dungeon (marked TESTING) and on the portal, and only they can start a raid; anyone can still join a tester's raid. A daily or weekly dungeon being tested takes no rotation slot: it's always open to its testers. Untick it to open it to everyone.
  • Spawners (Dungeons → Spawners; search by name or code, and filter by difficulty, what they spawn and whether a dungeon uses them): each has its code, a difficulty (from Difficulty settings, Unrated by default; for sorting and finding them), what it spawns (mobs of a type, elite mobs (Combat → Elites) or a boss (Combat → Bosses)), how many in all, how many alive at once, seconds between spawns, how close a player must come for it to start, how far around its sign they appear, how far from its sign they may get (Keep within, 16 blocks by default: one that gets further is put back by its sign, and endermen can't teleport further; 0 for no limit, never less than the spread + 2), health and damage multipliers, the XP each drops, a name over them, a hologram over its sign in the dungeon (blank: the name over them, else its name), with "Killed 2/6" under it, counting up as its mobs die and green once all are killed, up to 10 drops (a material or a custom item's ID, how many or a random amount ("1 to 3"), the chance in %), and whether they must be killed for the dungeon to count as cleared. The same code can go on many signs and in many dungeons.
  • Teleporters (Dungeons → Teleporters): each has a code (TP-XXXXX). Write it on a sign in the schematic where the teleporter should stand, and [dest] with the code on the sign it takes players to (both are taken out of the build; a teleporter with no [dest] sign, or two, is refused on upload). It looks like a floating block (any block, like END_PORTAL_FRAME or BEACON) or a mob that stands still, can't be hurt and does nothing, with a hologram over it saying whether it's open. It stays shut until every spawner it needs has spawned all its mobs and they're dead (picked by code on the teleporter's page, as many as you like, so they never have to fit on a sign; none ticked: open from the start). When it opens, everyone in the dungeon is told and its particle effect (Cosmetics → Particle effects) starts over it, played again whenever it ends. A right click takes the player to the [dest] sign.
  • End point (an [end] sign in the schematic; set on the dungeon's page under End point): it looks like a floating block (BEACON by default), a mob standing still, or a player (an armour stand wearing a player's head and iron armour), with a hologram over it. In a dungeon with one, clearing it doesn't end the raid by itself: the end point opens (everyone gets a "Cleared! Go to the end to finish" title) and the raid ends, cleared and with its rewards, when a player right clicks it. Its optional dialogue (up to 20 lines, each with a speaker, the words and the seconds until the next; {player} is who clicked, {dungeon} its name) is said in chat to everyone in the dungeon first, a line at a time; the time limit stops counting while it plays. A schematic can have one [end] sign.
  • Zones (written on signs): add zone 1 (or zone: boss, up to 16 letters, digits or _) to a sign. A spawner sign with a zone (DSP-ABCDE / zone 1) puts that spawner in zone 1 on that sign only, so the same spawner can be in another zone, or none, elsewhere. A teleporter sign with zones (TP-ABCDE / zone 1, or zone 1 zone 2) opens when every spawner sign in those zones has spawned all its mobs and they're dead (instead of the spawners ticked on its page). A zone wall ([wall] / zone 1, a block of its own or a pos1/pos2 box, bedrock unless the sign names a block) is up from the start of the raid until zone 1 is cleared. A zone wall for a zone no spawner sign is in is refused on upload.
  • Stuck raids: a raid still running 15 minutes past its time limit (the server went down and never reported it) is failed by itself, so nobody stays "in a raid". Staff can end any forming or running raid by hand in Latest raids on the Dungeons page, as failed, abandoned or cleared (which gives the clear rewards to everyone still in it), and in game with /dungeon end (or /dungeon end cleared; network.dungeon.admin) while standing in it.
  • A finished dungeon's world is deleted: it's unloaded and deleted when the raid ends, tried again every 10 seconds until nobody is left in it (players on the respawn screen keep a world loaded), and any left over after a restart go when the script loads. Nobody can sleep in a dungeon, and anyone whose respawn point or logout spot is in a dungeon that's gone goes to spawn instead.
  • XP: a dungeon mob drops its spawner's XP as orbs and gives the killer that much network XP (times hardcore's multiplier); the general mob XP rules don't add to it.
  • No PvP in dungeons: players (and their arrows and potions) can't hurt each other there.
  • Schematic size: dungeon schematics can be any size (islands stay at 256 a side). Staff are warned when one is bigger than Warn about schematics bigger than (512 blocks a side by default, in the dungeon settings).
  • Building a raid: when a raid begins, its world is built from the schematic a slice of every tick (blocks go in for about 30 ms of each 50 ms tick, then it waits a tick, so a big build is as fast as the server allows without lagging it). Nobody goes in until it's done: the party sees a Building the dungeon… 45% bar, and the time limit, spawners and zone walls only start once every block is in. A build that takes over ten minutes is called off (abandoned). The chunks holding holograms, teleporters and the end point are kept loaded for the whole raid (they're made before anyone is there, and the server would otherwise unload them and delete those entities with them).
  • /raid (and /raids) is another name for /dungeon, everywhere: the menu, the commands allowed inside a dungeon, and the combat command block. Announcing: after picking a dungeon (and Normal or Hardcore), the leader chooses Announce it (everyone on this server who isn't in a dungeon is told who started a raid of which dungeon, and to type /dungeon to join) or Keep it quiet. Room to spawn: a spawner only puts a mob where there's a solid block to stand on and air for its height (two blocks, three for endermen, iron golems, wither skeletons, withers and ravagers, five for ghasts), trying up to ten spots in its spread a few blocks up and down, then its own sign; with no room anywhere it waits for its next turn instead of spawning it inside blocks.
  • Rotation (on the Dungeons page, Rotation and raids): Always-open dungeons are open every day. Of the Daily rotation ones, Daily dungeons open each day (1) are picked each day, and of the Weekly ones Weekly dungeons open each week (1) each week, the same pick all through the day or week. A weekly dungeon can be cleared once a week and its coins, item amounts and subscription days are multiplied by Weekly rewards times (2). Raids begin by themselves after (60 seconds; 30, 60, 90 or 120): others can join a raid until then, and the leader can begin it sooner. Its party sees a boss bar counting down, and the last five seconds as big 5, 4, 3, 2, 1 titles, and the raids list in /dungeon shows how long is left. Raids in progress show their time left (from the time limit) in the /dungeon raids list and on the portal's Dungeons page, where it counts down live; forming raids show when they begin. A player can pick their own time for raids they lead with the Auto start button in /dungeon (it cycles 30, 60, 90 and 120 seconds; a raid of theirs still forming takes the new time at once). A raid still forming two minutes after it should have begun (the server went down, the leader left) is dropped.
  • In game: /dungeon (aliases /dungeons, /dg) opens the menu with two buttons. Dungeons available (/dungeon available) lists the open dungeons: each shows its name, description, max players and time limit, then when it's open, attempts left, what it needs and its first few rewards (or why the player can't start one); clicking one starts a raid (the player leads it), and right clicking opens its rewards menu: the rewards for clearing it (custom items as the item itself; weekly ones already multiplied), each item its spawners' mobs can drop with its amount (or range), drop rate and which mob drops it, and about how much XP its mobs give in all. Raids on now (/dungeon raids) lists the raids on that server: those taking players (click to join) and those in progress (how long they've run), each with its leader and party. The leader begins it from the menu or with /dungeon begin; /dungeon leave (or /dungeon quit) leaves (the leader leaving a forming raid ends it). Beginning builds a new, empty world dungeon_<raid> from the schematic and takes the party to its start.
  • Rewards everywhere: wherever a dungeon's loot shows, drops read the same way, amount (or range), item and drop rate ("2 x Bone (50%)", "1-3 x Rotten Flesh (25%)"), and clear rewards say they're guaranteed: the dungeon item in the in-game menu (first few clear rewards and drops), its rewards menu (a 100% drop rate on each clear reward), the portal's Open now list, the staff Spawners list (a Drops column) and each dungeon's form (its spawners' drops).
  • Hardcore: tick Hardcore mode on a dungeon (off by default) and players starting a raid choose Normal or Hardcore. Hardcore raids: every mob has 3x health and deals 3x damage, mob drops are 3x and the clear rewards are 3x (on top of the weekly multiplier). Whoever dies is out: they respawn back where they were, the party is told, and they're marked Died (hardcore) with no rewards; once nobody is left in it, the raid fails. Hardcore raids are tagged on the Dungeons page, the portal and in the menus, the boss bar says HARDCORE, and the raid overview shows the mode.
  • Holograms and keys: a dungeon's Hologram over the start floats over its [start] sign (blank: "Spawn point"). Needs a custom item makes it need one (a dungeon key): how many, whether the party leader needs it to start the raid or everyone needs it to start or join, and whether beginning the raid takes it. The menu shows it ("Needs: 1 x Crypt Key") and the server checks inventories when players click and again when the raid begins; anyone who no longer has it then stays out and is marked as having left.
  • The raid: each spawner starts when a player comes within its range and spawns until it has spawned its total. It's cleared when every required spawner has spawned all its mobs and they're dead; it fails when the time runs out or everyone has left. A boss bar shows the time left, and the survival scoreboard shows the dungeon's name, Area Killed (the spawner nearest to them, killed / total) and Dungeon Killed (every spawner), each turning green when all are killed. It's always night in a dungeon unless its Time of day is set to Day (the clock is stopped either way). Players have 3 lives in a raid by default (Lives in a raid in the dungeon settings; a dungeon can set its own under Lives, blank for the network's; tick Unlimited lives in either place, or enter 0, for no limit, so players keep going back to the start until the time runs out; hardcore is always 1): each death tells them how many are left (a "Last life" title on the last), and on the last death they're out of the raid, back where they were and marked as died, with no clear rewards. Death messages for players who die in a raid are shown as usual unless staff tick Hide death messages in raids in the dungeon settings (off by default); a dungeon can choose Show or Hide under Death messages in a raid, or follow the network's setting. While hidden, nobody gets the chat line, custom death messages included (network/Chat/CustomMessages.sk checks the raid). A player who dies in it keeps their items and XP and goes back to its start. No mobs spawn naturally in a dungeon world: the mob spawning game rule is off there, and natural spawns of every kind (spawner blocks in the build, patrols, reinforcements, jockeys...) are cancelled, so only its spawners' mobs and their bosses' summons appear. Mobs there only fight players: they never target another mob (an iron golem or wolf from a spawner won't go for the zombies), and a mob's hit, arrow, fireball or explosion does nothing to another mob. Explosions (creepers, TNT, fireballs...) break no blocks there, so the build stays intact, unless the dungeon's Explosions break blocks box is ticked; they still hurt players either way. Nobody can teleport in but its party (staff with network.dungeon.admin can). Inside a dungeon players can only use /dungeon and the commands in Commands players can use inside a dungeon (the dungeon settings: by default /msg, /r, /stats, /recipes, /help and a few more); /back, /home, /spawn, /tpa and every other command are refused, in their plugin:command forms too (staff with network.dungeon.admin can use any). No one can teleport inside a dungeon either: ender pearls can't be thrown (none is lost), and chorus fruit, commands and other plugins' teleports are refused. The only moves are the raid's own: arriving, going back to the start after dying, and leaving. Being teleported out any other way (staff pulling someone out) leaves the raid. Players can't change a dungeon: no breaking or placing blocks, no buckets, no lighting fires, no editing signs, and no breaking or turning item frames and paintings or taking from armour stands (staff with network.dungeon.admin can). Nobody tramples crops in a dungeon (players or mobs), and players can't use the blocks in Blocks players can't use inside a dungeon (the dungeon settings; by default anvils, crafting, enchanting and smithing tables, furnaces, brewing stands, grindstones, looms, stonecutters, beacons, ender chests, beds, respawn anchors and lecterns; a * matches any part of a name, like *_BED). Doors, buttons, levers and chests not on the list still work. Leaving a raid that has begun (/dungeon leave, teleporting out or logging off) tells everyone still in it, and the player is marked Left mid raid (action left, or left in the finish report): they get no clear rewards, it still uses an attempt, and it doesn't count as a clear (weekly limit, Most clears). If the leader leaves a raid that has begun, the next player still in it takes over (everyone is told, and the server sends the panel its pick with leader; without one the panel picks whoever joined first). The overview (/dungeon overview) then says Led by the first leader and Taken over by the new one (taken_over_by). Leaving after the clear is fine. At the end everyone sees how they did. After a clear a title tells them how to leave: /dungeon leave takes them back now, otherwise a boss bar counts down 120 seconds, with a title at 10 seconds left and at 5, 4, 3, 2 and 1, then everyone still in it is sent back and the world is deleted (sooner if everyone has left). After a failure they're sent back after 10 seconds. "Back" is where each player was when the raid began (spawn if that world is gone) (and any left from a restart are deleted when the script loads).
  • Overview: /dungeon overview (or Your last raid in the menu) shows the player's last raid that has ended on a server of this category: the dungeon, whether it was cleared, failed or abandoned, its time, leader, server and when it ended; the raid's total damage, kills and deaths; their own stats (with their place in damage and what they got); and a head for everyone in it (most damage first) with their damage and share of it, kills, deaths, the leader and anyone who left mid raid. With none: "You have no previous participation in a raid." After every raid the players are told about it in chat.
  • Counting: damage each player dealt to the dungeon's mobs, the damage they took in the raid (damage_taken: from anything, after armour, while the raid is running), their kills and deaths go to the panel when it ends (POST /api/v1/server/dungeons, action finish), which gives the rewards and replies with what each player got. Staff see the latest raids on the Dungeons page; players see theirs on the portal (Play → Dungeons), which also lists the raids now on every server (taking players, or in progress, with the party, its leader, the server and since when; yours in bold) and: how each went, whether they led it, their damage, kills and deaths, and leaderboards for the most damage, most enemies killed, most clears, most hardcore clears, most raids led, the fastest clear and the fastest party clear, in every dungeon or one (fastest clears need one) and for all time, this week or this month. Clears count only players who stayed to the end. Staff can also make dungeon leaderboards for holograms, /leaderboard and the website (see Leaderboards in quests.md).
  • Stats (Dungeons → Stats, /manage/dungeons/stats, dungeons.manage; App\Services\DungeonStats, charts from App\Support\StatChart): raids by the time they began (raids still forming aren't counted). Period: last 24 hours (by hour), 7, 30 or 90 days (by day), or custom dates (From and To, up to 366 days; 2 days or less is by hour). Filters, combined and kept in the address so a view can be shared: dungeon, difficulty (or Unrated), mode (Normal or Hardcore), schedule (Always, Daily, Weekly), server and party size (1 to 4, or 5 or more). Headline figures: raids started, cleared, failed, abandoned, clear rate (cleared out of those that ended), average and fastest clear time, unique players, damage dealt and taken, kills, deaths, players who left mid raid and hardcore deaths; each shows how it moved since the period of the same length before (a percentage; points for the clear rate), green when that's good and red when it's bad, and what it was. Charts (hover or arrow keys for the figures; each also as a table): raids each hour or day (stacked cleared, failed, abandoned), clear rate, damage dealt and taken, and average clear time. By dungeon (click a heading to sort): raids, clear rate, average clear and deaths per raid; a dungeon's name filters the page to it. Busiest hours (raids begun at each hour of each weekday, UTC) and top players (the 10 with the most damage dealt, or click a column for damage taken, kills, deaths, clears or raids). Everything is added up in the database by hour or day (dungeon_runs.started_at is indexed) and cached for a minute. All times are UTC.
  • Tests: tests/Feature/DungeonsTest.php, tests/Feature/DungeonStatsTest.php.

Island subscriptions #

Players need an island subscription to use their island (App\Services\IslandSubscriptionService, panel: Survival → Island subscriptions, permission islands.manage). One subscription covers islands on every server and in every category, not one server group.

  • Checked by the panel. The islands API (/api/v1/server/islands) only answers get, create and build for an owner with an active subscription; otherwise it answers ok: false with subscription_required and a message saying how to get one, which the server shows. visit needs the island's owner to be subscribed; visitors don't need their own. An island already loaded when a subscription runs out stays until it's put away, and saves are always accepted so nothing is lost. When it's renewed, the island comes back as it was.
  • Islands need a subscription (on by default): turn it off and everyone can use islands, subscribed or not.
  • With global coins (on by default): up to 6 lengths, each with its days (1 to 365), price (up to 2 decimal places) and an optional label (see Items and economy → Island subscription and Pets Premium in the store). Every length is sold in the in-game /store and on the portal. /island subscribe sells the shortest. Bought in game with /island subscribe (shows the status, the offer, and how many more coins are needed) then /island subscribe buy (a refusal, such as not enough coins, says why in the game's own translations), or on the portal (Play → Island). The price the player was shown is sent with the purchase, so a price changed in the meantime is refused rather than charged. Each purchase is a coin_transactions row and is in the audit log.
  • With real money (PayPal), off by default: a price and the days it gives, paid once with PayPal on the portal (Play → Island → Pay with PayPal). It uses the Store's PayPal account and IPN (see Economy and store → Store (PayPal) and credits), as a store product of kind island that is kept on this page rather than the Store's product list and isn't in the Store's product list. Players can also buy it from the in-game /store and the website store (see Items and economy → Island subscription and Pets Premium in the store). Refunds and chargebacks take the days back. Players only see it when it's on and PayPal is set up.
  • Renewing adds the days to what's left. Every purchase or gift is an island_subscriptions row (source coins, PayPal or staff); the page lists the latest.
  • Staff can give days to a player by username (with an optional note), or end someone's subscription now (it's taken back however it was paid for). Both are in the audit log.

Pit skills #

Skills for Pit only (pit/Combat/Skills.sk), made on the panel under Pit → Pit skills (permission pitskills.manage). Players open the menu with /skills (or /pitskills), or the Skills button in the Upgrades Shop (/upgrades).

  • Buying. Each skill has a price in Pit coins and a level it needs. Left click buys or equips, right click upgrades. An upgrade costs the upgrade price times the current level, and makes the skill's numbers stronger by its "stronger per upgrade" percentage (not effect levels or health limits; chances stop at 100%). The panel checks the level and the price; the coins are only taken once it agrees.
  • Slots. Active and passive skills have their own slots. Each level in the slot list (Pit → Pit skills → Skill slots) opens one more, up to 4 of each. By default: actives at levels 1, 25, 50 and 80; passives at 1, 15, 40 and 70. With every slot full, equipping a skill takes off the one equipped longest ago.
  • Active skills use sword combos, so the kit needs no extra items. A player can have one active skill on each combo; equipping another one on the same combo swaps them.
    • Sneak + block: start sneaking while blocking with your sword.
    • Double jump: jump again in the air. Only for players with a skill on it, in survival or adventure, so staff flight isn't touched.
    • Sneak mid-air: start sneaking while in the air.
    • Drop key: press Q holding your weapon (sword, axe or the Combo Spade). The weapon stays in your hand.
  • Effects.
    • Active: dash, leap, shockwave (slam down, then hurt and knock back players nearby), grapple (pull the nearest player to you), strength, speed, heal and absorption hearts.
    • Passive: lifesteal, thorns, critical hits, dodging melee hits, healing, speed or extra coins on a kill, and resistance when a hit leaves you low.
    • CRITICAL. Every critical hit from the network's own crit system says so: the critical effect of classes and Pit skills, pet crits and survival's crit rate. Vanilla's falling hits are not counted as crits. Each crit says it once: the floating damage number over what was hit reads CRITICAL -12.5 (whichever of the combat indicators and survival's text indicators shows it first; the other shows a plain number), and only when no floating number said it does the attacker see CRITICAL 12.5 on their action bar instead. The label is the game text msg.combat.critical_damage, translated under Cosmetics and text → Translations. /stats shows each player's crit rate and damage from the same numbers (see /stats in players.md). In-game: network/Combat/Crits.sk.
    • Passive skills can have a cooldown too.
  • Fair play. Damage and pulls from skills count as a hit by the player, so spawn protection and the combat tag apply and kills are theirs. Skills don't work in creative or spectator.
  • Starting set. Nine skills come with the install (Dash, Leap, Shockwave, Grapple, Vampire, Spikes, Bloodlust, Bounty Hunter, Last Stand). Change their prices and numbers, turn them off or delete them.
  • Skill descriptions can be translated under Cosmetics and text → Translations.

Classes and class skills #

Network-wide classes, made on the panel under Network gameplay → Classes and skills (permission classes.manage), played through network/Players/Classes.sk. Staff turn classes on per category in the Rules box (Survival categories are on unless unticked; 1.8 servers never use them, and Pit keeps its own Pit skills).

  • Classes: name, description, colour, menu item, a particle effect played when someone picks it, level needed, and bonuses while they play it: extra hearts, % damage dealt, % damage taken, % walk speed, Haste level (mining), Luck level (fishing), and extra max MP and MP per second where the Mana rule is on (see Mana). Exactly one is the starting class; everyone starts as it (seeded: Human, plain). Also seeded: Warrior, Ranger, Mage, Miner, Angler.

  • Skills: active (used with a key combo, one per combo) or passive, a rarity (the shared tiers), a particle effect, price, level needed, cooldown, upgrade levels. Linked to classes; a skill with no class is for any class. Bought and upgraded with in-game money (the panel says yes, then the server takes it). Changing class takes off skills the new class can't use; they're kept for later.

  • Combos: F, Sneak + F, Sneak + right-click the air, double jump, drop key holding a weapon or tool. No extra items or hotbar slots.

  • Numbers per level: on a skill's page, under Numbers per level (optional), staff can set any of the effect's numbers and the MP cost for upgrade levels 2 and up. A number set there is used at that level instead of the "Stronger per upgrade" sum; blank boxes keep the sum, and levels above the highest upgrade level are dropped. Column class_skills.level_values ({"2": {"drain": 0.2, "mana_cost": 90}}), sent to servers as levels; Classes_Mod and Classes_ManaCost in Classes.sk read it first.

  • Void Zone (effect void_zone, seeded for any class, legendary, on the drop key): level 50 and 50,000 to learn, 45 second cooldown. When cast, a dark circle (particle effect void_zone) appears where the player stands and stays there. For the duration, every living thing inside it except the caster gets Slowness (effect level) and Blindness, topped up once a second so they wear off soon after leaving, and loses the drain amount of HP several times a second (pulses per second, 10 by default). When it ends, the caster heals the share (%) of all HP drained, and the action bar shows how many it drained and the HP gained. The drain counts as the caster's hit (protected areas and teams still stop it) but gives no knockback and no hit cooldown. Seeded numbers: radius 4 blocks, 5% back, Slowness I, and per level:

    Level Drain Lasts MP cost
    1 10 × 0.1 HP a second 1 second 100
    2 10 × 0.2 HP a second 2 seconds 90
    3 10 × 0.2 HP a second 3 seconds 75

    The circle is drawn by the particle effect, which has its own radius (4); if staff change the skill's radius, change the effect's layers to match (Cosmetics and text > Particle effects). It only uses particles with a 1.8 equivalent (smoke, dark dust, witch magic, portal), so it plays on Pit too, though classes themselves never run on 1.8. Migration 2026_11_13_211649_add_void_zone_and_level_values_to_class_skills.php, tests tests/Feature/VoidZoneTest.php.

  • Rules: first pick free, cost to change, hours between changes, level needed to change, and the levels that open active and passive skill slots.

  • In-game: /class (or /classes) to pick or change class, /class skills for skills. The web pages don't show a player's class or job next to their name.

  • Quests can need a class: pick it under the quest's requirements. The panel answers with the class it keeps (QuestRequirements::resolveClassUsing in AppServiceProvider).

  • Survival: Server/Game/ClassBuffs/BuffHandler.sk passes class damage/defence into survival's damage numbers, listens to the F key, and keeps data.classes.selected in the cache as the class key.

  • Panel code: GameClass, ClassSkill, PlayerClass, PlayerClassSkill, App\Services\ClassService, App\Support\ClassConfig, ClassAdminController, Api\V1\ClassApiController, migration 2026_05_25_000100_create_classes_and_class_skills.php, tests tests/Feature/ClassesTest.php.

Pit kit layout #

Players choose where each part of their Pit kit goes: the weapon (sword or Combo Spade), bow, fishing rod, arrows, and healing (golden apples, soup and golden heads from kills).

  • In-game: /loadout layout (also /kitlayout or /layout). Plain /loadout opens it too on Pit when the category has no loadout shop. Click an item, then the slot it should go to; clicking another item swaps them. Save keeps it, Default layout puts everything back.
  • On the portal: Play → Pit kit layout. Click an item in the inventory grid, then a slot, or use the lists below it.
  • The layout is kept on the panel, so it's the same on every Pit server. A change on the portal moves the kit at once if the player is on Pit.
  • Every spawn hands out the kit as before (pit/Kits/DefaultKit.sk), then moves each part into its slot. Healing from a kill goes to the healing slot.
  • With no layout saved, the kit is laid out as before: weapon, bow, rod, arrows, then healing in hotbar slot 5.

Pit 1v1 #

Players challenge each other to a fair 1v1 in an arena staff set in-game (pit/Combat/Duels.sk).

  • Players: /1v1 <player> (or /duel) sends a request with clickable [Accept] and [Decline] buttons; it lasts a minute. /1v1 accept [player], /1v1 deny [player], /1v1 leave (gives up the fight).
  • Staff (permission network.1v1): stand where each fighter should start and type /1v1 setarena 1 and /1v1 setarena 2. /1v1 arena shows both spots and who is fighting; /1v1 stop ends the fight with no winner. The spots are saved per server.
  • Only one 1v1 runs at a time; accepting while the arena is busy says so and keeps the request.
  • Neither player can be in combat when the fight starts. Both get the same default kit (iron chestplate, chainmail leggings and boots, iron sword, bow, 32 arrows; no upgrades), are healed, and get a 3 second countdown. Skills, pets, pet abilities and the kill streak damage bonus are off for both.
  • Fighters only hit each other and nobody else can hit them. They can't drop or pick up items or use other commands. Nobody dies: the hit that would kill ends the fight, and the winner is announced to the server. After 5 minutes the fight ends with no winner.
  • Each fighter's own inventory, armour and position are saved to disk before the fight and put back afterwards. Leaving mid-fight loses the fight and gives the gear back as they go; if the server stops or crashes mid-fight, it comes back the next time they join.
  • Other features can check {-net::duel::<uuid>} (the opponent's UUID while a player is in a 1v1) to switch themselves off too.

Elite mobs #

Rare, tougher versions of hostile mobs with better rewards (Network gameplay → Elite mobs, permission elites.manage). Modern servers only; 1.8 (Pit) never gets them.

  • Where. On per category. A Survival category is on until staff untick it; the rest are off.
  • Spawning. Each hostile mob that spawns naturally has the chance (default 1%) to be elite. Mobs from spawners (and trial spawners) can't be elite unless "Mobs from spawners can be elite" is ticked. Staff pick which hostile mobs can be elite (all of them by default, bosses never). Mobs that already have a name (wild NPCs, pets, scripts' mobs) are left alone.
  • What an elite is. Settings for all hostile mobs, and any mob can have its own that change only what's different (empty box = the default): name over its head ({mob} = the mob's name, default &6&lElite &e{mob}), health and damage multipliers (damage covers arrows, fireballs and explosions), glow, a particle effect from Cosmetics and text → Particle effects (pick one that repeats so it stays on), XP and money multipliers, and drops. Starters: all hostile mobs ×3 health, ×1.5 damage, glow, ×3 XP; creepers hit ×1.2 and drop gunpowder/TNT; endermen drop pearls and eyes; witches give ×2 money. "Restore starter elites" puts these back.
  • Rewards (only when a player kills it), on top of its normal drops: vanilla XP orbs (and network XP where it's on) times the XP multiplier; money for an elite kill (default 25) times the money multiplier; and every drop rolled on its own chance: an item (material, amount range, custom name), a custom item, money, XP levels or a console command ({player} = the killer). Items fall where it died and can have a rarity (Items → Rarity). Starter drops: iron, gold, XP bottles, emeralds, golden apples, diamonds, and a 0.5% enchanted golden apple (Legendary, announced).
  • Players are told what they got. Staff can have every elite kill told to the whole server; a drop marked "announce" always is. Inside a dungeon these go only to the players in that dungeon.
  • Stats and quests. Each kill adds to the stat elite_kills (Elite mobs killed) and the quest counter kill_elite:<MOB TYPE> (objective "Kill elite mobs", param = a mob type like ZOMBIE, blank = any elite). Players see it in /stats (Items and world), on the portal's stats page, and it can be a leaderboard.
  • Voice lines (each elite page, App\Support\VoiceLines): chat lines elites say during a fight. A mob uses the lines and radius for all hostile mobs unless Use the voice lines for all hostile mobs is unticked. Rows of moments: spawned or summoned, health at or below N% (a row per threshold, like 75/50/25/10, each said once per fight), hits a player, is hit, kills a player, dies, and no target (idle, every so often while players are near but nobody fights it). Each row has up to 10 lines (one per line in the box; one is picked at random each time), a chance % and a cooldown in seconds (empty: the moment's default; "is hit" defaults to 20% and 10 seconds so it isn't spam, "hits a player" to 30% and 10 seconds, idle to a 30-second cooldown). Lines are up to 160 characters with & colour codes and the placeholders {boss} (its name), {player} (the player it hit, was hit by or killed, else the nearest) and {hp} (its health in %) and {hearts} (its health in hearts, to the half heart); when several health thresholds are crossed by one hit, the lowest speaks. Hearing radius: 1 to 20 blocks (default 20; never more). Only players in the same world within it hear the line; a dungeon raid has its own world, so inside a dungeon only that dungeon's players hear it, never the rest of the server. Health lines also show on the action bar. Lines are sent through translation (Trc) with the key voice.<owner>.<hash of the English>, listed under Translations → Boss and elite voice lines once saved (changing a line's English gives it a new key). The page shows a few saved lines as they look in chat. In game: network/Combat/Voices.sk (Voice_Say(entity, moment, player, attack number), Voice_Track, Voice_Forget), fed by "voice" in the download (voice in each profile, with the group sync).
  • In-game (network/Combat/Elites.sk, settings with the group sync as elites): elites carry the scoreboard tag neutine_elite, so they stay elite after a restart (their particle effect doesn't come back). /elite shows whether elites are on; /elite spawn [type] spawns one next to you (permission network.elites).

Bosses #

Mobs turned into bosses with a summon item: much more health, a health bar, special attacks and their own reward set (Network gameplay → Bosses, /manage/bosses, permission bosses.manage). Modern servers only; 1.8 (Pit) never gets them.

  • Summoning. A player right clicks a mob while holding the boss's summon item. If the mob is one the boss can be summoned from (none ticked = any mob), one item is used up (not in creative) and that mob becomes the boss on the spot. Players, NPCs, armour stands and mobs that are already bosses can't be. When "tell the whole server" is on, everyone is told who summoned it and where, and again when it's beaten. A boss inside a dungeon is only announced to the players in that dungeon, not the whole server.
  • The summon item is a normal custom item (Items → Custom items). Leave it empty when making a boss and a glowing paper named after it is made for you; pick any other custom item instead if you like. Because it's a custom item, shops, rewards, loot, store packages (citem give <id> {player}) and crafting recipes can hand it out. Staff: /boss give <key> [player] [amount].
  • Entity editor. Name (with colours; on its head, its health bar and in messages), mobs it can be summoned from, health in hearts (0.5 to 512, to the half heart; a player has 10. Stored and sent to servers as health points, 2 per heart: Boss::HP_PER_HEART, Boss::hearts(), Boss::heartsLabel(). Paste/Import JSON copied before this, with stats.health in points and no hearts, still works), damage multiplier for its own hits (melee and arrows; special attacks set their own damage), speed multiplier, size (1 = normal, up to 5), armour points, knockback resistance (%), equipment for every slot (a material like DIAMOND_HELMET or a custom item like CITEM-1a2b3c4d; it never drops it), glow, health bar colour (or none; shown within 48 blocks), and a particle effect on it (pick a repeating one).
  • Special attacks. Up to 12 per boss, each a combat script (the same language as weapon skills: see "Combat scripts" below) with its own page, live check and top-down preview. caster is the boss, target is the player it's after; aim self centres an attack on the boss. Every "attack every" seconds (default 6) while it has a target, the boss picks one at random by weight from those that fit: "only at or under N% health" (a second phase) and "only when the target is within N blocks". Use marker and a wait before damage so players can dodge. Damage zones with an element get elements and reactions when they're on. Attacks are played by network/Combat/Anim.sk as timelines boss.<key>.<n>. A boss's attacks (damage, potions, pulls, root) never touch bosses or minions (neutine_minion), players in creative or spectator, or staff with network.bosses.bypass.
    • Presets: on the boss page, Add GRAVITY, Add Freeze and Add Blind, or Start from a preset on a new attack's page with a radius, how long it lasts and an optional particle effect played on the boss when it lands. A preset only fills in the name, the lookup text and an ordinary script, so staff can change anything before saving (BossAttack::PRESETS, BossAttack::preset()). GRAVITY: a purple warning ring and a shrinking portal spiral, then everyone in the radius is pulled in and gets slowness 255, blindness and nausea (2 seconds longer), plus root, so they can't walk or jump. Freeze: slowness IV and mining fatigue III. Blind: blindness and darkness (darkness is 1.19+ only).
    • Announcing moves: each attack has Announce it in chat (on by default, also for attacks made before) and an optional announcement (up to 160 characters, {boss}, {attack}, & colours; blank: "{boss} uses {attack}!", translatable as msg.bosses.attack_used). When the boss uses it, players in its world within its arena radius (32 blocks when it has no arena) are told, so inside a dungeon only that dungeon's players. With voice lines: the "Uses a special attack" voice line (in character, within the hearing radius, at most 20 blocks, with its chance and cooldown) is said first; players within that line's hearing radius when it was actually said don't also get the announcement, and players further away still do. When no voice line fires (chance, cooldown or none set), everyone in range gets the announcement. Turn announcements off for an attack whose voice line already says what it does.
  • Target. The mob's own target when it's a player within 32 blocks, otherwise the nearest player in survival or adventure within 24 blocks.
  • Reward set. XP levels, in-game money, and reward lines rolled on their own chance: an item (material, amount range, custom name, rarity), a custom item, money, XP levels or a console command ({player}), the same lines as elite drops. Items go into the player's inventory (the rest drops at their feet). With "reward everyone who helped" every player who did at least a tenth of its health in damage gets their own roll; otherwise only the killer. Lines marked "announce" are told to everyone. Custom items given here can be crafting ingredients (Network gameplay → Recipes), so a boss can drop the parts for something players craft.
  • Boss lookup (players): /bosses on the portal (public, Play → Boss lookup; BossLookupService, Portal\BossLookupController) and /bosses in game (aliases /bestiary, /bosslookup), and /boss <name> on the Discord bot (see Community → Discord). Every boss that's on, A to Z, with its icon, health in hearts (to the half heart, like everywhere players and staff see a boss's health: the boss list, the portal, Discord, /bosses), damage, armour, speed, size and knockback resistance, its special attacks in words (with "at N% health or less" and "when you're within N blocks"), its summon item and the mobs it works on, the categories it's on, the open dungeons whose boss spawners use it, and its rewards with their chances (XP and money at 100%, then each reward line), and whether helpers get them too, plus short hints at the fight ("Changes 3 times as it weakens.", "Calls minions to help it.", "Enrages if the fight drags on.", "Won't let you leave its arena."; BossFight::traits) without the details. The portal can search by name and filter by dungeon or by mob. In game the menu lists the bosses on that server; clicking one opens its page (stats, attacks, summoning, where it appears, rewards), and /bosses <key> opens a page straight away. Each boss's page on the panel has a Boss lookup section: Show in the boss lookup (on by default, so existing bosses show; off hides it from both lookups while it still works in game, and the Bosses list tags it "Not in lookup"), What players read about it (optional), and a Lookup icon (a material or CITEM-<id>; blank: the spawn egg of its first mob). Each attack has its own optional What players read about it; blank, it's worked out from the script: damage (with element, radius and knockback), potion effects, pulls and pushes, heals and dashes, like "Hits for 6 damage within 4 blocks of the boss, knocking you back." Never shown to players: attack scripts, the staff description, keys and console command rewards (listed as "A special reward"). The list is cached for 5 minutes and cleared when a boss changes.
  • Voice lines (each boss page, App\Support\VoiceLines, columns voice_lines and voice_radius): chat lines the boss says during a fight. Rows of moments: spawned or summoned, health at or below N% (a row per threshold, like 75/50/25/10, each said once per fight), hits a player, is hit, kills a player, uses a special attack (any, or one you pick), dies, and no target (idle, every so often while players are near but nobody fights it). Each row has up to 10 lines (one per line in the box; one is picked at random each time), a chance % and a cooldown in seconds (empty: the moment's default; "is hit" defaults to 20% and 10 seconds so it isn't spam, "hits a player" to 30% and 10 seconds, idle to a 30-second cooldown). Lines are up to 160 characters with & colour codes and the placeholders {boss} (its name), {player} (the player it hit, was hit by or killed, else the nearest) and {hp} (its health in %) and {hearts} (its health in hearts, to the half heart); when several health thresholds are crossed by one hit, the lowest speaks. Hearing radius: 1 to 20 blocks (default 20; never more). Only players in the same world within it hear the line; a dungeon raid has its own world, so inside a dungeon only that dungeon's players hear it, never the rest of the server. Health lines also show on the action bar. Lines are sent through translation (Trc) with the key voice.<owner>.<hash of the English>, listed under Translations → Boss and elite voice lines once saved (changing a line's English gives it a new key). The page shows a few saved lines as they look in chat. In game: network/Combat/Voices.sk (Voice_Say(entity, moment, player, attack number), Voice_Track, Voice_Forget), fed by "voice" in the download (voice on each boss in /server/bosses; attacks by their number there).
  • Phases (each boss page, App\Support\BossFight, column phases): up to 8 rows, each starting once per fight when its health drops to the phase's health % (1 to 99; two phases can't share a %). Blank fields keep what the boss has at that moment, so phases build on each other: special attacks it uses from now on (tick some of its attacks; none ticked keeps the current ones; an attack that's off or deleted is skipped, and if every ticked one is, it keeps what it had), attack every seconds, speed, damage multiplier and size (the same ranges as its stats; they replace the stat, enrage multiplies on top; size uses the SCALE attribute, so only 1.20.5+ servers change it), equipment per slot (a material or CITEM-<id>; blank keeps it), invulnerable for 0 to 30 seconds while it transforms (it can't be hurt, stands still and doesn't attack; hits don't count for rewards), a particle effect (Cosmetics → Particle effects) and a sound (a short name like thunder, explode, whoosh, anvil, or a Minecraft sound key like entity.wither.spawn) played where it stands, a minion wave to call (by its number under Minions and arena), a health bar colour and a name suffix (like &c(Enraged), on its name and health bar). Each phase is told to players within 48 blocks in its world (inside a dungeon that's only that dungeon's players): its own message ({boss} and & colours) or "{boss} enters a new phase!" (msg.bosses.phase). Phases are checked the tick after every hit and every second, so one big hit can start several in a row. The voice lines' Health at or below moments keep playing alongside (use them for what it says, phases for what it does). A boss loaded again (restart, chunk) quietly catches up on the phases its health has passed. The boss lookup only says how many times it changes, never how.
  • Minions and arena (each boss page, columns minion_waves and arena):
    • Minion waves (up to 6, numbered from the top): how many (1 to 20), normal or elite (made like Combat → Elites), which mob, within 1 to 24 blocks of the boss (on a spot with room, else next to it), and when: when it appears, every N seconds (5 to 600, only while it's after a player) or only when a phase calls it. Most minions alive at once (1 to 50, default 12) caps every wave. Minions carry the scoreboard tag neutine_minion: they only go after players (never another mob, anywhere), never hurt the boss or each other and the boss never hurts or targets them, don't stay when their chunk unloads, and don't count as boss kills (no boss_kills, no rewards). With Minions drop their normal loot off (the default) they drop no items or vanilla XP, give no network XP (Players/Xp.sk) and elite minions give no elite rewards (neutine_minion_loot marks the ones that do). With Minions die with the boss on (the default) they're removed when it dies, is removed with /boss kill or disappears from a reset.
    • Enrage: after N seconds (0: never), counted from the first hit a player lands, its own hits (not special attacks) are multiplied by damage times (1 to 10) and its speed by speed times (1 to 5), with a roar, and players within 48 blocks get the enrage message or "{boss} is enraged!" (msg.bosses.enraged). It stays enraged through restarts until it dies or resets.
    • Arena radius (0: off, else 8 to 128 blocks) around where the boss appeared ({bosses::home::<uuid>}). Every player who has hit it and steps outside is warned on the action bar for warning seconds (0 to 30; 0 pulls straight away), then teleported back to where they last stood on the ground inside the arena (else where the boss appeared) with "You can't run from this fight!". Players more than 64 blocks past the edge, in another world, dead or in creative/spectator are let go, so /spawn and the like still work outside dungeons. The boss is put back where it appeared when it's dragged, knocked or lured out.
    • When everyone walks away: with nobody (survival or adventure) within nobody within blocks (0: off) for for seconds (5 to 3600), it either heals fully and starts over (full health, back where it appeared, its own stats, gear, bar and name, phases, enrage, timers and voice line thresholds from the start, minions removed, damage counted for rewards forgotten) or disappears (with its minions).
    • Range and patience (each boss, with defaults for bosses that never set them; leash, idle_despawn, follow_range in arena and in "fight" on the download):
      • Leash (default 256 blocks; 0: off; 32 to 1024 and at least the arena radius): further than that from where it appeared, or in another world, it starts over back home exactly like "heals fully and starts over" above, and players within 48 blocks are told. The arena radius (at most 128) is tighter and acts first, so the leash is for bosses without an arena, or ones dragged off some other way. In a dungeon the spawner's "Keep within" still applies as well.
      • Leaves when unprovoked (default 30 seconds; 0: never; 5 to 3600): when no player has hurt it for that long, counted from when it appeared (or was loaded again after a restart or chunk load), the last hit, or a reset, it disappears with its minions and players within 48 blocks are told it lost interest. Never in a dungeon world ({-dg::world::<world>}), because the raid counts its mobs. This runs next to When everyone walks away rather than replacing it: that one is about nobody being near (and can heal instead), this one about nobody fighting; whichever comes first happens. A summoned boss that leaves doesn't give the summon item back.
      • Attention span (default 100 blocks; 16 to 256): its follow range attribute (FOLLOW_RANGE, GENERIC_FOLLOW_RANGE on older servers) is set to it, and every second it keeps the player it's after, or goes back to the last player who hit it, while they're online, alive, in survival or adventure, in its world and within that distance. Special attacks use the same range for their target.
    • Inside dungeons (a spawner of kind "boss" uses Bosses_Make): phases, waves, enrage and the arena work the same. Minion spawns aren't natural, so the dungeon lets them in, but they aren't the spawner's mobs: they don't count towards "Killed", clearing or the spawner's drops, and the spawner's health and damage multipliers don't apply to them. The dungeon already stops mobs fighting mobs. Pulling a player back sets the raid's teleport allowance ({-dg::allow::<uuid>}) for that one teleport, because dungeons refuse every other teleport. Arena vs. the dungeon leash: the spawner's Keep within (default 16) puts the boss back by the spawner's sign every second, measured from the sign; the arena puts it back where it appeared (within the spawner's spread of the sign), measured from there. Both run, so the tighter one decides where the boss can go; the arena radius is what keeps players in, so set it at least as big as Keep within (or the boss can stand where players are pulled away from). A reset in a dungeon always heals, never disappears, so a spawner is never left with a boss it can't count as killed.
  • Stats and quests. Each rewarded player adds to the stat boss_kills (Bosses beaten) and the quest counter kill_boss:<key>.
  • Where. Each boss is on for the categories ticked on its page (new bosses: Survival categories). Off: servers don't get it and its summon item does nothing.
  • Starter: the Graveyard King (graveyard_king): summoned from zombies, husks, zombie villagers and drowned with its own paper, 300 health, size 1.6, gold armour and a netherite sword, a red health bar, and three attacks (Ground slam around itself, Fire rain on its target, and Grave pull under half health). Rewards diamonds (Rare), a golden apple (Epic) and a 5% announced netherite ingot (Legendary), 10 XP levels and 500 money for every helper.
  • In-game (network/Combat/Bosses.sk, GET /api/v1/server/bosses?version= every minute, only sent when it changed, last copy kept for restarts). Bosses carry the scoreboard tag neutine_boss and are remembered by UUID, so they stay bosses (health bar and attacks come back) after a restart or when their chunk loads again; they never despawn. A mob that was an elite stops being one. Staff: /boss list, /boss give <key> [player] [amount], /boss spawn <key> (its first mob type next to you), /boss kill (bosses within 16 blocks), /boss reload (permission network.bosses). Other scripts: Bosses_Has(key), Bosses_SummonItem(key, amount), Bosses_Make(entity, key, summoner), Bosses_Is(entity), Bosses_Key(entity), Bosses_Reward(player, key), Bosses_LookupOpen(player), Bosses_LookupShow(player, key). Each boss in the download has a lookup object (what the boss lookup shows; null when staff hid it) and a fight object (BossFight::wire: phases with attacks by their number or null for no change, waves, and the arena settings).

Game mechanics #

How combat, damage, hunger and movement feel (Network gameplay → Game mechanics, permission mechanics.manage). Set for the whole network; a category or a single server can change any one setting, and anything it leaves empty comes from the network (a server: from its category, then the network). Like level rewards, pick "Mechanics for" at the top; the page lists every category and server that changes something. Every default is what the game does normally, and a setting left at its default is never touched, so game-mode scripts (Pit's own knockback in pit/Combat/Skills.sk, Tag's freeze) keep working. Every change is in the audit log.

  • Knockback (all servers): away and up multipliers, the extra push from sprint hits, arrow knockback, and fishing rod knockback (0 = as the game does it: 1.8 rods push players, modern rods don't; 1 = the 1.8 push, on either version). Knockback is redone a tick after the hit, keeping the Knockback enchantment.
  • Combat: hit delay in ticks (20 = normal; all servers), attack cooldown on or off (off = 1.8-style full-strength hits; modern servers only, skipped on Pit), crew members hurting each other (all servers).
  • Damage multipliers (all servers): fall, fire and lava, drowning, void.
  • Hunger and health (all servers): how fast the hunger bar goes down, how fast health regenerates from a full hunger bar.
  • Movement (all servers): walking speed (players whose class changes their speed keep their class speed), an always-on Jump Boost level.
  • Projectiles (all servers): speed of arrows, snowballs, eggs, pearls and tridents; seconds between ender pearl throws.
  • Death (all servers): items dropped, kept or destroyed; XP dropped or not. The category's Keep inventory setting wins.
  • PvP, fall damage on/off, hunger on/off and health regenerating on/off stay game rules (Servers → category or server).
  • In-game (network/Combat/Mechanics.sk, every server): settings come with the group sync as mechanics (every value for that server) into {-net::group::mechanics} and are re-read every 5 seconds, so a change is live within a minute (heartbeat every 15 seconds). /mechanics lists what this server got (permission network.mechanics).

Combat: weapon skills, enchantments and elements #

Network gameplay → Combat (/manage/combat, permission combat.manage). Three things that work together, on every server (1.8 Pit and modern). Every change is in the audit log, and servers pick changes up within a minute (GET /api/v1/server/combat, only sent when it changed).

  • Weapon skills. A skill is a short combat script (below). A player uses it by right clicking, sneak + right clicking, left clicking, hitting, sneak + hitting, with an arrow landing, by charging it, or just by holding it, depending on the skill. Charge: draw a bow, or sneak while holding any other weapon; the script's charge block plays round the player on a loop with a charge bar in the action bar (a sound when full), and letting go at or past the script's minimum fires the rest of the script, stronger the longer it charged (damage times the charge, at least 20%). A bow loses its arrow when the skill fires, unless the script says keep; letting go too early just shoots the arrow. Switching item or putting the bow down cancels the charge; a skill still cooling down doesn't start one. Hold: while the weapon is in the hand the script plays every hold every (default: the cooldown, at least half a second), with no cooldown message. A weapon has a skill when staff imbued it (/combat imbue <skill>), or when it is one of the skill's weapon kinds (every sword, every bow...) or custom items. Each skill has a cooldown, a rarity (lore colour), an optional element shown in the lore, and an optional particle effect played on the player. While a player holds a weapon whose skill aims at a block or a mob, they see a ring where it will land (only they see it; grey while it cools down). The skill form checks the script as you type and plays it from above.
  • Custom enchantments. Items carry them with a level (/combat enchant <key> [level]), shown at the top of the lore. Each says what it goes on, when it goes off (hitting, an arrow hitting, being hurt, killing, using the weapon's skill, every second while held or worn, every second while in the hand only (hold), or on letting go of a charged weapon (charge: at full charge, or at its skill's min when its effect runs a skill that has a charge line, which also gives the charging animation and time)), its chance (plus more each level), and what it does: extra damage, give hits an element, give hits air (with its own spread radius and percent, which beat the reaction's and the settings'), lifesteal, a potion, fire, run a weapon skill on the target, knockback, hurt attackers back, take less damage, a stronger skill, or a shorter skill cooldown. It can also play a particle effect, and list enchantments it can't share an item with.
  • Getting custom enchantments like vanilla ones. Each enchantment's form has How players get it (all off for the starters and for enchantments made before this; on for new ones). Enchanting tables (all servers): an enchant can also add one custom enchantment that goes on the item (any on a book), picked by how common it is (1 to 100; vanilla uses 10, 5, 2 and 1) from those whose lowest table level the enchant's cost reaches; the chance is the combat setting Enchanting table chance (25% at 30 levels, less for cheaper enchants) and more levels give a higher level. Anvils (modern survival servers): a book or item with custom enchantments on the right puts the ones set to Anvils on the left item if they go on it (any on a book); two of the same level make the next level up to the highest; each adds its anvil cost times its level to the XP cost (at most 39); enchantments it conflicts with are left off. Loot chests (modern survival servers): each enchantment set to it has its own chance in each loot chest of an enchanted book with it at a random level. Combat settings From enchanting tables, On anvils and Books in loot chests turn each on or off per category or server. In-game: tables in network/Combat/Combat.sk, anvils and loot in survival/game/Server/Game/Modifications/EnchantBooks.sk (modern-only Bukkit events, so not in the network scripts that Pit loads).
  • Elements (Combat → Elements and reactions), in the style of Genshin Impact. Off until you turn "Elements and reactions" on in the combat settings for the network, a category or a server. A hit with an element leaves it on what it hits for a few seconds (a coloured symbol floats over it). A different element on top makes a reaction: the damage is multiplied, the reaction can burn, freeze, stun, weaken (more damage taken), burst, chain to 3 others or shield the attacker, and its name shows in the damage number (e.g. "Vaporise ✹ -12.5"). Order matters (Water on Fire and Fire on Water are separate rows). Elements that don't "stay on targets" (Air) are never put on anything by themselves; when one meets another element (on the target, or in the same hit, e.g. a Fire sword with Tempest) the damage spreads: everything within the radius takes that percent of it and gets the element ("Heated": 3 blocks, 10%). Starter elements: Fire, Water, Ice, Lightning, Nature, Earth, Air, with the usual reactions; "Put the starter elements and reactions back" restores them.
  • Combat settings (on the Combat page; network, then category, then server, like game mechanics): weapon skills on/off, the aiming marker, whether skills can hurt players, a skill damage multiplier, enchantments on/off, elements on/off (off by default), elements on players, how long elements stay, seconds between reactions on one target, the air spread radius and percent, the symbols over targets, and damage numbers (element and reaction hits only, every hit, or none; Survival has its own numbers for every hit).
  • Starters: seven skills (Meteor Strike, Thousand Blades, Frost Nova, Thunder Lance, Tidal Wave, Gale Dash, and Charged Shot: draw a bow fully to fire a damaging beam of light instead of the arrow; on no weapon kind, so only imbued weapons have them) and eleven enchantments (Blazing, Tidecaller, Tempest, Vampirism, Thundercall, Frostbite, Arcane Focus, Quickcast, Spiked, Aegis, and Overcharge: bows, charge, fires Charged Shot). Migration 2026_11_11_000100_add_charge_combat_starters adds the two new ones to panels that already have the others. "Restore the starters" puts them back as they were.
  • In-game: network/Combat/Combat.sk (skills, enchantments, elements, /combat) and network/Combat/Anim.sk (the animation runtime that plays skill scripts; boss attacks and events can use it too). /combat cast <skill> tries a skill with no item or cooldown; /combat element <element> puts an element on what you look at. Permission network.combat.

Combat scripts #

One step per line; lines under repeat and array are indented. Times are ticks (20 a second) or seconds like 0.5s. # starts a note (a colour like #ff5500 doesn't). The panel works out every point and unrolls repeats and arrays, so servers only play it back. At most 400 steps (after unrolling), 60 seconds, 240 points a shape.

Step What it does
aim self / aim block 20 / aim entity 16 / aim hit, then marker 3 #ff5500 Where the skill lands: the player, the block they look at, the mob or player they look at (needs one), or what was hit. The marker is the ring the player sees while aiming. Without an aim line: aim hit for hit and arrow skills, otherwise aim block 20 marker 2.
wait 10 Later steps happen this much later.
shape ring radius 3 points 32 particle flame at target for 1s Draws a shape: ring, disc, helix, spiral, sphere, dome, line, burst, star, heart, point. Also height, turns, strands, colour #rrggbb (dust), size, mode static|draw|trail|expand|shrink, every, spin (degrees a second), rise, tilt x y z, spread, speed, follow (moves with the player).
marker 3 #ff5500 for 1s at target A warning ring on the ground that everyone sees.
damage 6 radius 3 at target element fire knockback 1 lift 0.5 max 3 Hurts living things in the zone (not the player using it) as their hit. Element and air work as above. max limits how many it hits.
effect slowness level 2 for 3s radius 3 at target (or self) A potion effect on what is in the zone, or on the player. Levels go up to 255 (slowness 255 stops walking). darkness needs 1.19+ and does nothing on 1.8.
root for 3s radius 4 at caster Players in the zone can't walk or jump until it wears off; they can still look around and fall (network/Combat/Anim.sk holds their position, {-anim::root::<uuid>}). Works the same on every version, unlike the jump boost tricks.
heal 4, dash 1.5 up 0.3, pull 1.2 radius 4 Heal the player, throw them forward, pull things in (a minus pushes away).
sound explode at target volume 1 pitch 1 explode, fire, glass, splash, thunder, hit, whoosh, levelup, orb, anvil, zap (or a modern sound key).
particle kill_burst at target, lightning at target A particle effect from Particle effects; a lightning flash that does no damage.
beam to target particle crit points 16 A line of particles from here (default: the player's eyes) to target, caster or eyes.
repeat 5 every 4: The indented lines, 5 times, 4 ticks apart.
array 8 ring 3 at target stagger 2: / array 6 line 1.5 at caster: The indented lines at 8 points around the target (or 6 points going forward), 2 ticks apart; inside, at point (the default) is each point.
charge 1.5s min 60 keep: For charge skills: a full charge takes 1.5s (0.25s to 10s). The indented lines (optional) are the charging animation, played round the player on a loop; in them target is the player. Everything else in the script fires on release, at any charge from min percent (default 100, so a full charge). keep: a bow still shoots its arrow. One per script, not inside a repeat or array, and it doesn't move time on. It compiles to timeline.charge (ticks, min 0-1, keep, and a timeline of its own, played as Anim key skill.<key>.charge).
hold every 1s For hold skills: how often the script plays while the weapon is in the hand (0.5s to 60s; default: the cooldown). Compiles to timeline.hold.every (ticks).

A charged bow beam, for example (the Charged Shot starter):

aim entity 30 marker 1 #9be7ff
charge 1s min 60:
    shape ring radius 0.8 points 12 particle end_rod at caster offset 0 1.2 0 mode draw for 10
    sound orb at caster pitch 1.6
beam to target particle end_rod colour #9be7ff points 40 for 6 every 2
sound zap at target
damage 7 radius 1.5 at target knockback 0.6 max 1
shape burst radius 1 points 16 particle end_rod at target for 6

Places (at): caster (the player's feet), eyes, target (followed if it's a mob that moves) and point inside arrays. offset right up forward moves from there, turned the way the player faced when the skill started; random 2 moves it up to 2 blocks at random.

Smart mobs #

Monsters fight more cleverly (network/Combat/SmartMobs.sk, modern servers only; on Pit the file loads and does nothing). Every behaviour is on unless a category or server turns it off: Servers → a category (or a server) → Rules.

  • Smarter mobs: the master switch for all of the below.
  • Skeletons keep their distance: skeletons, strays and bogged back away from players who get within 5 blocks, and hop back when cornered.
  • Zombies call for help: hitting a zombie, husk, drowned or zombie villager sends the zombies within 12 blocks that aren't busy after you.
  • Creepers rush and wait out shields: creepers get a burst of speed when a player is 3–10 blocks away, and back off while their target holds up a shield.
  • Spiders pounce: spiders leap at their target from 3–8 blocks away (every few seconds).
  • Witches support other monsters: a witch in a fight gives hurt monsters near it regeneration and resistance.
  • Badly hurt monsters retreat: under a quarter of their health, monsters run off for 3 seconds and then come back (at most once every 20 seconds each). Bosses and creepers don't.
  • The Ender Dragon fights back: whoever hurts it gets a dragon fireball aimed at them (every 4 seconds at most), players crowding it are roared away with nausea, and at half health it calls the endermen nearby onto the nearest players.
  • The Wither calls for backup: three wither skeletons at half health and three more at a quarter.

Leaderboards and envoys #

Envoys #

Envoys: crates fall from the sky around spawn every so often. Off by default: turn on "Envoys" in a category's or server's rules, set how often, how many and how far, and set the loot under "Envoy crate loot". /envoy start|stop|setcentre needs network.envoy. Scripts can add their own crate types (Envoy_AddCrate, see the Script editor's hooks).

Wild NPCs #

Wild NPCs (network/World/Npcs.sk): named mobs that spawn near a random player. Off by default everywhere: turn on "Wild NPCs" in a category's or server's rules, then set how often, how many, the mob, name, health, damage, how long they last and whether they drop anything. "Players can hit wild NPCs" and "Wild NPCs fight back" (never, whoever hits them, or also players nearby) set how they fight. They're mobs so they work on 1.8.9 and modern Paper with no new plugin; an NPC that looks like a real player would need Citizens or similar. Monster types don't survive on Peaceful difficulty. /wildnpc, /wildnpc spawn and /wildnpc clear need network.npcs.

Health under names #

Health under names is a rule too ("Health under names"): each player's HP (20 is full) under their name tag. The scores are set by network/World/Rules.sk on every player's own scoreboard when health changes (damage, healing, respawn, join, and every 15 seconds), because Minecraft only updates a "health" objective on the main scoreboard and the sidebars give everyone their own board.

The rank, badge, level and crew around names (above heads and in the tab list) are rules too. See Name tags and the tab list.

Tag in-game #

Tag (tag/Tag.sk, tag/TagMap.sk, tag/TagSkills.sk, tag/TagSpectate.sk, modern Paper only: it uses glowing, boss bars and clickable chat; 1.8 players join through ViaVersion). Upload the tag folder as the Tag category's Category update (folder tag) and set the server up like survival (config-survival.sk). One round at a time per server:

  • Where maps are built: each Tag server has one map spawn point. Staff stand there and run /map-spawn-point (or /tag mapspawn); the round's map is built with its [center] sign (or its middle) on that block. /map-spawn-point <map ID> also builds that map there now, to check it between rounds, and says where it went: its size, where its [center] is inside the schematic, the two corners it fills, whether FastAsyncWorldEdit built it, and whether part of it is above the world's height limit or below its lowest block (those layers can't be built, so move the map spawn point). The server console logs the same for every build. Pick a spot in an empty area (a void world is ideal) with room for the biggest map around it.
  • Building a map: when the vote ends the map is picked and built before anyone moves: the server downloads its blocks from the panel (only when the map changed), clears anything still standing in a map's box (the box is remembered across restarts, so nothing of an old or moved map is left), then pastes the new one. With FastAsyncWorldEdit installed on the Tag server, clearing and pasting go through it on another thread, so even big maps don't lag the server; it's detected by itself (and again after /tag reload) and isn't required; the server console says which way maps are built. Without it, or if its API doesn't answer, the server places the blocks itself to a time budget of about 30 ms a tick, and clears only the blocks the map placed (skipping its air), or the whole box when it no longer has that map's blocks (after a restart). The boss bar and the sidebar show "Clearing old map..." and then "Building the map..." with the progress. Its chunks stay force-loaded while it stands. If it can't be built (no map spawn point, the panel didn't answer), everyone is told why and the server waits for the next vote.
  • Taking the map down: once everyone is back in the lobby after a round, the map is cleared the same way ("Clearing old map..." on the boss bar and sidebar) and its chunks are let go, so every round builds its map fresh. Voting for the next round starts once it's gone.
  • Lobby and vote: players wait at the lobby (/tag setlobby; without one, the server's spawn from /setspawn). Everyone who joins lands there, even while a round is on (they watch in spectator and play the next one), never inside the map; on a first join this also wins over the network's first-join spawn teleport. Once enough are online, they vote by clicking a mode in chat or with /tag vote <mode>; the most votes wins, and a tie or no votes is settled at random. A boss bar shows the countdown.
  • Start: runners are spread over the map's runner spawn points. The taggers arrive a few seconds later on the [tagger] spawn points (one each, picked at random; any without one on a random runner spawn point). Taggers are faster (the speed bonus), and so everyone can see who's it on every Minecraft version they glow (modern clients), have the map's particle effect around them (started again whenever it ends), and are named on the boss bar ("Tagger: Steve") and on the sidebar, which also shows the mode, the map and how many are still running. A hit is a tag; player damage never hurts anyone.
  • Last One Standing: whoever holds the tag when the timer runs out is out, and new taggers are picked. Panic mode speeds everyone up near the end. The last one left wins; places 1 to 3 get the top rewards.
  • Freeze Tag: tagged runners freeze until a free runner touches them. Taggers win if everyone is frozen; otherwise the moving runners win when time runs out.
  • Infection: tagged runners join the taggers. Survivors win when time runs out; if everyone is caught, the first taggers win.
  • Classic Tag: tagged runners are out. Survivors win when time runs out.
  • Map extras: jump pads launch players, and falling below the map's fall-out height sends you back to a spawn point.
  • Boosters (tag/TagBoosters.sk): once the map is built, each [booster] sign's booster stands there with its name over it. A runner or tagger it affects (not frozen or out) who comes within its radius gets its effects, a sound, particles and the action bar ("Speed: +Speed II 5s" in green, a nerf in red); it then disappears for its cooldown and comes back. Players it doesn't affect walk past it. Booster effects are taken off at the end of the round, and the boosters are taken down then and before the next map is built.
  • Skills: /tag skills opens the skills menu. Click to buy, left-click to equip or take off, right-click to upgrade. Money is this category's in-game money, taken only after the panel agrees (level and price are checked there). Active skills are in the hotbar during a round, and the action bar shows their cooldowns.
  • Spectating (tag/TagSpectate.sk): while a round is on, players who aren't in it (joined late, or the round was full) and players who are out fly, are hidden from everyone, and their sidebar says (Game on-going). They get a compass: right-click lists the players still in (taggers first, with role and distance, refreshed every second) and clicking one follows them and teleports there; left-click teleports to whoever they follow. The compass needle and the action bar track that player live (the nearest one still in when nobody is picked). Everything goes back to normal when the round ends.
  • After a round: everyone gets their coins, tag_games / tag_wins / tag_tags stats and a little XP (when XP is on). The result goes to the panel for the weekly leaderboard.
  • Staff (neutine.tag.admin): /map-spawn-point [map ID] (also /tag mapspawn [map ID]), /tag setlobby, /tag start (skip the wait), /tag stop, /tag reload, and for maps without a schematic /tag setspawnpoint <map ID> and /tag clearspawns <map ID>.
  • Setting up and testing a map: build it in a creative world, put a [runner] sign wherever runners should start, [tagger] signs for the taggers and a [center] sign where it should sit on the map spawn point, then //schem save it. Upload it on the map's page (Tag → Tag → the map) and check the summary. In-game on the Tag server: /tag reload, stand at the map spawn point and run /map-spawn-point <map ID> to build it and see the spawn point count, then /tag start with two or more players online.

Jobs #

Jobs (network/Players/Jobs.sk, panel: Survival → Jobs, permission jobs.manage): job classes players take with /job. None come ready. Turn on the Jobs rule for a category (or one server) to use them there; a job can also be limited to some categories.

  • Tasks give job XP and money each time. Each can be narrowed with Which (blank = any; the editor shows what it means for each type), unlocked from a job level, and limited by conditions (kill streak, level, health, held item, world, dungeon difficulty). The jobs list, the /job menu and the server config describe them in plain words ("Break Stone", "Harvest fully grown Wheat").

    Task Which Works on
    Kill players – both (only where PvP is on)
    Kill mobs mob, e.g. ZOMBIE both
    Kill elite mobs / bosses elite ID / boss key both
    Break / place blocks block, e.g. STONE both
    Harvest fully grown crops crop, e.g. WHEAT, CARROTS (only when ripe) both
    Till soil with a hoe – both
    Catch fish the vanilla catch, e.g. COD, ENCHANTED_BOOK, or citem-<ID> both
    Win fishing loot the loot table's item, citem-<ID>, MONEY, XP or COMMAND both
    Craft items / a custom recipe item / recipe ID both
    Smelt items (taken out of a furnace, smoker or blast furnace) item made, e.g. IRON_INGOT both
    Enchant items item, e.g. DIAMOND_SWORD both
    Spend levels enchanting – (one per level spent, 1 to 3) both
    Repair or rename on an anvil item made (only when levels are paid) both
    Brew potions ingredient, e.g. NETHER_WART (one per potion; whoever last opened the stand, within 16 blocks) both
    Trade with villagers item bought, e.g. EMERALD (one per trade) modern
    Breed animals mob, e.g. COW (survival/.../Quests/Breeding.sk) modern
    Tame animals mob, e.g. WOLF both
    Milk animals COW, MOOSHROOM, GOAT both (goats modern)
    Shear sheep / eat or drink – / item both
    Clear dungeons dungeon key; add the "On dungeon difficulty" condition for a difficulty key survival
    Sell or win at auction, play time, die, custom script event (Progress_Add(player, "custom:koth_win")) – / event name both

    Farmed actions give no job XP or money unless the setting Farmed actions give job XP is on: blocks a player placed and then broke (not crops that have grown, or logs from a sapling), placing again where a placed block was just broken (so replanting doesn't count), mobs from spawners, spawn eggs or breeding (so breed-and-kill loops don't pay), tilling the same block again within 10 minutes, milking the same animal within a minute, and fishing, fishing loot or brewing while AFK (when Anti-AFK is on). Servers keep placed blocks in memory, so a restart forgets them. Quests and badges still count farmed actions.

    Left out on purpose: earning coins (job money would count towards itself), selling to the shop (buy-and-sell loops), walking, swimming or flying a distance (water streams, ice and minecarts can be left running while AFK; use play time), and picking up items (drop-and-pick-up loops).

  • Levels: XP for level 1 → 2 and how much more each level needs (%), up to the highest level. Staff can set the exact XP needed for any level instead (under "Levels: XP, goals and rewards"); levels without one use the formula. Any level can also have goals to finish at the level below (kill 50 zombies, mine 200 iron ore), money, a message, and panel rewards (global coins, badges, global values, console commands). There's also money for every level up.

  • Requirements before /job lets a player take it: level here, another job's level, not doing another job, a finished quest, a badge, something done before (e.g. mined 1,000 stone), hours played, global coins, in-game money, a permission. The menu shows each one ticked or crossed. A job can also cost money to take.

  • Quests: give quests to a job on its page; only its players (from a level) can start them, and finishing one gives job XP.

  • Settings (Survival → Jobs): jobs at once, cooldown after leaving a job, cooldown between taking jobs, keep levels when leaving, the "+5 Miner XP" action bar, level-up announcements, Farmed actions give job XP (off by default, above), and Players ask staff to change jobs (on by default).

  • Job change limit (Survival → Jobs settings): how often a player can change job in a rolling window: 1 change every 24 hours, or 3 for Premium players, by default (0 = no limit; all three numbers are settings). A change is leaving a job in game, or a change request staff approve; taking a job (the first one, or another while under the job limit) isn't. It's checked when the player leaves or asks, so they're told straight away ("You can change again in 5h 12m") instead of waiting on staff, and it's counted when the change happens, so declined or cancelled requests cost nothing. Staff can tick Don't count it towards their job change limit when approving a request, for changes they make for the player. The /job menu has a clock icon with the changes left today (or when the next frees up, and what Premium gets), and the portal's Jobs page says the same. Changes are kept in player_job_changes.

  • Job change requests (panel: Survival → Job change requests, permission jobs.requests): while that setting is on, a player's first job is free to take, but leaving a job or swapping it for another is a request. Players send one in game (/job change <job> <new job|none> [reason], or by clicking another job in /job when they're at their job limit) or on the portal (Play → Jobs). Staff see the reason and what the new job needs, then approve or decline it with an optional note. Approving leaves the old job (its level is kept) and takes the new one, skipping cooldowns, requirements and the price. The answer goes to the player's inbox, and if they're online their server reloads their jobs and tells them straight away. One request at a time; /job change shows it and /job change cancel takes it back.

  • In-game: /job (menu: click to take, shift + right click to leave), /job join <job>, /job leave <job>, /job info [job], /job change .... XP is given straight away; progress is saved to the panel every 30 seconds and when the player leaves.

  • Portal (Play → Jobs): the player's jobs, levels and XP to the next level, and the change request form.

Postponing games #

Postponing games (network/World/Postpone.sk): turn on Postponeable for a category (Server groups → edit → Games, off by default) and staff can push back the next game on its servers. From the panel: a server's page → Postpone the next game (minutes, this server or every server in the category; needs servers.manage). In-game: /postpone <minutes>, /postpone off, or /postpone to see what's left (permission neutine.postpone). The game running now carries on; Tag waits in the lobby with a countdown on the boss bar, and /tag start ends a postponement. Other game scripts can check Postpone_Left() (seconds, 0 when not postponed).

Health bars above mobs #

Health bars above mobs (network/Combat/HealthBars.sk): off everywhere by default. Turn on "Health bars above mobs" in a category's rules, or for one server in its own rules (a server can also turn it off inside a category that has it on). "When mob health bars show" picks either 10 seconds after a mob is hurt or always (mobs within 24 blocks of a player). Only living mobs get one: not players, armour stands or NPCs, and a mob that already has a name (pets, name-tagged mobs) keeps its name. Turning it off clears bars near players within 2 seconds.

Spawn #

Spawn (network/World/Spawn.sk, every server): /spawn takes players to this server's spawn after standing still for spawn_warmup seconds (config.sk: 3, 5 on Pit; network.spawn.instant skips it); moving, being hit or being in combat cancels it. /setspawn (network.admin) sets it where you stand. It replaces Essentials' /spawn and /setspawn (their /espawn and /essentials:spawn forms too) and Pit's old /spawn. The spawn is the one set with /setspawn, else the lobby's (/setlobbyspawn), else the main world's; Pit's join and void rescue use it too. A player's first time on a server (nowhere to put them back) puts them at this spawn, not the world's own spawn point. In combat, players can't use commands that would get them away: /spawn, /hub, /lobby, /island (/is), /home, /sethome, /tpa and the other teleport commands, /warp, /back, /rtp, /server, /dungeon, /trade and /ah (any plugin:command form too; staff with neutine.commands.bypass can).

Teleport requests #

Teleport requests (network/World/Teleports.sk): /tpa <player> and /tpahere <player> send the other player clickable [Accept] and [Deny] buttons (also /tpaccept, /tpdeny; requests last 2 minutes, 10 seconds between requests). Whoever moves stands still for 3 seconds and can't be in combat. /tpacancel takes a request back and /tptoggle stops requests. Essentials' forms (/etpa, /essentials:tpaccept…) are caught too, so it replaces Essentials' teleport requests; /tp and other staff teleports stay Essentials'. Same server only. Where it's on is the game rule Teleport requests: "Where Essentials is installed" (the default), On or Off.

If a staff member's panel account has their Minecraft UUID linked, the panel checks their role's permissions for in-game punishments too (punishments.revoke for lifting them).

Mana #

Mana (MP) (network/Players/Mana.sk). Off by default: turn on the Mana (MP) rule for a category (Servers → Groups → edit) or one server (Servers → edit). Off, or until a server has the panel's rules, nobody has MP, nothing shows, skills cost nothing and every mana function acts as "has enough" and changes nothing.

  • Rules (per category, each overridable per server): Max MP (100), MP regenerated per second (1), Most max MP artifacts can add (100) and Most MP per second artifacts can add (5) and MP on the action bar (Only while not full). They reach servers with the group rules on every heartbeat (mana, mana_max, mana_regen, mana_artifact_max, mana_artifact_regen, mana_bar in group.rules).
  • Text. Every mana message (the action bar "✦ 75/100 MP", "Not enough MP", /mana) can be reworded under Translations → Change the English wording (search mana), and translated like any game message.
  • Max MP and MP per second are the rule's number plus: the player's class (bonuses Extra max MP and Extra MP per second on the class form; modern servers, where classes run), script bonuses (Net_ManaBonus, below) and artifacts they carry (the More mana effect, Items → Artifacts). Each artifact can have its own limit: its bonus never takes max MP past that number. All artifacts together then stop at the category's two artifact caps. Class and script bonuses aren't capped.
  • MP is kept in server memory. It refills every second and is full again on every join and server switch. Players see it as a slot of its own on the shared action bar (core/Support/ActionBar.sk, source mana, e.g. ✦ 75/100 MP), joined with the other info there (combat timer, cooldowns, XP gains; on Survival the same layer PlayerAppUiActionbar__Intercept uses) rather than replacing it. The MP on the action bar rule (mana_bar) picks Only while not full (default; hidden as soon as MP is at max), Always (a persistent slot, sent again only when the numbers change) or Don't show it; turning mana off or leaving clears it. Its priority is 45: when the line is too long it's left out before hits, pet and class messages (50), cooldowns (60), the combat timer (70) and alerts (100), but kept over status (40) and XP gains (30). Not enough MP is a separate 2-second alert (source mana.short, priority 60). /mana shows MP, max and refill, and where each comes from. Texts are under Translations (msg.mana.*).
  • Class skills have an MP cost (active skills only, default 0; an upgrade level can have its own, see Classes and class skills). Where mana is on, the combo only works with enough MP, and doesn't start the cooldown otherwise; the skill menu shows the cost. Where mana is off it's free. Column class_skills.mana_cost (migration 2026_11_13_190651_add_mana_cost_to_class_skills_table.php), sent as mana_cost with the skills.
  • Script bonuses (Mana_Bonus / Net_ManaBonus(player, key, maxAdd, regenAdd, seconds)): a key of your own, 0 seconds for until removed (Net_ManaBonusRemove). They're saved with the game mode save ({addon::<uuid>::mana.bonus.<key>} = max|regen|until), so they follow the player across servers in the category; a timed one ends on time even while they're away. This is how skills, level rewards, pet abilities or blessings can raise MP later.
  • Hooks for Script editor projects (network/Panel/Hooks.sk, listed in the editor): Net_ManaOn, Net_Mana, Net_ManaMax, Net_ManaRegen, Net_ManaHas, Net_ManaUse (takes MP only if they have enough), Net_ManaGive, Net_ManaSet, Net_ManaBonus, Net_ManaBonusRemove and Net_ManaListen("command"): the console runs <command> <player> used|gave|short <amount> <mp left> whenever MP is spent, given or short (Skript 2.6.5 on Pit can't call a function by name, so a console-only command of yours is the callback on both versions). Network scripts call the Mana_* functions directly.
  • Works on 1.8 Pit (Skript 2.6.5) and modern servers. Tests: tests/Feature/ManaTest.php.

Anti-AFK #

Anti-AFK (Servers → Groups → edit, or Servers → edit for one server; network/Players/AntiAfk.sk). Off by default: turn on the Anti-AFK rule for a category or one server. Off, or until a server has the panel's rules, nobody is AFK and nothing changes.

  • How it's detected. A player is AFK after Minutes before a player is AFK (5) with no activity. The rules choose what counts as activity: Turning the camera (on), Moving (Any movement, Only moving on land, not in water or riding (default) or No), Chat and commands (on) and Hitting, breaking, placing and clicking (on, menus included). Looking and moving are checked once a second; jumping more than 10 blocks in a second is a teleport and doesn't count.
  • Staying in one spot. AFK if they stay this close to one spot (0, off). Set to a number of blocks, anyone who never gets further than that from one spot for the whole AFK time is AFK even while they move, look or click. That catches AFK pools, water streams and macros, but also players who mine or build in a small area, so keep it a few blocks wide.
  • What happens. What happens to AFK players: Nothing: they're only marked AFK (default), Kicked, Sent to the lobby or Teleported to spawn (the first world's spawn). Seconds of warning first (30, 0 for none) warns them in chat and on the action bar before a kick, lobby or spawn. The action waits until they're out of combat, and happens once per AFK spell. On the lobby itself, "Sent to the lobby" kicks. AFK players see AFK on the action bar (source afk, priority 40) until they're back.
  • Play time. AFK time counts as play time (off): AFK minutes don't add to the play time stat (profiles, leaderboards, play time join requirements) or play time quests.
  • Never AFK: players with the in-game permission network.afk.bypass (ops have every permission, so test with a normal player) and players who haven't signed in yet.
  • Text. Every message (msg.afk.*: AFK, back, the warnings, kicked, sent to the lobby or spawn) can be reworded under Translations → Change the English wording (search afk) and translated.
  • Hooks for Script editor projects (network/Panel/Hooks.sk): Net_IsAfk(player), Net_AfkSeconds(player) (seconds since their last activity) and Net_AfkActivity(player) (count something your script saw as activity). Network scripts use AntiAfk_Is, AntiAfk_Idle, AntiAfk_Activity and AntiAfk_CountsPlaytime.
  • Works on 1.8 Pit (Skript 2.6.5) and modern servers. Players read about it in the handbook (Being AFK) where the rule is on. Tests: tests/Feature/AntiAfkTest.php.

Blessings #

Blessings (Network gameplay → Blessings, /manage/blessings, permission blessings.manage; network/Players/Blessings.sk). A blessing lasts a while and gives an XP rate (1.5 = half as much XP again, 0.5 = half) and/or up to six potion effects, kept on while it lasts (written like SPEED:0, REGENERATION:1, the type then the level from 0; 1.8 and modern names both work). It works on every server. Staff give one on this page for its usual length or a number of minutes; an /inbox reward (Community → Rewards) can carry one; and game scripts can give the ones marked Scripts may give it with Blessing_Grant(player, "key") or Blessing_Grant(player, "key", minutes, "reason"). Giving a blessing to someone who has it makes it last longer instead of stacking. The page lists who has one now, and Take away ends it. Players are told when they get one and see theirs with /blessings (aliases /curses, /blessing). Giving and taking away are in the audit log.

Skill levels #

Every skill earns skill XP each time its owner casts it, on every server: class skills (network/Players/Classes.sk), Pit skills (pit/Combat/Skills.sk, 1.8) and Tag skills (tag/TagSkills.sk). network/Players/SkillXp.sk counts casts and sends them to the panel every 30 seconds through the queue (POST /api/v1/server/skill-xp, action record), so XP follows the player to every server. Passive skills count when they work, at most once every few seconds.

Staff set it under Network gameplay > Skill levels (permission skills.levels, audit action skills.levels): on or off, XP per cast (for every skill, or skill by skill), the total XP for each skill level, level-up notifications, and Upgrades need the skill level.

The skill level is separate from the upgrade level players buy with money. The upgrade level still sets what the skill does; cast XP never changes the numbers by itself. With "Upgrades need the skill level" ticked, buying upgrade level N needs skill level N first (the price stays the same). It's off by default, so nothing changes for existing players until staff turn it on.

Level-ups are sent with the NotificationService (type Rewards, prefix SKILLS). Players see skill levels in the skill menus in-game (/class skills, /skills on Pit, /tag skills) and on the portal at Play > Skills (/account/skills).