Servers
Server groups, whitelist, emergency lockdown, storage, global values and scheduled jobs.
Server groups and per-group saves #
Server groups and per-group saves (Servers → Manage groups, permission servers.manage):
- Every server must belong to a group, a server type such as Pit, Survival or Lobby. Servers registered before groups existed were moved into Default.
- Servers in a group share one save per player in the
player_storagetable. Each save holds:- inventory, armour, ender chest and potion effects, stored as Bukkit-serialised base64 so enchantments, names and NBT survive
- XP level and progress, health, food, saturation and gamemode
- coins, game stats and game data
- The logout location is saved per server, not per group, in the
player_locationstable (App\Models\PlayerLocation). Survival US and Survival EU share items but run different worlds, so each restores its own spot. A player with no spot saved on a server goes to that server's spawn (Net_SpawnLocation), never to another server's coordinates. The group save still keeps the last spot anywhere in the group, which the player page shows as Logged out at.- Upgrading: the migration copies each existing group save's spot to the server that last wrote that save, which is where the player logged out. On the group's other servers they arrive at spawn once. Saves with no known writing server aren't copied.
- Resetting a player's save, or deleting a group's player data, also forgets their spots on that group's servers.
- Each group has four toggles:
- Keep inventory on death: default off.
- Restore inventory on join: on for new groups. It's off for Default, because the Pit kit script resets inventories on join.
- Restore location on join: default off. While a player is still signing in (
network/Players/Auth.sk) they wait at spawn and go to the restored spot once signed in. - Share one location across this group: default off. The old behaviour: every server in the group restores the group's last spot. Only for servers that run the same world.
- Changes reach servers within one heartbeat (15 seconds).
- The saving guards work per group. A late save from Survival is still accepted after the player moves to Pit, but two servers in the same group can't overwrite each other. A player's first visit to a group carries over their old network-wide stats once.
- The player page has a Saved data tab with a card per group and a Reset button.
- Each card shows the saved items, laid out like the game: armour and off hand, the inventory with the hotbar, the ender chest, and active effects. Hover an item (or open Every item as a list) for its custom name, enchantments and lore; enchanted items have a purple edge. With each save, servers send a readable list next to the serialised items (
Storage_Describeincore/Players/Storage.sk, stored asitems_view). The game still restores from the serialised items, so this list is only for staff to look at. Saves from before this change show their items after the player's next save. - Announcements can target a whole group.
Custom scheduled jobs #
Custom scheduled jobs (Tasks page → Custom jobs, permission tasks.manage): staff can create jobs that run a console command or post an announcement.
- When: a preset (every 5 or 15 minutes, hourly, daily…) or any cron expression, in UTC.
- Where: every server, one group or one server.
- Jobs can be paused, run now or deleted, and each run appears in the task history.
- Jobs are scheduled by the normal
schedule:runcron. No extra cron entry is needed.
Global values #
Global values (Global values, permission globals.manage): staff-defined values synced to every server.
- Per player: each player has their own value, with a default for players who don't have one yet (for example
chat.selected-colorortitle.selected). In Skript, usePlayerGlobal(player, "key")andSetPlayerGlobal(player, "key", value). Values load with the profile on join and save with every autosave and quit. - Network-wide: one value for the whole network (for example
event.xp-multiplier). In Skript, useGlobalValue("key"). - Types are text, number and yes/no. Values are checked and stored by type.
- Servers fetch
GET /server/globals?version=…every 30 seconds, and straight away when staff change something. The last copy is saved for restarts and outages. - Removing a value only hides it. Every stored value is kept and listed under "Removed (data kept)", and saves that still include a removed key are ignored, so that data can't be changed.
- Re-adding the same key restores it with its existing data. Only Overwrite existing values replaces it. For network values, that's the old value. For per-player values, it resets every player to the new default, including players who are online now.
- Editing a per-player default only affects players without a value, unless "reset every player" is ticked.
- The player page has a Global values tab where staff can set one player's value.
Deployment instructions #
Deployment instructions (Server groups → Deployment, readable with servers.view, edited with servers.manage under Server groups → edit): how to set up a new server in each category, written in Markdown. Until you change them, each category shows a general checklist (software, registering, config, network scripts, category update) that you can edit. Each server's page links to its category's instructions.
Server selector #
Server selector. What the lobby's compass menu shows. The menu moves players through the proxy by name, so a server's Proxy name (Servers → edit) must match your BungeeCord or Velocity config exactly. Empty means proxy_name::<ID> in the lobby's config.sk, then the server ID in lower case. If a player hasn't moved after 5 seconds they get a message, and the console logs the name that was tried. By default it lists every server on the panel, so a lobby mixes regions. To choose, open a server (Servers → edit → Server selector) and add an entry for each place players can go: the server it sends them to, plus an optional name, icon and description for that lobby. A category (Servers → Manage groups) can have a list too, for its servers that don't have their own. The server's list wins, then the category's, then every server. Entries show in the order they were added, up to 28, and empty parts use the target server's own name and description and the usual icon. Player counts and online status come from the target, a removed or disabled target drops off the list, and a lobby never lists itself. Wording set here isn't translated, unlike a server's own description.
Server name #
Server name. The name players see: the Pit and survival scoreboards, the survival tab list, and {server} in custom messages and global commands. By default each server uses server_name from its config.sk, which ships as Neutine | <server-id> (<server-id> becomes that server's server_id). To override it, set a title in Settings → Server name for every server, or under a category (Servers → Manage groups) or a single server (Servers → edit). The server wins, then the category, then the network, and empty means "use the next one up". A title can be a whole new name (&6&lPITFALL) or use <config> and <server-id> (Play <server-id>). The shipped config name already starts with Neutine |, so Neutine | <config> shows it twice: use Neutine | <server-id> instead. A server or category set to <config> goes back to the config name even when the level above has a title. & colour codes work. Pit scoreboards show the first 32 characters, the limit on 1.8. A server's edit page shows the config name it last reported. Servers pick up a change with the group settings, within 15 seconds. In your own scripts, use Net_ServerTitle().
Scoreboard footer. A last line under the Survival and Pit scoreboards, such as your website (Sidebar_Footer() in network/Players/Sidebar.sk). Two game rules (Servers → Groups → edit, overridable per server): Website or text at the bottom of the scoreboard (on by default) and Scoreboard bottom line (&e{website} to start with; {website} is the server's portal_url from its config.sk; colour codes work; old clients show about 32 characters). Survival puts a blank line before it; Pit puts it under its bottom divider, and takes it away again when the rule is off.
Storage #
Storage (Servers → Storage, /manage/storage, permission servers.view). The page has three parts:
- Game servers. Each server measures its disk every 5 minutes (
network/Panel/ServerStorage.sk) and sends it with the heartbeat (core/Players/Sessions.sk). The page shows free and total space, then each world's region files, world data and player data, and the logs folder. Only single folders are listed, so measuring takes a few milliseconds. A disk is low under 10% or 5 GB free; you can change both limits on the page. A low disk is marked on the page, on the server list (Disk free column) and on the server's page. Discord webhooks with Server state are told once when a disk runs low and once when it has room again. - This panel (needs
settings.manage). The web server's free disk, the size ofstorage/app,storage/logs,storage/frameworkandpublic/build, and the database's size with rows (and sizes, where the database reports them) for its 40 biggest tables. The results are kept for 10 minutes; Check again measures straight away. - Player saves. Per category: the number of saves, the total size, how much of that is items, and the biggest save. Below that is a list of the 25 biggest saves (filter by category), split into items and stats/data, linking to each player's Saved data.
Join requirements #
Join requirements (Servers → Manage groups → a category → Join requirements, and Servers → edit a server → Join requirements; App\Support\JoinRequirements, checked at login in core/Players/Sessions.sk and network/Players/JoinRequirements.sk). By default nothing is required and everyone joins as before. Staff can ask for any of these, and a player must meet all of them:
- Played at least (minutes on the whole network, the
playtime_minutescounter). - Network level (the highest
reach_levela server reported). - Level in a category: their level in that category's save (the
levelstat, which is the Pit level on Pit and the Survival level on Survival). Never played there counts as 0. - Rank (any of a list, by name or slug), quests finished, badges, Premium, in a crew (optionally of a crew level), a job they're doing now (optionally at a level), a pet at a level (any pet, or one chosen pet).
- Account linked to the portal, and age verified (staff approved it under Players → Age verification).
A server's requirements are added to its category's; one of the same kind (a playtime, a job, a level in the same category) replaces the category's. Tick Ignore the category's requirements to use only the server's. The server's edit page shows what the category asks for.
A player who doesn't meet them is refused when they join, with a list of what they still need in their language, for example "Play 5h on the network first (you have 2h 10m)", and a link to the portal's Servers page (/account/servers), which lists what every server needs and, with a linked account, what they're missing. The lobby's server selector shows the same list on a server they can't join yet. The wording is translatable: the lines are panel.join.* texts and the refusal around them is msg.joinreq.refused.
Bypass. Players with the permission network.joinrequirements.bypass (or *, or network.*) in that category join anyway. Give it to staff ranks under Players → Ranks.
When the panel can't be reached at login, each category (or server) chooses: Let everyone in (the default, so an outage never locks players out) or Only players this server saw meet them before (the server remembers who passed when they last joined, and refuses everyone else with "They can't be checked right now"). The setting reaches servers with the heartbeat. Players already online aren't sent off when requirements change; they're checked the next time they join. Works on 1.8 Pit and modern servers. Needs core and network updated together, and lobby for the selector.
To add a new kind of requirement, add it to JoinRequirements::TYPES, rules(), fromInput(), missing() and describe(), add its line to config/panel_text.php, and a field to resources/views/partials/join-requirements.blade.php.
Whitelist #
Whitelist (Servers → Whitelist, permission whitelist.manage; checked at login in core/Players/Sessions.sk): while a whitelist is on, only allowed players can join. Turn it on for every server, a category or one server, each with its own message (colour codes work). Players can still join if they're on the list (for every server, their category or that server; optionally for a number of days), have a bypass rank (e.g. owner, admin, mod), or are linked to a staff account (can be turned off). Saving with "Kick players who are online and not allowed" removes people already playing. Servers keep a copy, so it still works while the panel is down.
Emergency lockdown #
Emergency lockdown (Servers → Emergency lockdown, permission lockdown.manage; network/Moderation/Lockdown.sk): one switch that closes every server, or ticked categories, to everyone but staff. Tick what it does: stop joins, kick who's online, mute chat, block commands except a list (msg, tell, r, discord, hub, lobby, link to start with) and freeze players (no moving, building, breaking or fighting). Staff are active panel accounts linked to a Minecraft account, ops and anyone with network.lockdown.bypass; only the first can join while joins are stopped, since permissions aren't known at login. Saving pushes it to every server at once. In-game, /lockdown on [message], /lockdown off and /lockdown (permission network.lockdown) lock that server straight away, even with the panel down, then ask the panel to lock every server (a linked staff account needs lockdown.manage). Needs core and network updated together.
Console #
Console (network/Panel/Console.sk): Servers → a server → Console shows the server's logs/latest.log live (new lines every 2 seconds). Lines are sorted into info, warnings and errors (stack traces stay with their error); tick or untick each, or use "Only problems" / "Hide problems", and search. Staff with console.command can run console commands there; they go through the action queue, show their output in the console, and are in the audit log. The newest 5,000 lines per server are kept, for up to 7 days. IP addresses are hidden from staff without players.view_ips. On by default; turn off "Send the console to the panel" in a category's or server's rules to stop sending.
Console access #
Roles give console access everywhere: console.view to watch, console.command to run commands. To let one staff account into some consoles without changing its role, open Servers → Console access (permission console.grant), choose the account and where (every server, a category or one server), and tick Can also run console commands if they should. Remove takes it away again. The table shows who has access, where, and who gave it when; a console page has a "Who else can open this console" link to it.
- You can only give what your own role has: watching needs
console.view, commands needconsole.command. - Nobody can give access to themselves except an owner.
- It only works for active staff accounts. Deactivating an account, or taking away its staff role, stops it.
- Giving and removing it is turned off while you're signed in as someone else.
- Every grant and removal is in the audit log (
console.grant,console.revoke) with the account and the server or category. A command run through it is logged asserver.console_command, saying it came from console access.
Staff with access see Servers → Consoles, a list of the consoles they can open, so they don't need servers.view to find them. The check is the same on the console page, its live updates and sending a command: the role or a grant for that server.
Global commands #
Global commands (Servers → Global commands, needs commands.manage): commands made on the panel that every server answers, with an on/off switch. Each has a name and aliases, an optional permission and cooldown, chat lines with & colours ({player}, {server}, {online}, {args}), console commands ({player} only; {args} is refused there so players can't inject into the console) and an optional clickable link. Servers answer them from Bukkit's command event, so they work like normal commands but don't tab-complete; one here takes over a plugin command with the same name.
Deleting a category's player data #
Servers > Groups > Delete player data (players.wipe_data, owners only until you add it to a role) wipes one category, for example for a season reset. It needs a 6-digit code emailed to the staff member (valid 15 minutes, 5 tries) and the category's name typed out, and it refuses while anyone is online there. A database backup is made first, and nothing is deleted if that fails.
It clears saves (items, money, stats, location), logout spots and homes on those servers, players' own loadouts, loadout purchases, marketplace listings and uncollected items, item shop history, and progress on that category's quests. Accounts, ranks, global coins, pets, crews, jobs and moderation records stay. App\Services\CategoryDataWipe holds the list.
Update the servers first. Game servers keep a local copy of stats and hold inventories themselves, and a server that finds no save uploads its copy again. So saves are blanked, not removed, with player_storage.wiped_at set. The first join after that clears the player's local data and items (PlayerData_Forget, Storage_Clear), and their first save clears the flag. Older scripts ignore the flag, so items and local variables would survive. Saves based on a version from before the wipe are refused. The reset button for one player's save on their player page works the same way (PlayerStorage::blank()).
Database backups #
network:backup runs daily at 02:30 from the scheduler and can be paused or run from Scheduled tasks. The Database backups page (backups.manage) can also start one, download one after asking for a password or 2FA code, and delete one. It writes a gzipped SQL file in PHP, so mysqldump isn't needed, and checks the file reads back whole before saving it.
- Where:
backups/on the disk named byBACKUP_DISK, by defaultlocal(storage/app/private, not reachable from the web). Set it to an off-site disk fromconfig/filesystems.phpif you can, or copy the files off the server yourself. - What's in it: every table except the data in
sessions,cache,cache_locks,jobsandjob_batches, which are recreated empty. Files aren't encrypted, so treat them like the database itself. - What isn't: uploaded files and
APP_KEY. KeepAPP_KEYsafe separately, because encrypted columns can't be read without it. - Restore: try this on a spare database first. It replaces every table in the target.
gunzip -c neutine-2026-11-02-023000.sql.gz | mysql --default-character-set=utf8mb4 -u USER -p DATABASE
For SQLite, use sqlite3 database.sqlite in place of mysql and its options.
Data exports #
- Players and staff: Account > Settings > Your data downloads a JSON copy of what we hold about them.
App\Services\PersonalDataExportlists tables and columns by hand; add new personal data there. It is limited to 5 downloads an hour. - Staff: Data exports (
data.export) offers CSV files of players, accounts, punishments, store payments and the audit log. Each also needs the permission that opens that list. They leave out IP addresses, password hashes and staff notes, and guard against spreadsheet formulas in player-typed text. Add one inApp\Support\DataExports.
Every download is in the audit log, and none of them work during "Sign in as". Backups and exports need new permissions, so only owners have them until you add them to a role.