Roadmap · STYGION Keystone
Everything we are building, in the open
No dates, no promises we cannot keep. Just what we are thinking about, what we decided to do, what somebody is working on today, and what is already out.
Last thing out A project can be renamed, cards and all 3 weeks ago
Exploring
4Ideas we keep turning over. None of it is a promise.
Manage players and the world from the web
Inventory, status, punishments and weather can be handled from a browser — changes apply safely.
Crashes and TPS drops reported to Discord
Starts, crashes and performance drops arrive in Discord by themselves — no console watching.
Maintenance mode and anti-spam
Your own whitelist and screen during maintenance, plus protection against spam and abuse.
Optional STYGION ID link
Identity and server link — only if the admin wants. Mod still works offline to the cloud.
Planned
26Decided. Waiting for its turn.
The server says what it runs, and the launcher fetches it
Click a server and you are in it. The server states which modpack and which version it wants, right there in the list; STYGION Launcher picks that up, fetches the pack or switches to the right version, and connects you. You have it but three mods differ? It says which three. You added client-side mods of your own? They stay. And a server that says nothing behaves exactly as it does today.
One file, and the server says whether players need it too
Keystone is one mod. The same file goes on the server and into a player's client — no server edition, no client edition, no two version numbers to drift apart. The server picks whether it requires the client: a public server lets everybody in, and whoever has the mod also gets the maps, the screens and real colour in chat; a modpack server can require it, because there everybody has it anyway. Two people on one server, one with the mod and one without, are both served correctly — and the second is told what the file would add rather than handed a worse imitation of it.
Screens that look designed, not improvised
Quests, claims, teams and ranks get real interfaces in the game — a map you click to claim a chunk, not a row of items in a fake chest.
Claim a chunk by clicking it on a map
The grid over the world, your land and your neighbours’, and the limit counting down while you draw.
Watch the world from a browser
A live view of the spawn, a build or a station, drawn in the browser from what the server sees. Modded blocks included.
A live window for your own page
Fixed views that cycle, embedded on the server’s own site, so a visitor sees the place before deciding to join.
Money the server already has
Payments, balances and shop history built on the currency a server already uses, instead of a second one nobody spends.
Machines stop at the border
Drills, saws and moving contraptions respect a claim the way a player does, so protected land stays protected.
A server behind a router is still yours to configure
Where a browser cannot reach the machine, a short code from the console pairs the two. What travels between them stays unreadable to everybody in the middle.
VIP that is yours to design
A rank hands out named benefits and the benefits are a list you edit. Flight, a seat kept on a full server, a colour, a higher home limit, cosmetics, a weekly kit. A fourth tier is a line in a file, not a new version of the mod. Nothing on the list can give anybody an advantage in the game.
Connect the server to a panel without opening a port
The server reaches out rather than waiting to be reached, so a machine behind a router works the same as one that is not. Where it connects to is a setting, so it is not tied to us.
Chat split into channels
The first time you join, a window offers the channels — Czech, English and whatever else the server sets up. You write into yours and read only that one; a command switches you. Otherwise it is the same chat you already know.
Claims visible on maps
Claimed territory shows up automatically in minimaps and on the server web map.
Homes, warps and teleports
The everyday commands players expect, including per-rank limits.
Vein and tree mining
Hold a key to take a whole vein or tree — balanced, and respecting other people’s claims.
One mod instead of the whole FTB set
Quests, teams, claims, essentials and ranks under one roof — no stitching ten mods together.
Drag-and-drop quest editor
Build the quest map with the mouse and see how it will look as you go.
A modern UI in game and on the web
One visual language everywhere, instead of cluttered windows from ten different mods.
Heavy work off the main thread
Saving, quests and data work stop blocking the server.
Smart throttling of distant machines and mobs
What nobody is watching ticks slower. On big modded servers you feel it in the TPS.
Fewer stalls from memory and recipe lookups
Cached recipes and chunk data, fewer garbage-collection pauses.
Quest trees, branches and secrets
Dependencies, optional branches, hidden quests and repeatable tasks with cooldowns.
Tasks for items, mobs, places and stats
From handing in an item through boss hunts to reaching a place or a vanilla advancement.
Rewards, including team-wide and permissions
Items, XP, temporary and permanent perks, ranks — and rewards for a whole team.
Teams with roles and shared progress
Invites, roles, a shared bank and chat — plus quest progress that counts for the whole team.
Claims with granular protection
Set separately what members, allies and strangers may do — from chests to explosions and PvP.
Building
0Somebody has their hands on it right now.
Nothing here
Done
39Built and out. Newest at the top.
Documentation read out of the mod
Every module has its own page: what it does, what can be set on it, which commands it adds, and what to do when it behaves differently than you expected. Alongside it a complete reference to the interface — every path, what a key must hold to reach it, what it takes and what it is for — and, for settings, examples both ways: a server reached only from inside, and one somebody has to reach from outside. None of it is written from memory: the mod hands over the list of everything it has, and the pages are built from that, so after a fix they can be squared up again rather than guessed at.
Pick from what the pack actually has
A condition that names a mob, an item or a block should be something you click, not something you type from memory and get wrong. The server can be asked what it has loaded — every registry, everything in it, and the tags over it — with the mod each entry came from and the best name a server can give it. Modded entries included, without the mod having heard of the mod. It is what the editor's pickers read, and what quests, shops and rewards will read after them.
A rank the site can grant
A rank no longer has to be played for. A site says "this player holds this rank until this date", the mod writes it into the same list as everything else somebody holds, and takes it away on the day by itself — nobody has to remember to. And it finds the player through their linked Discord rather than a name typed into a form, so on a server without Mojang what somebody bought reaches the person who bought it.
Prove in game that an account is yours
Ask for a code in game, then type it on Discord as a command — so the code never becomes a message anybody has to delete, and the reply is visible only to you. A server that does not ask Mojang has no other way of knowing who somebody is: a link was made from inside the game under that name and confirmed by an account the game does not hand out. Which is why a shop can ask about it and deliver what somebody bought to the person who bought it, rather than to the right-looking name.
A page worth the mod, and everything ready to launch it
The product page is built whole while the mod is still being finished, so on release day it goes live together with the first download. The listing texts, the announcement and a short video are written before anybody is waiting for them.
Measurement that names the mod eating the tick
Test players spread far enough apart that each holds its own piece of the world, and the profile of a run splits the tick between individual mods — not only while the server is struggling, but all the time. A server that opts in then sends one anonymous sample a day, so the public figures describe real play rather than a synthetic test. One command turns it off.
No IP address is ever written down
An address exists only while somebody is connecting, and what the server records instead is a place: a one-way token under a key that server made for itself and keeps to itself. The same machine still reads as the same machine — which is all anything ever asked — and nobody, us included, can turn a place back into an address. It also makes the warning better: "somebody is joining as you, from somewhere you have never connected from" is a question a player can actually answer, where four numbers about their own house is not.
Live metrics and lag-spike hunting
TPS, tick time, memory, chunks, entities and players sampled continuously and kept for a week, so "it was bad last night" becomes a graph instead of a memory. Read in the editor, over the interface, or as it happens. It is also what the machine test later reads to say how many players this server actually holds.
Nothing changes without a record, and a change can be undone
Four things can change your server now — the console, the editor, the interface and the assistant — so "who turned that off on Tuesday" needs an answer. Every change made over the interface is written down with the key that made it and the person it was made for, and so is every refusal, because a key repeatedly trying what it may not do is the only sign you will get that an integration has been taken over. Settings go further: each change keeps the value it replaced, and one press puts it back — in the editor or from the console, because at two in the morning the browser is usually the thing you do not have. A credential is recorded as having been replaced and never as what it was replaced with.
Ask the server what is wrong with it
Ask in a sentence and get an answer that read the numbers instead of guessing: what the last hour looked like, why it stuttered at eight, what changed since yesterday. It can also propose a change to the settings — shown as a before and after, applied only when you say yes, written into the same history as everything else, and undone the same way. Hand it the last stretch of console and chat and it says what looks wrong, which is the job nobody has time for at the moment it would help. The conversation is one thread, whether you opened it in game, in the editor, or in a chat channel, and it is still there after a restart. A server owner brings their own model — anywhere they like, including one running on their own machine — and nothing secret is ever part of what is sent.
Bots that stand in for players
Spawn a marked bot that stands in for a player: it holds its chunk loaded, walks a small circle of where you put it, and costs the server what a person costs — because a bot standing still measures a cheaper server than the one you actually have. Labelled everywhere it appears, never counted as a real player, and taken out again when the test ends. It is a measuring instrument and nothing else: it never breaks, places or takes anything.
One command says how many players the machine actually holds
The question "how many people fit in here with this modpack" is answered today on the evening it matters. `/keystone test 20` answers it on a Tuesday: the server measures itself doing nothing first, then test players arrive in groups so that as much of the world loads as really would, and there is a verdict at the end. Because a quiet world measures a quiet world, the test can bring a known amount of extra work with it — the same amount on every machine and every pack, so two answers can actually be compared. Not just "TPS was 18" but where the time went: which mod, which place, which things. Nothing is written to the world, and every test player is taken out at the end.
A player list that says something
The list everybody opens twenty times an evening gets a header and a footer the server writes itself — the number of people, how the server is doing, where to find its Discord, whatever it wants to say — with each person's rank in front of their name. On newer Minecraft versions it is sorted by rank instead of alphabetically, so the list means something at a glance; on older ones there is no way to do that without taking name colours and friendly fire away from other mods, so it is left alone and said out loud rather than half-done.
Tickets that live with the server, not in a chat channel
One command in game opens a ticket, and what somebody can open is a list the server writes — each kind going to the people who handle that kind, and inside them to whoever is carrying the fewest. The answer arrives in chat, and when the person was away, the moment they next join. With a chat bot each ticket also gets its own private room for its team and the person who asked; when it closes the room goes and the whole conversation stays, because it was never kept in the room in the first place.
Vote rewards that actually arrive
Vote sites disagree about how they talk to a server, so Keystone speaks both ways at once and works on all of them rather than on half. A vote that arrives while somebody is away is kept and paid the moment they next join — once, in one line rather than ten. What it is worth is lines you write: a command for anything your mods can do, or a rank or perk that goes into the same list as everything else somebody holds and ends on its own date. Voting several days running can pay for itself, and a goal the whole server counts towards gives everybody online something when it lands. Nothing is accepted that is not properly signed, and the way in stays shut until the owner opens it.
Playtime and ranks
Playtime with two clocks — time connected and time actually moving — and the server decides which one a rank reads. Promotion on more than hours: mobs killed, blocks mined and placed, biomes visited, distance walked, each by the game's own name, so a modded creature counts without the mod having heard of it. Write the promotions as lines, commas meaning and; a line that does not make sense is named in the log rather than guessed at. `/playtime` says how far along you are, for anybody the server has ever seen — online or not.
Discord bridge
Chat and events both ways: what is said in game shows up on Discord and back again, with everybody wearing their own name and face. Roles that follow a promotion, a ban that means it in both places, the console in a channel, and a message when the server is struggling — and another when it is fine again. Prove an account is yours with a code the game gives you. It worked in 1.0.1 through code carried over from the old mod; that was deleted whole on 2 September 2026 and written again, properly, on all four builds.
Nobody plays wearing somebody else's name
A server that does not check with Mojang hands whoever types a name that name — including yours. Keystone closes it three ways, and the server owner picks which. A password, set once and typed after. Or nothing to remember at all: the moment somebody joins as you, a message arrives on Discord saying so, and you answer with a button — which also means an attempt you did not make reaches you as a warning instead of as a quiet theft. And a name that belongs to a real bought account cannot be worn here by anybody who cannot prove it is theirs. Until somebody has proved it they stand where they arrived, unable to move, be hurt, speak, or run a command.
Bans that end by themselves, and a history that remembers
Minecraft's own ban list has no expiry worth the name, so "banned for a week" has always meant a ban plus something else remembering to lift it. Keystone keeps one ledger instead: a reason, who decided, where it came from and when it ends — and it ends on its own. Nothing is ever deleted, so "has this person been in trouble before, and who let them back" is a question with an answer. You can also finally name somebody who is not standing in front of you: the server remembers everybody it has seen, follows a rename, and says so when one name has been worn by two accounts.
Nobody is turned away with "Kicked by an operator"
The screen somebody reads when they are refused is the moment they decide whether they were treated fairly — and Minecraft's own version of it says "You are banned from this server." with no reason, no name, no end date and nowhere to appeal. Every one of those screens is now a line you write: banned, banned until a date, kicked, maintenance, and a full server. The reason, who did it, when it ends and how long that is from now are filled in for you, and one command shows the finished screen exactly as a player reads it.
A cleaner that merges before it deletes, and maintenance mode
Stacks of the same item lying near each other become one — most servers go from twelve hundred entities to four hundred and nobody loses a thing. Only if that was not enough does a countdown start and anything get removed: items, experience and spent arrows by default, never mobs, with named and tamed animals and anything the game refuses to despawn protected. A server with nothing to clean is never counted down at, and one command says what a sweep would take before you trust it. Maintenance mode closes the server with a reason, and tells whoever tries to join the same thing in the same words.
Notices worth reading
A server that says the same three things to everybody every half hour teaches people to scroll past all of them — including the one that mattered. Here a notice carries who it is for, so somebody who already voted is not asked to vote. Chat, the action bar or across the screen, never twice in a row, and never to an empty world.
Backups you can afford to keep
Every backup is a whole world you can copy out and run — but a part of the world that has not changed since the last one is shared with it instead of copied, so a week of a 5 GB world costs about seven, not thirty-five. Taken the only way that is safe on a running server: saving flushed and paused for the length of the copy. Older ones thin out rather than vanish, a copy can go somewhere off the machine, and restoring is prepared and done on the next start — because a world cannot be swapped underneath a server that is playing.
Restarts that know whether they are needed
A restart at six because it is six is downtime a healthy server did not need. Keystone schedules a time and a reason: memory and TPS fine, uptime short — it is skipped and the console says so. Needed but somebody is playing — it waits for the world to empty, up to a limit you set. Nobody there — it goes quietly. The world is saved and flushed first, a boss bar counts the rest down, and on a machine with nothing watching it the server still comes back on its own.
One timetable, not four timers
Restarts, backups, cleanups and announcements are the same kind of thing: something with a time, a warning before it and a record after it. Keystone runs them off one schedule, so the countdown looks the same wherever it comes from, two heavy jobs never land on the same minute, and one screen shows what is coming and how long is left. Everything that ran is written down — including what a cleanup removed.
A tag builds the mod and releases it
Tagging a version builds every combination of loader and Minecraft version, boots a real server on each of them, and puts all four out together with what changed. A build that has not started, registered its commands and answered a call never goes out at all.
Rebuilt from nothing, in Java
One mod for both loaders and more than one Minecraft version, written so a new game version costs a small bridge instead of a rewrite.
Secure foundation: auth and fail-closed start
Admin only after sign-in, safe startup, data migrations, no demo content in runtime. Local-first, no required cloud.
Build your own on top of it
Keystone is open to addons: write your own module, quest task, reward or perk against an interface that travels inside the jar you already downloaded and carries no dependencies of its own — and it behaves exactly like the ones that ship with the mod.
Drive the server from your own tools
Everything the mod can do is also reachable over an interface, with keys you can keep narrow. Anyone can build a panel, a bot or a dashboard on it, not only us.
Everything a player holds ends on a date, and says where it came from
Bought, played for, won in a quest, given by an admin. One list, one history, and it expires on its own without anybody remembering to take it back.
Everything can be switched off
An unused module never loads — it costs no memory and no CPU.
Web control panel
Configure the whole mod from a browser instead of editing configs over SFTP.
Changes apply without a restart
Save on the web and it is live in game — nobody gets kicked.
Ranks and permissions without another mod
Inheritance, prefixes and chat colours built in — an ordinary server needs nothing extra.
Access via scoped keys
Every integration gets exactly the permissions it needs — and nothing more.
Runs on Fabric and NeoForge, on more than one Minecraft version
One mod, both loaders, and a version range rather than a single build. Written so that a new Minecraft version costs a small bridge instead of a rewrite.
The editor comes with the mod
The web interface ships inside the download and opens straight from your server. No account anywhere, and it works with the cable pulled out.
The mod has its own page
What Keystone is, what it replaces, how the four combinations of loader and Minecraft version differ, and where to get it. Until the first build exists the download says so plainly rather than pretending.