Players and the portal
Registration, the player portal, saved data, stats, friends, the inbox, faces and skins, and the data filters on staff tables.
Player portal #
Players and staff sign in at the same /login. Players (accounts without a staff role) land on /account. Staff land on the staff dashboard and get a My account link; on their account pages they get a Staff panel link. Players get 403 on every staff page.
Registration #
Registration (/register):
- The player enters their Minecraft username, email and a password. The username is resolved to the UUID our servers recorded when they joined, so they must have joined at least once. This also works behind offline-mode or ViaVersion proxies, where a Mojang lookup would return the wrong UUID.
- An 8-character code is emailed to them.
- Portal → game: in-game they type
/link CODE. The server shows which email (masked) the link is for, and gives them a second, 6-character code in chat. - Game → portal: the waiting page moves on by itself and asks for that second code. Once it's entered, the account is created and linked to their UUID, the email becomes their verified notification address, and they're signed in.
Linking always needs both codes. The first proves the person in-game has the email. The second proves the person on the portal is that in-game player. Someone tricked into typing another person's code still can't be linked, unless they also hand over the code from their own chat, which the in-game message warns against. Codes are stored hashed. The email code lasts 30 minutes and the in-game code 10. Five wrong in-game codes void the link.
Portal pages #
Portal pages: overview (stats, rank, online status, active ban or mute), punishments (own record with reference numbers and appeal link), play history, and settings. In settings, players can change the game language (pushed to every server straight away), change their email (6-digit code sent to the new address), and change their password.
Staff without a linked Minecraft account can link one from My account, using the same two codes. The first is shown on screen instead of emailed. Linking also sets their staff minecraft_uuid for in-game punishments.
Guest access #
Guest access (/manage/guest-access, permission settings.manage, Administration > Guest access) chooses which portal pages and actions people who aren't signed in can view and use. Every page in the portal menu is listed by its menu group, plus the public pages outside the menu (the /premium store, /player/{name} profiles and /developers). Tick View to open a page to guests and Use to let them take its actions. Using needs viewing too. Changes are recorded in the audit log.
- Unticked pages send guests to sign in, then back to the page. Signed-in players aren't affected.
- Pages that can be opened to guests: play in browser (
/client), servers, leaderboards, boss lookup, vote, Gatcha, stock market, all crews, news, events, partners, updates, handbook, the help and documentation (/docs), apply for staff, feedback and/programs. Guests see the shared parts; anything about their own account (votes, wishes, trades, what they still need to join) asks them to sign in. - Actions: only buying Premium with PayPal on
/premiumcan be offered to guests. Applying, responding to feedback, wishing, trading, credits, coins and gift cards always need an account. - Always signed in: pages about a player's own things (home, stats, inventory, island, friends, settings...).
- Guests' menu shows only the ticked pages that are in the portal menu.
- Defaults: the public pages above are ticked (and buying on
/premium), and so are the handbook and the documentation (/docs, also open to every signed-in player and in the portal's Help menu). Servers, vote, Gatcha and the stock market need sign-in. A panel that had saved its choices before November 2026 gets the handbook and documentation ticked once by an update (php artisan migrate). Terms and the other legal pages are always public.
Client version and brand #
Each session records the client a player joined with, shown in the Client column of the Sessions tab on their player page and of Play history on the portal, for example 1.8.x, Lunar Client or 1.21-1.21.1, Fabric. Five seconds after a player joins, core/Players/Sessions.sk sends a client event to POST /server/players/session with:
client_protocol: the protocol number of their version. From ViaVersion when the server has it, otherwise from Paper, otherwise 47 (a 1.8 server without ViaVersion only lets 1.8 clients in).client_brand: what the client calls itself (vanilla,fabric,forge...). Only modern Paper can read this.client_channels: the plugin channels the client registered. Forge, Fabric, Lunar, Badlion, LabyMod and Feather register their own, so this is how 1.8 clients are told apart. A client with none of these is shown as Vanilla, so a client that hides itself also shows as Vanilla.
The panel turns these into a version name and a client name (App\Support\ClientInfo; a protocol newer than its list shows as Protocol <number>) and saves them on the player's open session on that server (client_version, client_brand). Closed sessions are never changed. Sessions from before this was added show –.
Deaths #
Deaths are on each player's page (Deaths tab): cause, killer, server and whether the inventory was kept. There is no separate staff Deaths page.
Stats (Saved data) #
Stats (Saved data). Every server group keeps detailed stats in the player's save, recorded by Stats.sk. Combat: kills (melee and bow), deaths (by players, the void and other causes), K/D, current and best kill streak, damage dealt and taken (see Damage below), arrows shot and hit, mobs killed, longest life and combat logs. Items and food: golden apples, golden heads, soups, other food and potions, items picked up, dropped and crafted, Item Shop purchases and money spent, loadouts used. World: blocks broken and placed, fish, distance travelled and jumps. Activity: time played, times joined, days active, chat messages, commands, and first and last played. Pit level, XP and highest level are recorded too. Staff see them by section on the player's Saved data tab. Players see their own under My stats on the portal. Other scripts can add their own with Stat_Add(player, "key"), and new keys show up automatically (labels are in app/Support/GameStats.php).
Editing saved data #
Editing saved data (permission players.edit_data). Edit values on a group's save changes money, vanilla XP level, health, hunger and any stat. Only the values you change are sent. If the player is on a server in that group, the change is queued to that server (storage_set), applied to them live, and kept by its next save; the edit page shows each queued edit's status. Otherwise the save is changed directly and they get it next time they join. Every edit is in the audit log.
Friend chat #
Friend chat. Click a friend on /account/friends to chat. The page updates every few seconds without reloading, messages go through the chat filter, unread counts show in the menu and on join, and the friend gets an in-game message they can click to open the chat (at most one ping per 30 seconds per conversation).
Faces and skins #
Faces and skins. Faces and full skins come from mc-heads.net and are shown next to names across the panel, the portal site (neutine-site) and the WordPress plugin, and the full skin on profiles. Player::skinId() picks what they're looked up by:
- By Mojang UUID when the stored UUID is a real Mojang one: version 4, not a Bedrock (Floodgate) UUID, and not the UUID an offline-mode server makes from the name. This happens behind an online-mode proxy or a premium login plugin. It is always the right skin, even after the player renames their Minecraft account.
- By username otherwise. Offline-mode servers give every player
UUID("OfflinePlayer:<name>")(Player::offlineUuid()), which Mojang doesn't know, so the name is all there is.
If an image can't load (mc-heads.net down, or blocked by a browser extension), a plain grey face (public/images/head-placeholder.svg) is shown, not a broken image. Images are loaded with referrerpolicy="no-referrer", so mc-heads.net isn't told which page they're on. The panel's API answers (head in site/players..., stat leaderboards) carry the same address, and the portal site and WordPress plugin use it.
What can't be fixed (offline mode). The "skin issue" comes from the servers running in offline mode. Nothing ties an offline player to a Minecraft account, so the panel can only guess by name:
- A player without a paid Minecraft account shows Steve (or another default skin), on the web and in game.
- A player who joins with the name of someone else's paid account shows that stranger's skin.
- In game, players' own skins on offline servers need a skin plugin (for example SkinsRestorer), which the panel can't replace.
The full fix is to know players' real accounts: an online-mode proxy, or a premium login plugin (FastLogin, LibreLogin...) that gives paid players their Mojang UUID. Heads then switch to the UUID by themselves, with no panel change. A future option is letting players upload or pick a skin on the portal, stored by the panel.
Data filters on staff tables #
Players and Community > Crews have Filter by data under the search box: rules such as "Time played is at least 10h", "Kills in Pit is at least 100", "Server coins (every game mode) is at most 0", "Last seen was not in the last 30 days" or "Premium is Premium". Every rule must match. Up to 10 rules, kept in the address (?f[0][field]=playtime&f[0][op]=gte&f[0][value]=10h, plus f[0][mode]=<game mode>), so a filtered list can be bookmarked or shared. Each rule in use shows as a tag with Remove, and Clear all filters keeps the search.
- Players: time played, first joined, last seen, network coins, credits, Premium, web account linked, server coins and every numeric stat (each in one game mode or every game mode).
- "Every game mode" adds the game modes up. Levels, streaks and longest life take the best one instead.
- Times: a number of hours, or
30m,10h,2d 6h,1w. Dates: a number of days, orYYYY-MM-DDfor before and after. A player with no saved value counts as 0, and "last seen was not in the last N days" includes players never seen. - A rule that doesn't make sense (a word where a number goes, an unknown game mode) is left out with a warning, never an error.
Adding filters to another table. Write a class like App\Support\DataFilters\PlayerFilters that returns a FilterSet of Filter::number(), duration(), date() and choice() (a column name, an SQL subquery, or a closure taking the chosen game mode). In the controller: $filters = MyFilters::make()->read($request); $filters->apply($query). In the view, inside the page's GET form: <x-data-filters :filters="$filters" />. The JavaScript in resources/js/app.js only narrows the rule list to the chosen field; the page works without it. Tests: tests/Feature/DataFiltersTest.php.
Badges and profiles #
Badges and profiles. Players wear one earned badge (portal or /badge). It's shown before their name in chat on every server as a coloured tag (each badge has an optional in-game tag, since 1.8 can't show emoji) and next to their name on the website. /player/<name> is their public profile: private until they turn it on, and they choose what's shown (game mode stats, all or some modes, total play time, badges, crew, quests, friends, join date, online status, and whether /stats works for others). Players can also show their survival island there in 3D, the same view as the portal's Island page: they turn it on under Show it on your profile on that page (off by default), and it follows the profile's privacy (see Islands in gameplay.md). Staff unlock themes per player (player page), or for everyone (Settings → Player profiles). There are 7 themes plus an accent colour. Game mode stats show one game mode at a time: the most played one, with links to the others (?mode=<slug>); the 30-day graph follows the chosen game mode. The portal site's /player/<name> and the WordPress plugin do the same, with an extra Across the network choice (mode=all) for the totals.
Damage. Every server records the final damage (after armour, enchantments and resistance, in hearts) each player deals and takes, split by who was on the other end: damage_dealt_players, damage_dealt_mobs, damage_taken_players, damage_taken_mobs and damage_taken_other (falls, fire, lava, drowning, the void, poison, their own arrows). damage_dealt and damage_taken are the combined totals. Arrows and other projectiles count for whoever shot them, tamed animals and lit TNT for their owner, and cosmetic pets already hit as their owner. Hits other scripts cancel (spawn protection, dungeons' mob-on-mob, SmartMobs, pets, combat rules) aren't counted: Stats.sk listens last (monitor) and skips cancelled events. Mob-on-mob damage and armour stands aren't counted, and one hit counts as at most the victim's max health. Hits add up in memory and go into the stats every 10 seconds and on quit, rounded to one decimal. The portal's My stats and the staff Saved data tab show a Damage table: players, mobs and other, then the totals, each with dealt, taken and the ratio (damage dealt per heart taken). The totals are older than the split, so a player can have more in a total than its parts; the table then says the totals include damage from before. Each key also has its own row under Combat and its own leaderboard. /stats shows the totals (Combat → Damage dealt / taken).
/stats #
/stats (also /profile) is a menu: head with their real skin, rank, badge, crew, join date, total play time and badges (and quests when shown), then three items: Combat (kills / deaths with K/D, kill streak, melee / bow kills, damage dealt / taken, arrow accuracy, and the player's live crit rate and crit damage), Progress (level and XP to the next one, highest level, time played here, days active, longest life) and Items and world (golden apples and heads, soups / potions, Item Shop buys, blocks broken / placed, mobs and elite mobs killed, fish, distance), plus their profile link. Crit rate and damage are worked out with the numbers combat rolls (Crit_Rate / Crit_Damage in network/Combat/Crits.sk): survival's crit rate and damage, the class's "critical" skills and Pit's "critical" skills at the player's level (not in a 1v1), all together. Each source rolls on its own, so the rate is the chance at least one crits and the damage is the average extra damage of a crit (+50% (x1.5)); skill cooldowns aren't counted. They only show while that player is on the same server, since they depend on it. It works for anyone on the network unless they made it private. Progress also shows the XP needed for the next level ("Level 12: 340 / 1.2K XP to level 13"), worked out with the server's own curve: the panel's XP curve where the XP system is on, otherwise the game mode's (Pit's and survival's own formulas). Servers save it with the stats as xp_next, so the portal profile and the /server/profile API (progress) show the same line; with no xp_next saved yet the portal uses the category's XP curve when the XP system is on there.
Broken stats. One hit counts as at most the victim's max health in Damage taken and Damage dealt (/kill and the void deal Float.MAX or infinite damage, which once showed as "170141173319264432646258688T"). Servers drop NaN, infinite or absurd amounts before adding them, the panel ignores saved stats that are NaN, infinite or over 1,000,000,000,000 (the old value stays), and short numbers past 999T show as 999T+ (? for NaN). To fix values already saved, run on the panel:
php artisan stats:repair
php artisan stats:repair --apply
The first lists every broken stat (category saves and the old network-wide stats) and changes nothing; --apply resets them to 0. --max=<n> changes the threshold. Players online at the time keep the bad number in memory until they rejoin, but their saves no longer write it back.
Game settings and the account lock #
Game settings and the account lock. Players can turn friend requests, private messages, online alerts, their pet, textmoji auto-replace and whether others see their stats and weapon in chat hovers on or off (portal Settings, or /settings and the lobby menu); /settings also opens their chat colour and custom messages. Staff can change any of them and lock it with a reason (player page → Settings and pets). Lock my account refuses every login with that username until it's turned off on the portal, and kicks whoever is on now, which protects offline-mode names. Servers keep the lock locally, so it still works while the panel is down.
Web clients (/client) #
Web clients (/client). Players can play in the browser on /client, no account needed, and switch between the clients staff upload under Servers → Web clients (permission clients.manage). A client is a zip with an index.html or another .html page, up to 1 GB unpacked. Only web files are accepted, so a zip with a .php file or an unsafe path is refused whole. PHP's upload_max_filesize and post_max_size must be big enough: the page shows the current limits. Clients run as web pages, so set CLIENT_URL to a second domain pointing at this panel: on the panel's own domain, a bad client could act as whoever is signed in. Files live in storage/app/web-clients.
Shulker Boxes #
Shulker Boxes. Hovering a Shulker Box in a saved inventory shows what's inside, for staff on a player's Saved data tab and for players on their own Inventory page. Modern servers only, and it fills in the next time a player's data is saved.
Inventory search #
Inventory search (portal: Inventory, Search tab, /account/inventory/search; App\Services\InventorySearch; in-game /search, network/Items/InventorySearch.sk). Players find where an item is, one category at a time, because each category keeps its own save. The portal's Inventory page (/account/inventory) has two tabs: Your items (each game's last save in a card that folds away, the newest open) and Search; the old Inventory search menu link is now that tab.
- On the portal the player picks a category (only categories they have a save in) and types a search. Every word must match the item's name, material (
diamond swordorDIAMOND_SWORD), custom item ID or custom item name, an enchantment (sharpness, also 1.8'sdamage_all) or a line of lore. Colour codes are ignored. - It searches the readable item list of their last save in that category (
items_view): inventory (hotbar, off hand), armour, ender chest, and what's inside each Shulker Box in those. It also looks at items waiting for them there: unclaimed inbox rewards that can be claimed in that category (custom items and auction wins) and the marketplace collection box. Island chests aren't searched. - Each result shows the item (with its icon from Item icons), the amount and where it is:
Hotbar 3,Inventory slot 12,Helmet,Ender chest slot 8,Inside <box name>, slot 5with where the box is,Inbox: <reward title>orMarketplace collection box. At most 200 results are shown. - It's read only, and a player only ever sees their own items. Saves are searched in PHP on each request (a save holds at most a few hundred items), so there is no index to keep up to date. Items moved since the last save show where they were.
- In-game,
/search <text>(alias/invsearch) does the same over what the player has on them right now on that server: inventory, armour, off hand, ender chest and the Shulker Boxes in them (modern servers; 1.8 has no shulker boxes or off hand). It lists up to 15 matches in chat with where each one is. Works on 1.8 Pit and modern servers. Its text is under Translations (msg.invsearch.*). - The rule: each category has an Inventory search game rule (Servers → Manage groups, on by default, a server can override it). Off leaves the category out of the portal search and turns
/searchoff on its servers. - Staff: the player page's Saved data tab has Search their items, the same search over every category of that player, with the permission that already shows saved data (
players.view). The rule doesn't hide categories from staff.
Save snapshots #
Save snapshots (player page → Saved data → Snapshots, /players/<name>/snapshots, permission players.snapshots). Each time a player leaves a server, a copy of their save for that category is kept, right after their final save arrives: money, stats, game data, inventory, armour, ender chest, effects, XP, health, hunger, gamemode and where they logged out. The newest 30 per category are kept. Restore puts a snapshot back after data loss or corruption: it replaces the player's save for that category with a new version (so a server still holding the old one can't write over it), and they get it the next time they join. What was there before is kept as a "Before a restore" snapshot, so a restore can be undone. A restore can't happen while the player is online in that category: kick them first. Every restore is in the audit log (players.snapshot_restore).
Player inbox #
Player inbox (player page → Inbox tab, permission inbox.send; network/Social/Inbox.sk). Staff write a message of up to 500 characters to one player, with & colours. It shows the sender's panel name, or Send as Anonymous shows "Anonymous" instead: the name is never sent to servers for those, but the panel keeps it, so staff who can open the tab (and the audit log) still see who sent it. Rewards staff send from Community → Rewards wait at the top of the same inbox. Messages are kept on the panel, so they follow the player to every server. A player who is online is told within seconds; one who is offline is told a few seconds after they next sign in (it's a notification, see Notifications). /inbox opens a chest menu, 45 to a page, newest first: click to read in chat, right click to delete. The Inbox tab shows each message as unread, read or deleted by the player. Players can't reply.
Notifications #
Notifications (App\Services\NotificationService, network/Players/Notifications.sk). Everything the panel or portal tells a player is kept in player_notifications until it has been seen, so nothing is lost when they're offline, on another server, or still at the in-game sign-in. Before this, messages went only to the player's last server, only while they were online, and expired after 2 minutes; ones that arrived while a player was held at the sign-in were buried under the sign-in prompt and never shown again.
- Live. If the player is online, the notification is pushed to their server at once (a
notifyaction carrying its id). It shows in chat with a sound and a short action bar line, and the server then marks it read. - Missed. If the push can't be shown yet (still signing in, data still loading, switching servers) the server leaves it unread. A few seconds after the player has signed in and their data is loaded, the server they joined asks for everything unread and shows it under "While you were away". It is only marked read once the server says it was shown, so a lost reply just means it comes again. If the panel can't be reached nothing waits on it.
/notifications(/notifs) lists the latest ones in chat, with buttons to mark them all read, clear them, or open the portal. Players see the same list on the portal under Account → Notifications (and the bell at the top); reading them in one place reads them in the other.- Muting. Players can mute types in-game in
/settings(the Notifications category) or on the portal: settings, rank, rewards and coins, quests, crew, friends and network notices. Muted ones still show on the portal. Account and security notices, punishments and staff messages can't be muted. - What sends them. Changes on the portal (game settings, language, chat colour, custom messages, sounds, chosen pet), password, email and in-game password changes, auto sign-in, a portal sign-in from a new place, rank and permission changes, punishments (issued, lifted, ended, and appeal answers), age verification decisions, inbox messages and rewards, quests, crews, friend requests, coins, badges, auctions, bounties, reports, staff applications and
Net_Notify()from Script editor projects. Anything sent throughFriendService::notifybecomes a notification; its type comes from its prefix. "A friend came online" is live only and not kept. - Punishments ride on their own ban, kick, mute or warning action (which shows the big notice in-game) and are marked read by it, so they aren't shown twice. The punishment-expiries task (every five minutes) tells players once when a ban or mute has run out.
- Other join reminders (unread inbox, friend requests, unread portal chats, quests, the link reminder) now also wait until the player has signed in.
- Staff send one from Players → Notifications (
/manage/notifications): to one player withnotifications.send, or to everyone who has played withnotifications.send_all. Both are in the audit log. Text is translated like other panel messages (config/panel_text.php). - Read notifications are deleted after 60 days and any after 180 (the prune task). Needs
coreandnetworkupdated together.
Friends #
Friends. Players use the portal page /account/friends or in-game /friend. Both use the same FriendService.
- Players can send, accept, decline and cancel requests, and remove friends. Adding someone who already asked you accepts their request. The limit is 100 friends.
- Requests and accepts are notifications (see Notifications): kept until seen. "X is now online on Pit 1" goes only to whichever server the friend is on, as a
notifyaction. - Players with pending requests get a reminder when they join.
Player IP addresses #
If every player shows the same private address (e.g. 172.18.0.9), that is your proxy's address inside Docker: the game servers aren't being told the player's real IP. The panel no longer saves private addresses (they made every player look like an alt of every other), cleared the ones it had, and warns on the server's page. To fix it:
- BungeeCord / Waterfall:
ip_forward: truein the proxy'sconfig.yml, andsettings.bungeecord: trueinspigot.ymlon every server (Pit and modern). - Velocity: Pit (1.8) only supports legacy forwarding, so use
player-info-forwarding-mode = "legacy"invelocity.toml, withsettings.bungeecord: trueinspigot.ymlon every server. (Modern forwarding works for 26.1 servers only.) - Restart the proxy and the servers. Keep the game servers' ports closed to the internet, or anyone can claim any IP and name.
Stats history, leaderboards and privacy #
stats:snapshot(hourly; one row per player, game mode and day) saves numeric stats for history graphs on profiles, the website and the API. A year is kept (history.keep_days).- Every numeric stat has a leaderboard (
App\Services\StatLeaderboards), for the network or one game mode, cached 5 minutes. The staff-made boards stay for in-game holograms. - Profiles are public by default now (ones already saved keep their choice). Players can hide their profile, leave the leaderboards, hide their history, or hide whole kinds of stats (Combat, World...).
Settings menu #
Game > Settings menu (settings.manage) groups the in-game /settings into categories with an item and order; anything not placed shows under Other. Category names can be translated. network/Players/Settings.sk opens on the categories, then that category's settings.
Editing buttons. Every button of the menu has an Edit link: each setting and menu, each category's button, Other and Back (/manage/settings-menu/items/{key}/edit). Staff can change:
- Item: a 1.8 material name, with an optional data value (
SKULL_ITEM:3). Newer servers translate it, so it works on 1.8 and modern servers; a name the server doesn't know shows as stone. A setting has an item for on and one for off; a locked setting is always a barrier. A category's item is the category's own. - Name and lore, with
&colour codes and one lore line per line. Placeholders:{label}and{help}(the setting's name and description),{colour}(green when on, red when off),{state}(the "On - click to turn off" line, or why staff locked it),{cc}(the player's chat colour), and on category buttons{name}and{count}. - Slot (0 to 53, 0 is the top left). A button with a slot goes there; the rest fill in from the second row, in order. If two pick the same slot, the first keeps it. Pages grow to fit (up to 6 rows), and Back moves along the bottom row if something is in its way.
- Left click and right click, each one of: switch a setting, turn a setting on, turn one off, open a menu (chat colour, custom messages, kill and death sounds, or the profile links), open a category, go back to the categories, run a command as the player (without the
/), send the player a message, close the menu, or nothing.{player}in a command or message is the player's name. Turning on the account lock from the menu is still refused, as before.
Empty fields, or fields left as the default, store nothing, so the button keeps following the default (and its translations). Back to the default forgets every change to a button. Add a button (on the Settings menu page) makes a button of your own, such as one that runs /discord; it goes in a category like any setting, and Remove button takes it away. Changed button names and lore can be translated under Translations (Settings menu buttons). Every change is in the audit log.
Preview. The Settings menu page and every edit page draw the menu like the game's chest menu, with the items' pictures (Item icons) or names. Hover a button for its name and lore, click or right-click it (Shift + Enter with the keyboard) to see what it does: settings switch, categories open, and anything that leaves the menu (a command, a link, another menu) is described underneath. It uses a pretend player with the default settings; nothing is saved. On an edit page the preview changes as you type.
On the servers. The panel works out every slot and sends them with the menu ({action: settings} on /server/profile: each category's slot, rows, slots and back_slot, home_rows, and items with only what staff changed on each button). The server keeps its own translated defaults for anything not changed, and still lays the menu out the old way if a panel sends no slots.
Ranks and permissions #
Ranks (Players → Ranks, /manage/ranks, permission ranks.manage; App\Services\RankService, network/Players/Permissions.sk): the network's own ranks and permissions, in place of LuckPerms. No permissions plugin is needed on any server.
-
Players with a rank (under the ranks list): a scrollable table of everyone holding a rank other than the default one, highest rank first, with when they got it, when it runs out, who gave it and why. Pick a rank (or click a rank's player count) to see only its holders. It shows up to 1,000; change someone's ranks on their page.
-
A rank has a name and a short name (
vip, fixed once made), a chat prefix ({rank}in the chat format, and before their name in tab and menus), a name colour (&a,&#ff8800), a weight, the ranks it inherits from, and permissions. One rank is the default: every player has it, under any others. -
Permissions are one per line:
essentials.fly; a*at the end covers everything under it (worldedit.*), and*alone is everything;-essentials.flytakes one away;essentials.fly @survival,pitis only on those categories; lines starting with#are notes. Mistakes are refused when saving, and so is inheriting in a circle. -
Players hold any number of ranks, each for good or until a time, plus the default one. Their main rank is the one with the highest weight: it gives their prefix and name colour, and it's the rank everything else goes by (chat colours, home limits, whitelist and quest rank checks,
players.rank). Their permissions are those of every rank they hold and the ranks those inherit, lowest weight first so higher ranks win, then their own permissions last. -
Giving ranks: on a player's page, under Ranks and permissions: set a rank as their only one or add it alongside, for good or for 1 day to 1 year, and give or take away their own permissions (also for a while, and per category). In-game:
/rank <player> set|add|remove <rank> [7d](permissionnetwork.rank; a linked staff account also needsranks.manage),/rank listand/rank <player>;/perms [player]shows someone's rank and permissions on that server. Every change is in the audit log. -
Running out: the expire-ranks task (every minute) takes away ranks and permissions whose time is up.
-
On the servers: the panel sends each player's main rank and their permissions in that server's category when they log in and the moment anything changes (a change to a rank goes to everyone holding it, or a rank inheriting it). The server gives them to the player with a Bukkit permission attachment, so plugins and Skript commands both see them, and refreshes their tab-completion. A node ending in
*is set as written and also expanded into every permission the server knows (registered by plugins or required by a command). What a player had is kept, so they keep it when the panel can't be reached at login. -
Moving from LuckPerms: the update made a rank for every rank name players had and every prefix under Settings → Chat (with a guessed weight, inheriting from Default), and gave each player theirs. Servers no longer report a player's LuckPerms group, and rank changes no longer run
lpcommands. Copy each group's permissions into its rank, check the weights, then LuckPerms can be removed. Needscoreandnetworkupdated together.
The network's own permissions #
These are the permissions the network's scripts check, to put in a rank's Permissions box (or a player's own). network.* gives every network. one and neutine.* every neutine. one; * gives everything, plugins' included. Plugins' own permissions (WorldEdit, EssentialsX and so on) are in their documentation.
Staff and admin
| Permission | What it allows | Where |
|---|---|---|
network.admin |
/network (the panel connection), /networkupdate, /chatfilter, /setspawn, /setlobbyspawn, and /language check |
every server |
network.rank |
/rank and /perms (a linked staff account also needs ranks.manage on the panel) |
every server |
network.lockdown |
/lockdown |
every server |
network.suspicious |
/suspicious, and the chat alert when a flagged player joins |
every server |
network.punish.ban |
/nban, and /ban and /tempban (sent to the panel) |
every server |
network.punish.mute |
/nmute, and /mute and /tempmute |
every server |
network.punish.kick |
/nkick and /kick |
every server |
network.punish.warn |
/nwarn and /warn |
every server |
network.punish.revoke |
/unban, /pardon and /unmute |
every server |
network.worldinfo |
/worldinfo (the world's rules and what applies here) |
every server |
network.mechanics |
/mechanics (the game mechanics in force here) |
every server |
network.combat |
/combat (weapon skills, enchantments, elements: test and give) |
every server |
network.items |
/citem and /rarity (custom items and rarity: give and check) |
every server |
network.particles |
/pfx (play a particle effect to test it) |
every server |
network.bosses |
/boss (spawn and manage bosses) |
modern servers |
network.elites |
/elite (spawn elite mobs) |
modern servers |
network.envoy |
/envoy staff options (start one, set drop points) |
every server |
network.leaderboard |
/leaderboard set and remove (place and remove leaderboard holograms) |
every server |
network.npcs |
/wildnpc |
every server |
network.quests |
/questplace (place quest NPCs and points) |
every server |
network.island.admin |
enter, build on and manage anyone's island, and go above its height limit | Survival |
network.dungeon.admin |
build, use blocked blocks, ender pearls and commands inside dungeons, and the staff /dungeon options (/dungeon end) |
Survival |
network.1v1 |
/1v1 setarena and /1v1 stop (the duel arena), and commands during a duel |
Pit |
neutine.tag.admin |
/tag staff options (start, reload, maps) and /map-spawn-point |
Tag |
neutine.postpone |
/postpone (postpone a scheduled game or event) |
every server |
neutine.admin.commands.events |
/nevents |
Survival |
neutine.admin.commands.prepare-update |
/prepare-update |
Survival |
neutine.admin.commands.purgetextdisplays |
/purgetextdisplays |
Survival |
neutine.admin.commands.setplayerstats |
/setplayerstats and /resetplayerscachestats |
Survival |
neutine.admin.ngive |
/ngive (give the network's items) |
Survival |
Bypasses (usually staff ranks)
| Permission | What it lets them skip | Where |
|---|---|---|
neutine.commands.bypass |
blocked commands (per server and inside dungeons), and the block on travel commands while in combat | every server |
network.joinrequirements.bypass |
a server's join requirements (level, rank and so on), checked by the panel | every server |
network.lockdown.bypass |
an emergency lockdown: they can still join and play | every server |
network.build |
the world rules that stop building and breaking | every server |
network.chatfilter.bypass |
the chat filter's blocked words | every server |
network.chatspam.bypass |
chat slow mode and repeat checks | every server |
network.settings.bypass |
players' settings that turn off private messages and chat from others: staff still get through | every server |
network.afk.bypass |
being marked AFK and moved for it | every server |
network.bosses.bypass |
boss attacks (they don't hit them) | modern servers |
network.spawn.instant |
the wait before /spawn teleports them |
every server |
Player perks (ranks like VIP, or everyone)
| Permission | What it gives | Where |
|---|---|---|
neutine.fly |
/fly in lobbies (Premium players get it anyway when Premium gives /fly) |
lobbies |
network.chat.colour |
& colours in chat, when Settings > Chat lets staff or a permission use them |
every server |
network.chat.gradient |
gradients and hex colours in chat, when Settings > Chat allows it by permission | every server |
neutine.command.alchemist |
/alchemist |
Survival |
A rank with network.* gets every network. permission above, bypasses included, so give staff ranks that only when they should skip all of them. To be sure the list is complete after a script update, search the scripts for has permission " and permission:.
Perks #
Perks (Players → Perks, /manage/perks, permission perks.manage; App\Services\PerkService): recurring perks for ranks, roles and programs. Pick a rank, role or program and add perks; each one is a reward and how often:
- Rewards: days of Player Premium, Crew: Premium (a code to redeem when they're not in a crew), Pets Premium or island access; global coins; credits; a custom item; a badge; a console command (
{player}is their name); a personal one-time store discount code from a template; or setting a per-player global value. Days of Premium stack on what the player already has, like any other grant. - How often: every N days, weeks or months, or once, when they're first given it.
- Who gets them: players holding the rank (not the default rank, which is everyone's), players whose portal account has the role (so their Minecraft account must be linked), and members of the program.
The give-perks task (network:give-perks, every hour) gives each player every perk that's due. A player's first period starts when they're first given the perk, and the next is due one period later. Every perk given is a row in the perk log, unique per perk, player and period, so it's never given twice for the same period, even if two runs overlap. Losing the rank, role or program stops future perks; what was given stays. Periods missed while they didn't have it, or while it was paused, aren't made up. Items and commands run on the server the player is on (or last was on); a player who has never joined gets nothing for those, and the log says so.
- Pausing: each rank, role and program has Pause on the Perks page (or the Paused box on its perks page): nobody gets its perks until it's resumed.
- The perk log (bottom of the Perks page, and Given lately on each one): who got what, when, from which rank, role or program, and when it's next due. Filter by player or by ranks, roles or programs.
- Players see their perks on the portal under Premium and credits → Your perks: what's coming up (and when) and what they've received.
Saving or pausing perks is in the audit log, and each run that gives perks adds one entry with how many perks and players.
In-game sign-in #
In-game sign-in (Players → In-game sign-in, /manage/sign-in, permission auth.manage; App\Services\GameAuth, network/Players/Auth.sk), in place of nLogin. The servers run in offline mode, so anyone could join with any name: with sign-in on, a name needs its password. It's on by default, on every server (servers that haven't heard from the panel yet treat it as on); staff can turn it off.
- Players:
/register <password> <password>(alias/reg) the first time, which claims the name;/login <password>(/l,/log) when they join from somewhere new;/changepassword <old> <new>(/changepass), which also signs them out of every other place;/logout, which signs them out everywhere and sends them off. Until they've signed in they're blind (a blindness effect, taken off as they sign in) and can't move (looking around is fine), chat, use any other command (only/login,/registerand/otpwork), build, break, use or drop items, open inventories or fight, and they're kicked when the time runs out (60 seconds by default). Their handbook has a page about it. - Staying signed in. Signing in (password,
/registeror a one-time code) starts a session for the name and the address the server sees. The panel keeps it alive while they're online on any server: every server's heartbeat (each 15 seconds) lists who's on it and from where, and a live session for that name and that exact address is moved on. After they leave it lasts for the grace window (Players → In-game sign-in → Staying signed in, "Still signed in after leaving", 5 minutes by default, 1 to 60). Joining any server, or rejoining, from the same address in that time needs no password; after it, or from any other address, they sign in again. The panel decides at every join (GET /server/players/{uuid},auth); servers only ask. When it lets them in on a session they already had,authsays why (restored:switch, moving between servers;returning, back from the same connection within the window, withminutes;auto, auto sign-in), and the server tells them once, in chat just after they join (msg.auth.restored_switch,msg.auth.restored_returning,msg.auth.restored_auto, all translatable), so they know why they weren't asked for/login. Signing in with/login,/registeror a code shows its own message instead. Because only the session's own "last seen" counts, it doesn't matter in what order, or how late, the old server's quit and the new server's join reach the panel, so a fast switch, a queued outbox or a heartbeat that closes and reopens a play session never asks again. - Why the same address, exactly: a different address may be someone else joining with the name (a server reached directly, a shared account). An exact match is the strict choice: a whole subnet (a /24, say) would let anyone at the same ISP or school in, and players whose address changes mid-visit (some mobile networks) just sign in once more. Anyone on the same connection (family, shared Wi-Fi) could still join as them within the grace window after they leave, which is why it's short and staff choose it.
- Ending it:
/logout(ends every session for the name and sends them off), changing the password (/changepasswordkeeps only where they are now;/resetpasswordafter/otpand the portal's new password likewise), a ban (any ban ends every session), staff (a player's page → Sign out everywhere, or Reset password). A heartbeat never brings back a session that ended or ran out: only signing in starts one. Starting a session (auth.session.start, with how and where) and ending one (auth.session.end, with why) are in the audit log; joining within the window isn't logged, but the session keeps where they were last seen. - What used to go wrong: before, the "still on the network" check read the play sessions built from join and quit events. Those go through each server's outbox and can arrive late or out of order, and a heartbeat can close and reopen a play session, so a switch sometimes looked like a new visit; a sign-in also ran out after 12 hours however long the player had been online, and leaving for a moment always asked again.
- IP forwarding: sign-in only trusts real player addresses. On a server with IP forwarding off, every player seems to come from the proxy's own address (see Player IP addresses), the same for everyone, so there auto sign-in is refused, the grace window doesn't apply and that address never lets anyone in by itself. Moving between servers while still on the network keeps working there (the proxy never lets one name connect twice): a server that sees the proxy accepts any live session of theirs while they're on another server right now or were seen in the last 30 seconds, and a server that sees their real address accepts one from the proxy's address the same way, but never one from a different real address. When it asks for a password, the server's console says why (
Sign-in: <uuid> must sign in: ...): no sign-in lately, away from this address for longer than the grace window, signed in from a different address, or (behind a proxy address) not on another server right now. Turn forwarding on everywhere: IP bans, alt detection and the grace window need it. Also keep the game servers reachable only through the proxy (a firewall, and Velocity's modern forwarding, whose forwarded address is signed): a server reached directly, or BungeeCord-style forwarding that anyone can write, would let someone claim any name and address. - Auto sign-in is off unless a player turns it on for their name:
/autologin onshows a warning (anyone on the same connection, such as family, a school, a shared Wi-Fi or a VPN, could join as them) and needs/autologin on confirm; or on the portal (Account → Settings → In-game password), after ticking that nobody else uses their connection. With it on, joining from the connection they last signed in from lets them straight in for 7 days (staff: 12 hours)./autologin off, the portal, or staff (a player's page) turn it off at once. On the sign-in page, staff choose whether players can use it (on by default) and whether staff can (off by default: staff accounts are the ones worth stealing); turning either off stops it for everyone it covers. - Passwords: at least 6 characters (staff choose), not the player's own name or a very common one, and case-sensitive. They're stored with bcrypt and only ever checked by the panel: a server sends what was typed to
POST /api/v1/server/players/signinand keeps nothing. Lines like "issued server command: /login …" are kept out of the console andlogs/latest.log(a Log4j filter added when the script loads), so the panel's live console never shows them, and the panel's command log skips these commands. - Guessing: 5 wrong passwords lock the name for 10 minutes (both can be changed), and 20 wrong ones from one IP across any names make that IP wait 10 minutes.
- When the panel can't be reached at login, the grace window can't be checked: a server lets a player in without a password only if they have auto sign-in on, from the IP it last saw them sign in from, until that would have run out; anyone else is asked to
/login, which works once the panel is back. - Forgotten passwords and one-time codes: a player signs in with a one-time code,
/otp <code>, then has 15 minutes to choose a new password with/resetpassword <new> <new>(no old one needed). Codes are 8 characters, work once, for 10 minutes, and only their hash is kept; a new code stops older ones. They come from:- Discord:
/otpwith no code DMs one to the Discord account linked to that name (at most once a minute), through the bot. Asking for a code doesn't sign anyone in: they stay held (no moving, chatting or commands) until they type/otp <code>. Only a reply to/login,/registeror/otp <code>signs a player in. Names without a linked Discord are told to use the portal or ask staff. - The portal: Account → Settings → In-game password: Get a one-time code, or set a new in-game password straight away after typing the website password.
- Staff: a player's page → In-game sign-in → Make a one-time code, shown once to pass on (only once you're sure it's them asking).
- Discord:
- Blocking mode (same page): refuses every join except the names on its list (names that haven't joined yet work too) and, if ticked, staff; they still sign in. Everyone else gets the blocking message, and anyone online who isn't allowed is sent off within 15 seconds of turning it on. Servers keep the list, so it holds while the panel can't be reached.
- Staff tools: a player's page has In-game sign-in: when they last signed in, whether the name is locked, Sign out everywhere, and Reset password (they choose a new one with
/registernext time they join: only do it once you're sure it's them asking). - Moving from nLogin: on the page, upload nLogin's SQLite file (from
plugins/nLogin), or, if it used MySQL, itsnlogintable (or another plugin's accounts) exported as CSV with a header row; commas, semicolons or tabs all work, and argon2 hashes don't need quoting even though they contain commas. Columns are found by name: the player's name (last_name,realname,name,username), password (password,hash), UUID (unique_id,uuid) and IP (last_ip,address,ip). Passwords in bcrypt or argon2 are used as they are, and nLogin's default SHA-256 ($SHA$salt$hash, the same as AuthMe's) is checked its way, then each is changed to bcrypt at the player's next sign-in. Passwords in any other format are counted in the import report, and those players choose a new one with/register. Names that already have a password are left alone, so importing twice is safe. Sign-in is on by default, so import before deploying this if you can, and remove nLogin from every server at the same time (with both, players are asked twice). Needscoreandnetworkupdated together.
Age verification #
Age verification (Players → Age verification, /manage/age-verification, permission age.manage; App\Services\AgeVerificationService, network/Players/AgeGate.sk) keeps some servers to players whose age staff have checked by hand.
- The rule: Age restricted is a game rule like Marketplace or Pets: set it on a category (Servers → Groups) or override it on one server. It's off by default everywhere. On an age restricted server, a player who isn't verified is refused at login with a message (translatable,
msg.age.not_verified) that links to the portal page. Turning it on while players are online sends off the ones who aren't verified within 15 seconds. Staff aren't exempt: verify staff accounts too (from their player page). - When the panel can't be reached at login, the server goes by what it remembers: whether it's age restricted, and who was verified when they last joined. Anyone it hasn't seen verified is refused, so it fails safe.
- Applying: players open Account → Age verification on the portal (they need a linked Minecraft account). They give their date of birth, pick one of the accepted documents and upload a photo or scan of it (JPG, PNG, WebP or PDF, up to 8 MB), and tick that it's theirs. The page shows their status: not applied, waiting for staff, verified, or rejected with staff's reason (they can apply again after a rejection).
- Manual checks only: nothing is checked automatically. Each new application posts to the Discord webhooks ticked for Age verification (Settings → Discord webhooks) and emails every active staff member with
age.manage, using the panel's mail settings. Neither says who applied or carries the date of birth or document: only a link to the review page. - Reviewing: the page lists waiting applications with the date of birth, the age it works out to (marked when under the minimum age), the document type and a link to open the document. Approve, or Reject with a reason the player sees. Players online are told in game. Every decision, status change, settings change and document view is in the audit log.
- Setting a status by hand: a player's page has Age verification: set them to verified, or not verified with a reason. If they have an application waiting, this decides it.
- Accepted documents and wording: the settings on the same page: the list of documents players choose from (one per line), the instructions above it, and the minimum age shown to players and used to mark applications (staff still decide).
- Privacy: documents are stored on the private disk (
storage/app/private/age-verifications), never the public one, and are only served to staff withage.managethrough the panel, not cached. The date of birth is encrypted in the database. Days to keep documents after a decision is 0 by default, which deletes the document the moment staff approve or reject; set up to 90 days to keep them longer. The prune-age-documents task (hourly) deletes documents past that. Waiting applications keep their document until decided. The date of birth and the decision are kept, so staff can see why someone was verified. Needscoreandnetworkupdated together.