Everything we published

Beta

STYGION Keystone b0.4.1: what's new

Zones: what claimed land gives, and to whom — and everything 0.4 brought, since this is the first 0.4 on CurseForge.

  • Zones (territory.zones, editor → Community → Zones): pick land by who holds it in FTB Chunks — a server team (your spawn), one team, the land of any team with a member in a rank (a VIP's claim), a player's own land or own land and allies' — then who may use it (everybody, the team's members, members and allies, ranks, a permission) and what it gives: flight that just works (double-tap jump) or that needs /fly, and any effects at any level — Haste, Speed, Night Vision, Saturation for no hunger, Regeneration, whatever the pack has. Rules for the same place add up.
  • One flight, never a drop. Flying out of a place where flight just works into land where a player's own /fly works — a VIP+ over their own claim, a LEGEND anywhere — keeps them in the air as if they had typed /fly; anywhere else they land gently, as before.
  • Effects are quiet and only ours are taken back. Given for 5 seconds and topped up while you stay, without particles; a stronger potion or a beacon is never touched.
  • Every player chooses. /zone lists the effects places can give you, /zone <effect> off switches one off for you everywhere (and on brings it back), kept across logins. With the client half the same switches are in K → Settings → Places, one per effect.
  • GET /v1/territory/claimants lists the teams that hold land, for the editor and for anything else that wants it.
  • The old fly.* settings work exactly as before; zones is empty until you write one, so nothing changes by itself.

Everything new in 0.4 (0.4.0 was built but never published on its own)

Flying at spawn, and a restart that only warns you when it is going to happen.

  • Block and container audit with rollback (new module audit, on by default): who broke, placed, blew up, took out of or put into what, where and when - players, mobs, explosions under the player who lit them, and machines (Create deployers and drills, quarries) as # and their name. /keystone audit inspect and a click shows a block's history; /keystone audit lookup u:Ada t:2h r:20 a:break finds changes with CoreProtect's filter words; rollback undoes them and restore does them again, a few each tick (rollback.budget-ms, rollback.per-tick), never over a block somebody built since (unless #force), #preview counts first. The tick only queues a row; a thread of its own writes them in batches to keystone/audit/audit.db, about 77 bytes a change, chest contents deflated. A drill in a cobblestone generator is one row every limits.repeat, a burst past limits.cause-per-second is one summary row. keep.for (30d) and keep.max-size (4 GB) bound it. /keystone import coreprotect now takes CoreProtect's history in (once, however often it runs). Editor screen Block audit & rollback, API /v1/block-audit/* (owner-only scopes block-audit.read, .write, .purge), events AuditNoted (a mod adds its own row) and AuditRolledBack. Blocks Create contraptions and Sable ships lift out of the world are not recorded as breaks (they still exist, and putting them back would make two); fluids, fire and decay are left out.

  • Swear filter (new module filter, off until you turn it on): swear words in chat become ducks and potatoes (kachna, bramborák in Czech) - in game chat, across the Discord bridge both ways, and on signs and in books. Built-in lists for English and Czech/Slovak; your own words, exceptions and replacements in filter.toml and the editor. It sees through accents, look-alike letters, l33t, f*ck, doubled letters and s p a c e d letters, and catches words only whole or by stem, so Scunthorpe, assassin, kokos and sranda are left alone. Points for each caught word run off while the player is calm (1 every 10 min); at 3 a friendly private warning, at 5 a mute, each further filter mute within a day longer (5, 15, 60 min), the third asks the team with a ticket. Slurs and threats are not shown at all, mute straight away (60 min) and are recorded for the team (alert-channel). Who may read the original is the server's choice (original = nobody | staff). /keystone filter test|points|clear; the editor's Moderation screen shows mutes, points, what was caught and a box to try a line.

  • Moderation for your own tools. /v1/moderation/*: mutes, history, mute, unmute (scopes moderation.read, moderation.write), the filter's points, caught, points/clear, words, check. Events for mods: MuteRequested, MuteLiftRequested, SwearCaught. A signed moderation webhook (webhook.url, webhook.secret in moderation.toml; X-Keystone-Signature: sha256= HMAC of <timestamp>.<body>) tells your panel or bot about every mute, unmute, ban, unban, kick and catch.

  • A mute is a Discord timeout too (mute.game-to-discord, mute.discord-to-game in discord.toml, both off): muted in the game is timed out on Discord for as long (28 days at most; longer adds mute.role), a timeout on Discord mutes in the game, lifting either lifts both - one row in the ledger, like bans. The bot needs Moderate Members.

  • Chat in every language (new module translate, off until you turn it on): everybody reads one chat in their own language. A line in another language arrives a moment later in the reader's, marked [CS]; whether hovering (or clicking, which copies it) shows the original is the server's choice (original = hover | click | off). Players choose with /translate on|off|to <language> or in Keystone Settings (K → Language & voice). The translators are a chain you order - Groq (a language model that reads typos and slang), Azure Translator, DeepL Free, LibreTranslate - and when none can answer the line is shown as written. Each has its own switch, monthly character budget (Azure and DeepL default to their free tiers) and requests-a-minute ceiling, and rests after "too many" or "no"; a cache, one detection per line and a per-writer share keep the month for real chat. All off the server thread; a line never waits longer than patience (6 s). Chat lines go to the services you set up - nothing before a key is set, no names or ids; translations go back through the swear filter. Editor: Chat translation (state, usage against the budget, try a line); GET /v1/translate/usage, POST /v1/translate/try, /forget.

  • Translation pairs (translate.pairs, e.g. cs>en, sk>en, en>cs): only the listed language pairs are translated - Czech and Slovak for English readers, English for Czech ones, never Slovak for a Czech reader; a reader whose language no pair goes into, or a line known to be in an unlisted language, costs no request. Empty is as before: any language into the reader's.

  • /ai, the pack helper (new module helper, off): a player asks about the mods, the quests or the server and only they get the answer, from a model you point it at (any OpenAI-compatible address and key). It is given the server's mod list, FTB Quests' chapter and quest titles and your own notes, and told to say it does not know rather than invent; 5 questions per 10 minutes per player, 2 at once, off the server thread.

  • Chat read aloud (client half, off): Keystone Settings → Language & voice reads chat on the player's own computer with Piper - a female or a male voice, English and Czech, speed and volume. The engine and the voices (about 25 MB + 63 MB per language) are downloaded only when the player presses Download, into config/keystone/tts/, each checked against a SHA-256 in the jar. Windows and Linux; nothing is sent anywhere.

  • Vote sites by language: a line in votes.lists takes lang=cs (or any language): /vote, the vote window, the HUD and the reminders offer it only to players who read that language; lang=en is for everybody whose language has no sites of its own; a site without lang is for everybody, as before. A vote from a site a player is not offered still counts.

  • Player names complete in every command that takes one (/keystone ban|unban|kick|history, /playtime, /keystone crate give|history, badges, quests, votes, accounts forget, maintenance allow, /skin …): online players, and for the commands about somebody offline the players the server has seen.

  • Polls in chat (new module polls, off until you turn it on): staff ask with /poll create 2h "Asphalt or concrete at spawn?" "Asphalt" "Concrete" (or Question | A | B, 2-6 answers, permission keystone.polls.create), or on Discord with the bot's /poll (question, 2-6 answers, optional length; for Discord roles in discord-creators and for anybody whose Discord is linked to a player holding keystone.polls.create, discord-command turns it off); everybody online gets the question with a button per answer and its share (with the client half, a notice card with a POLL plate), Discord gets a card with buttons (discord-channel, events by default), and one count for both: a player whose Discord is linked votes once, in the game or on Discord, and a vote from before linking is folded in. Votes can be changed while it runs (change-vote), who-votes = linked keeps unlinked names out, a player joining while a poll runs is shown it, and when it ends (time or /poll close) the result goes to the game and Discord. /poll, /poll vote <id> <n>; GET /v1/polls (polls.read), POST /v1/polls/create|close|vote (polls.write, vote for a player or a Discord id from your own site or bot); the PollChanged event. Discord's own polls are not used: a bot cannot vote in them for a player.

  • Land for sale (new module plots, off until you turn it on): staff put the chunk they stand in up for sale with a price and a height cap (/plot sell 1sovereign 230, a whole area with /plot corner + /plot sell area, or /plot sell radius); a player walking in sees the price (with the client half, a faint red edge along the chunk), buys it with /plot buy where they stand or from K → Plots (a map of the land around them with prices and owners, their own plots, and for staff every zone and plot), and pays from their inventory in the server's coins, change given back (coins; or another mod's money through currency.take-command/give-command). The claim moves to the buyer's FTB Chunks team in the same moment - all or nothing: two buyers in one tick, a double click or a failed claim never charge twice or leave two owners, and the money goes back when the claim cannot be made. A bought plot is for good and by default does not use up the buyer's own claims (count-in-claim-limit); when the claims mod drops its claim (FTB Chunks' max_idle_days_before_unclaim, an admin unclaim), a plot from a zone goes back on sale at the zone's price, and a plot a player sold goes back to that player when somebody in their team was on within player-sales.return-days (30; else the server offers it, at the zone's price or at what it last went for; event action returned). Blocks above a plot's height cap are refused. Players may sell their own team's land to each other when player-sales.enabled is on (permission keystone.plots.sell, a server fee in percent, the seller paid when next online; a seller who lost the land sells nothing). Without FTB Chunks Keystone keeps its own record and protects bought plots itself (keeper). /plot info, /plot list, /plot unsell, /plot cap, /plot revoke; the editor's Plots screen; GET /v1/plots, /v1/plots/sales (plots.read), POST /v1/plots/offer|withdraw|cap|revoke (owner scope plots.write); the PlotChanged event.

  • /fly works at spawn. Land the server itself holds (spawn, a market, a public station - chunks claimed by the server's own team in FTB Chunks) is flown over by everybody who may /fly at all. Before, a VIP+ could fly over their own claims only and a LEGEND anywhere except where a chunk had a holder who was not them, which the server's team always is. Set fly.at-spawn = false in territory.toml to keep spawn on foot.

  • "Restart in 15 min" means a restart. The announcement (chat line, bar, Discord news) now starts only if the restart is worth its downtime at that moment; a server that is healthy and not old enough gets the quiet "skipped" line in the log instead of a warning followed by nothing. And once it has been announced it happens, even if memory dips back under the line during the countdown. A restart asked for by hand is announced as before. If the countdown starts late, the line says the time that is true now ("5 minutes"), not "15".

  • Who holds the world loaded. /keystone loaded (and the editor's new Loaded chunks screen, and GET /v1/loaded/sources with the new owner scope loaded.read; GET /v1/loaded with status.read gives the counts only) lists every source that keeps chunks in memory - players, vanilla /forceload, FTB Chunks force-loads, mods' chunk loaders through NeoForge's ticket controllers (Create Power Loader, Mekanism, AE2, ...), dimension spawns, moving structures such as Sable sub-levels, portals - with its owner, when they were last online, how many chunks it keeps and how many of those tick. Every kept chunk is put down to the one ticket that decides it, so the totals add up to what the server holds. /keystone loaded measure [seconds] times the tick and shares each area's time over the sources holding it; the editor draws a map of every kept chunk in its source's colour, with the hottest areas framed. /keystone loaded worlds counts per world. It only reads: an idle rule (idle.days, idle.action = report | release in loaded.toml) is off by default, and when set to release it lets go only of vanilla and FTB Chunks force-loads of owners away that long, each logged and optionally posted to Discord; mods' own chunk loaders are never touched. /keystone loaded release <row> lets go of one by hand (permission keystone.loaded.release, apart from keystone.loaded for looking).

  • The profiler's hottest chunks go where they say. The report named a 16 x 16-chunk area as if it were one chunk, so its teleport landed 16 times too close to 0 0; it now names the area and its middle chunk.

  • Player snapshots and inventory restore (new module snapshots, on by default). Keystone keeps what every player carries - inventory, armour, off hand, ender chest, Curios slots, experience, where they stood - when they die (before anything drops or a grave mod moves it), leave, change dimension and every 15 minutes when something changed. The team puts one back from the editor (Snapshots & restore, with a preview against what the player carries now) or with /keystone snapshots: fill puts stacks only into empty slots and leaves out what they already carry again, replace asks first and keeps what it replaced as a snapshot of its own, so it can be undone. Nothing is handed over twice: a snapshot restored once, or one older than the player's last restore, needs again; one restore per player at a time; somebody offline gets it at their next join, exactly once. Items from mods keep every component; one whose mod is gone is reported, never lost. Every restore is written down (who, what, how, the result), and "restored" goes into the player's newest open ticket. Kept 14 days, 30 ordinary and 20 deaths per player (snapshots.toml); everything stays in keystone.db, nothing is sent anywhere.

  • Internal: the ultimine outline is covered by a test for a flat 248-block floor (lines only round the rim).

  • Importers: move over from another server. /keystone import <source> [--dry-run] reads the files you used before and brings them into Keystone: EssentialsX (homes, warps, nicknames, kits, balances), LuckPerms (groups with weight, prefix, suffix and parents, permission lines per world, players' memberships with the end of a temporary one - from its YAML or JSON file storage), FTB Ranks (ranks as groups, players' ranks - SNBT and the newer JSON5 files), the game's own lists (bans into the ban ledger, operators into a group of your choice) and CoreProtect (counted now; taken into the block audit as soon as a build has one). --dry-run shows what would come over and what would be refused, and changes nothing; a second run finds everything already here, and nothing you already have is overwritten. A permission line limited to another server, or a temporary one, is left out rather than made wider. EssentialsX permission nodes become Keystone's (essentials.kits.* becomes keystone.kit.*). Balances are paid once through a console command you set (import.economy.command); Keystone keeps none. The report is printed, kept, and shown on the new Import screen of the editor. Settings import.*; owner-only API GET /v1/import, POST /v1/import/run.

  • Metrics for Prometheus and Grafana. A new module, off until you turn it on (openmetrics.enabled): GET /v1/metrics/prometheus (or ?format=openmetrics) answers TPS, tick time as median/p95/max, players, chunks and tick time per dimension, entities and block entities (and by mod), Java memory and garbage collection, and - while a profiler run is fresh - each mod's milliseconds per tick. It needs a key that holds metrics.read and nothing else (/keystone key new prometheus metrics.read). No player name is in it unless you allow it (labels.players). A Grafana dashboard that matches the version ships in the jar (GET /v1/metrics/dashboard, and a button on the new Metrics screen).

  • A smooth UI, not a blocky one. Keystone's chat, notices, polls, chips, buttons and screens are drawn smooth at any GUI scale: round corners and real circles (heads, timeline dots, swatches), slanted plates and buttons without steps, diamonds and rings with soft edges, a real italic face (Atkinson Hyperlegible Next Italic) instead of slanted upright letters, times in JetBrains Mono, and text set like a desktop sets it rather than the game's blocky way: Keystone's faces rastered with light hinting and fuller strokes, every letter on whole screen pixels, a soft shadow straight under the words (as in the approved chat design) instead of a hard copy a whole GUI unit away, and the line you type in chat in the same face as the chat (cursor, selection and clicks measured in it); emoji and pictures stay smooth when drawn smaller than they are. No shader of its own, so Sodium, Iris and STYGION Render leave it alone. Keystone Settings → Theme → Smooth UI turns it off for the game's blocky look.

  • Colours to click, for those who may use them. A player whose colour codes work (chat.permissions.colour) gets an Aa tool in the chat input: the sixteen colours, the brand's colours and its gradient, the styles, and a preview of the line as others will read it; a click writes the code where the caret is. Coloured signs (new permission chat.permissions.signs, default keystone.sign.colour, given to nobody until you do): &c, &l and the rest on a sign turn into colour and style, and beside the sign editor the same picker colours a line or just the selected words, with the sign as it will look. Both pickers are roomy: bigger swatches and style keys, words as large as the chat's. A sign written before comes back with its codes when edited. Hex colours and gradients stay chat's.

  • A new chat: the Captain's Log. Messages hang on a rail down the left: each head is a node on it in its rank's colour, each name a slanted plate in its rank's gradient over the words. Lines from one player in a row share the plate (a dot on the rail), server lines carry a mustard diamond, joins a green dot with the head. Opening the chat draws the rail up from the bottom and spills the backdrop in from the left, with each message's time after its words; closing lets the lines run out and fade like the game's own; new lines rise in. A moving rank colour (<gradient:…:animate>, <rainbow:animate>, <pulse:…> in a prefix) flows along the plate with a glint and turns round the node - also on chips in the tab list; Keystone Settings → Chat → Animated colours holds every colour still. A mention - or an answer to your line - lays an orange bar along the line, rings the plate and pings the node three times. Hovering a line lights it and shows slanted ORIGINAL (for a translation) / REPLY / COPY; a right click opens the line's menu (Reply, Copy, the original, Mention). "X is typing" is a ring on the rail with a see-through plate and bouncing dots; @name suggestions are plates with heads. The input is a slanted field starting under the words with the hint after the caret, and three tools at its right.

  • Replies, like Discord. Reply on a line shows "Replying to " above the input; the answer carries a small curve and the quoted words above it, a click on the quote scrolls to the original and lights it up. Discord replies come into the game the same way, and a reply made in the game goes to Discord as a real reply (or a quote line when the bridge speaks through a webhook). Settings: chat.replies.*, discord.reply-pings, format.on-discord-reply.

  • Command panel. / typed (or the / tool) opens a panel of every command the player may run: search, categories, arguments, what each does (Keystone's own from the server, every other mod's usage from the game's command tree); ↑↓, Tab fills, Enter runs. chat.palette turns it off.

  • Emoji and GIFs. The emoji tool opens a picker with the Discord server's own emoji (animated ones move) and the standard emoji (Twemoji, CC-BY 4.0), searchable, in the line as pictures; :name: turns into its emoji; a line of only emoji is drawn big. The server fetches the pictures for the players (emoji.standard, the CDN in emoji.standard-source). GIF search through a provider the owner chooses and pays nothing for (gif.provider Giphy / KLIPY …, gif.key, off by default): a pick sends the line with the GIF, which moves in the chat; players without Keystone's client half see the link.

  • Notices in the chat's look. A notice can carry a category tag, a leading emoji, an image, a GIF or a link card like Discord's; its /commands are clickable chips; {key:<id>|<fallback>} in any Keystone text shows the reader's own key binding as a key cap.

  • The chat follows the game's Chat Settings: text opacity, background opacity (the open chat's backdrop), scale, width, both heights, line spacing, links and their prompt; bare https addresses in players' lines are clickable on the client too. Links are underlined only under the mouse; a channel's colours are calmer (Trade's green no longer shouts); the time is no longer shown twice on hover.

  • Keystone's own font, sharp at every GUI scale: Atkinson Hyperlegible Next and Archivo defined per GUI scale 1-6 across chat, K, the HUD, the changelog and toasts; Keystone Settings → Theme → Keystone font switches back to the game's.

  • The changelog reads well: version headings, bullets with a bold start, numbered and nested lists, code, a ~70-character column; one text can carry several languages (# Česky section) and each player gets theirs.

  • Chat shows where a line was said. Each line from a channel carries the channel's chip (its tag; Global none); clicking a tab switches without the "You now write in" reply (typing /channel still answers). Right click on a tab: mute or listen again, close a whisper, close a ticket; tabs that do not fit scroll with arrows; the ticket tab writes the answer directly.

  • Every rank on the chip. Chat and the tab list draw all of a player's prefixes as chips (tablist.chips-max, 2), reading MiniMessage gradients, &#hex and & codes, painted in the chip and never cut.

  • "X is typing…" is back in the Keystone chat style, and the player card is drawn over the chat lines, opaque, with the name once.

  • K belongs to Keystone on existing installs too (client.claim-hub-key, on): other controls on the hub's key are unbound once and the chat says which.

  • Ultimine says why nothing would be taken (not on the server's list - try Shapeless, a protected block, the wrong tool, a tree only from its trunk) instead of "Nothing to take here".

  • The real Keystone mark on the title and pause button, in K and Keystone Settings and on toasts, scaled to the screen's own pixels at every GUI scale.

  • Crates draw the whole prize: the reel and the open-all cards show the item with its model, look, name and colour (a coin is a coin, not a debug stick).

  • Keystone Settings rebuilt: tabs wrap, each tab scrolls in its own column, a short line under each switch, a fixed footer, nothing drawn over anything; the preview steps aside on a narrow screen.

  • A logo in the tab list (tablist.logo, logo-height, logo-align): a picture from the server's resource pack in place of the title.

  • A notice's picture in the chat: the picture of an announce.notices line appears under the notice in the Keystone chat style.

  • The profiler, as detailed as spark. A call tree per thread pool with self and total time, class and mod (pruned to tree.max-nodes, the rest summed as "smaller calls"); --threads server|workers|netty|io|all|<name>; --only-ticks-over <ms> keeps only the samples of slow ticks, with the tick's median, p95, p99 and max; GC pauses, the heap after GC and allocation in MB/s by mod and class; one JSON file with the whole report and tree, the .jfr on request (/keystone profile export, GET /v1/profiler/export, /v1/profiler/recording, buttons in the editor). Attribution like spark: mixins owned through their names, a mod that only wraps a call (@WrapOperation) is no longer charged for the call it wraps. The editor's Profiler screen has the tree (double click opens the hottest path), search, Hot methods, thread tabs, the slow-tick filter and memory. New settings sample-ms, threads, allocations, tree.*, keep-recording.

  • Measuring the tick costs only when asked. The per-thing tick measurement (profiles, benchmarks, a measured census) is cheaper on the hot path, the profiler's live view measures one tick in four, and a failed run can no longer leave it on; while a profile runs, Keystone's own measuring wrappers no longer take the blame for the game's work they wrap.

  • Backups tell the team. Start, progress and end of a backup go to everybody with keystone.backup.notify, in chat or as a boss bar with the percentage (backup.notify = chat | bossbar | both | off); players see nothing.

  • Yesterday's records. The daily report marks a new record - most online at once, most players in a day, most time played - with "New record!", and counts new players again (the game said "first time" for nobody, so the field was always 0; Keystone now looks for the player's own save file, which also makes the first-join kit and the first-join line on Discord work).

  • Pick a channel before you talk (chat.channels.require-choice, off by default): the first line waits until the player picks a channel from a clickable choice that says why; commands and private messages are never held.

  • Notices with a picture. A line in announce.notices may carry image=https://…: the server fetches it once (https only, nothing on the local network, PNG/JPEG/GIF up to 8 MB) and players with the client half see it in the chat under the notice; everybody gets the link too (announce.image-link).

  • Ban and lift from the editor and from tools: POST /v1/moderation/ban and /unban (moderation.write), the same ledger row, screen and Discord mirror as /ban in game; the Moderation screen has a ban line and Lift.

  • A timed ban ends on Discord too. With ban.game-to-discord on, a ban with an end lifts the Discord ban when it runs out - only a ban the game itself gave (marked in Discord's audit log), never while another account linked to the same Discord is still banned, and a Discord outage only postpones it.

  • The language question can be required, and asked again after an update (language.ask-on-join = off | once | version, default once - the old true/false read as once/off and the file is rewritten to the word; language.require-choice, default off): version asks again after every Keystone update. Under require-choice a player on their first choice stays where they stand with chat and every command but /language and the login held until they choose, for at most language.choice-timeout (2m; then their game's language, else language.default, is chosen for them) - a player asked again after an update is only asked, never held; a game with the client half gets a window that cannot be closed without a choice (each language named in itself, the question in its own words), a vanilla game the question in chat, one clickable name per language. The choice also sets the language the chat translator reads chat to them in. /keystone language ask <player> puts the question now (keystone.language.admin).

  • A vote reward never gives less than the player has (higher-rank.mode = skip | coins | both | give, default skip; a higher-rank = ... from an earlier 0.4 build is moved to higher-rank.mode as votes.toml opens - TOML cannot have higher-rank as a value and as the table of higher-rank.items at once): somebody who already holds a rank at least as heavy as the reward's (a LEGEND and a week of VIP+) is skipped and a top prize goes on to the next in line (skip), is paid in items instead - Keystone's marked coins, say - (coins, amounts per occasion in higher-rank.instead: top 1 = sovereign 3, streak 7 = seal 2, items as in crates.items under higher-rank.items), or both. Streaks and the month's top alike; items wait for a player who is away and come at the next join; the board says who was passed over and why.

  • Every screen and reply in the player's language. The kick, ban, maintenance and full screens are drawn in the player's language (also a /kick from the console), with English and the server's other languages at the door before anybody is known; what a crate gives is said in the player's language; the benchmark's own lines went to language keys.

  • /keystone worlds reset stygion:mining takes a world id with its colon.

  • Groups edited in the editor. Groups & permissions gains New group, Edit group (weight, prefix with a live preview, what it inherits) and Delete, and a line to allow or refuse a permission everywhere or in one world; an own rule is forgotten with its ×. Behind it POST /v1/groups/save, /v1/groups/rule and /v1/groups/delete (owner-only permissions.write): ids and permissions as the command takes them, every parent must exist and none may make a circle.

  • Tickets answered from the editor. A reply box and Close on the Tickets screen (/v1/tickets/reply and /close, scope tickets.write); the player reads the answer in game under the name of the key, in the same thread as answers from Discord and the game.

  • A player who is away shows what they hold in the editor's player detail (/v1/players/grants finds anybody the server has seen).

  • A chunk count never waits on the disk. /keystone loaded, the editor and the hourly idle check read the game's tickets on the server thread and name the people behind them from the database afterwards, off it.

  • Editor polish: Loaded chunks puts the sources table and the map across the whole width, groups its numbers and asks before a release in the editor's own dialog; Moderation shows a mute's reason under the name; Import says "the server folder" and the source's name in earlier runs; History and Updates & crashes never cut a value short; code blocks have their own look; a row that has no room wraps instead of running out of its card.

  • Internal: Permissions can define groups and lines (defineGroup, setGroupNode, groupNodes); Game.loadedChunksByWorld(); the profiler announces each run's per-mod cost as ProfileMeasured; routes can answer with plain text (http/Text).