Minecraft Server AI Copilot

Two models, one chat box

There are two engines behind the same chat box. Pulsar answers in seconds and takes up to 8 steps, which covers a question, a crash to read out or a single plugin to put in. Quasar takes up to 30 steps in one message and keeps going until the job is finished, checking the result of every step before it starts the next one. There is a third setting called Auto, and it is the one most people leave on: the panel reads your message and picks the engine that fits, so a one line question never costs you a large job and a large job never gets a one line answer.

What Quasar can build on its own

Quasar is the part that makes this more than a help desk in a chat box. It is an agent: it decides which of its 18 tools to use, it uses them on your live server, it reads what actually came back, and it decides the next step from that. Up to 30 of those steps fit in one message, which is why a request that would be an afternoon of clicking through a panel is one sentence to Quasar. You do not get a numbered list telling you what to do. The work is done when it answers.

These are the kinds of request it takes in a single message, not a menu of buttons but the actual sentences people send it:

• Set up an RPG server: classes, quests, an economy, a shop and the permissions to match
• My server lags every evening around eight, find out why and fix what you can
• Move my survival world to a new world manager and keep the spawn and the game rules
• Install a web map, put it on the right port and make it match my world border
• Go through my plugin configs and tell me which settings are fighting each other
• Set up a staff hierarchy with four ranks, prefixes and the permissions each rank needs
• Read the crash from last night and stop it from happening again
• Get this modpack server ready for twenty players instead of five

What happens after you press send is always the same shape, and it is the part that separates an agent from a chatbot that writes confident instructions:

1. It takes a backup first

   Before it touches anything on a job of this size it makes a full backup, without being asked. If the rest goes wrong you are one restore away from where you started, on top of the undo that every single change keeps.

2. It looks at what you already have

   Which server software and Minecraft version you run, which plugins are already installed and in which versions, what the console said in the last minutes, what your current settings are. It works on your server as it is, not on a clean example server.

3. It splits the job into pieces and starts

   A request like an RPG server is not one action but a dozen: a permissions plugin, an economy plugin, a world manager, a config file for each, an extra world, groups and their permissions. It does them one at a time instead of dumping a plan on you.

4. It reads the real result of every step

   After a command it waits for the console and reads back what the server actually answered. After a file it reads the file. A tool result is the truth and its own expectation is not, so a plugin that failed to load is caught in the next step rather than at the end.

5. It fixes what broke, or it stops and says so

   A missing dependency, a config key that moved between versions, a plugin that needs another one first: it deals with those as they come up. What it cannot fix it says out loud, at the point where it happened, instead of carrying on as if the step worked.

6. It tells you where it got to

   At the end you get a list of what changed and what is still open, every item with its own undo, and one button that takes the whole message back. If it runs out of steps or credits halfway it says exactly where it stopped so you can tell it to carry on.

It thinks harder than the fast engine before it acts, it writes longer answers when the job needs them, and it is allowed to keep going for as long as the work takes instead of stopping at a tidy paragraph. That costs more credits per message than a quick question, and it is the reason there are two engines rather than one: a question about your MOTD does not need thirty steps, and a whole server build does not fit in eight.

The safety rails do not loosen for it. Quasar installs from the same 510 vetted plugins, edits the same files, may send the same 45 console commands, and still cannot stop or restart your server without a person clicking. Everything it does keeps its undo, and one button takes back a whole message even when that message changed twenty things.

What it can do on your server

This is the whole list. 10 of these 18 tools only read, 6 change something and keep an undo, and 2 never run without your click: a restart, because it drops everyone who is online, and a restore, because it replaces every file on the server. It is the same list the agent itself is handed, so what is not here it cannot do.

The catalogue it installs from holds 510 plugins across 15 categories, and it resolves the build for your exact loader and Minecraft version at the moment it installs, so you do not end up with a jar for the wrong version. The names you would expect are in it:

• EssentialsX
• LuckPerms
• WorldEdit
• WorldGuard
• Vault
• CoreProtect
• Multiverse-Core
• PlaceholderAPI
• Dynmap
• ViaVersion
• Spark
• Chunky

Three modes, the way a code editor does it

How much the Copilot may do without asking is your choice, and you set it under the message box per message. The three modes are borrowed from the coding tools that got this right: you start by approving everything, and you loosen it once you trust what it does.

A restart is in none of the three. It drops everyone who is online, so it always waits for a person, even on Auto, even halfway through a job it started itself.

Backups it takes itself, and the one it will not press for you

Every server here gets a backup every night, ten slots, and an eleventh place that keeps the one that rolled out of the list for seven more days. That part runs whether you ask for it or not. What is new is that the Copilot can work with them: it sees the list with the exact moment each one was taken, it takes one on your word, and it can put the server back to one of them.

"Make a backup before I install these plugins" is the easy half. It takes one, then checks that it actually finished before it touches anything, because a backup that is still running is not a backup yet. On a job of any size it does this without being asked.

"Put the server back to how it was yesterday evening" is the half that needed rules. Three of them. First, there is no restore to a point in time: there are snapshots, so it tells you which one is nearest to the moment you named, at what time it was taken, and what falls in the gap. Second, it never presses the button. Not on Ask, not on Accept edits, not on Auto: a restore replaces every file on the server, so it waits for you. Third, and this is the one that makes the rest safe, it takes a backup of the server as it is at that moment before it restores anything. That backup is the way back, so a restore you regret is one click from undone, exactly like every other change it makes.

The server is stopped for the restore and started again by you, which is not us being careful for the sake of it: a server that is running holds the world in memory and writes it back when it shuts down, so a restore with the server up would quietly undo itself. And deleting a backup is not on its list at all. It can push the oldest one into that seven day trash to make room, the same way the nightly round does, and that is as close as it gets.

Restoring a backup, step by step walks through both routes side by side, and the backups themselves are on their own page.

One click takes it all back

Every change the Copilot makes is written down with the way back next to it. A changed setting keeps the old value, a written config file keeps the file as it was, an installed plugin can be uninstalled, and a console command stores the command that reverses it. That is per change, and you see them listed under the message that made them.

Under every message there is also a single button that takes back everything from that message. It walks the changes in reverse order, so a config file written after a plugin was installed goes back before the plugin does, and you end up where you started rather than halfway. Before a large job the Copilot takes a full backup on its own as well, which is the layer under the undo.

It remembers your server, so you stop repeating yourself

The Copilot keeps a memory per server, and it has two halves that are deliberately kept apart. The first half we measure ourselves: your server type and version, how many plugins are installed and which ones, how much memory and CPU your plan gives you, and the settings people actually care about such as difficulty, whitelist, PvP and view distance. Nobody types that half in. It refreshes itself every day, and the Copilot is told plainly that if a tool says something different, the tool is right and the memory is stale.

The second half you write: up to 2,000 characters of house rules, one per line. Keep the economy plugin enabled. Never remove the permissions plugin. Do not reset the world. Take a backup before anything big. The Copilot reads those before every single message, so you never have to say them twice, and it quotes the rule back at you when it follows one.

Two things about house rules that matter more than they sound. They can only make it more careful: a rule can never hand the Copilot a permission it does not have, and if a rule seems to allow something the safety checks refuse, the checks win and it says so. And the memory sits in the cached part of the conversation, so it is paid for roughly once every five minutes instead of on every step, while it removes the looking-around the Copilot would otherwise do at the start of every chat. Remembering your server makes it cheaper, not dearer.

It reads your public chat, on our machines, for nothing

Your players tell you what is wrong with your server every day, in chat, and nobody has time to read all of it. So we do. The Player experience tab sorts your public chat into lag complaints, grief and theft reports, questions nobody answered, moderation complaints, praise, players talking about leaving, and the one that matters most: somebody in chat casually mentioning a dupe, a glitch or an exploit. That last one usually shows up in chat hours before it shows up in your economy.

This runs on a language model on our own machines, not on a paid one, which is why a whole day of chat costs you nothing at all. Measured on our hardware it sorts 200 messages a second, so a busy day of ten thousand chat lines takes under a minute of a machine nobody is otherwise using. Only if it finds something serious, and only if you switch that on separately, does one short summary go to the Copilot and cost credits. Find nothing, pay nothing.

Private messages are never read. Not filtered out afterwards, never read: whispers, direct messages and every command a player types are recognised by the shape of the log line and skipped before anything looks at them, and we show you how many were skipped so you can see the filter working. It is off until you turn it on yourself, because it is your players' chat and not ours, and when a round finds something serious it can post it straight into your Discord.

What it is not allowed to do, and why that is in the code

An AI that can change a live server needs walls that a sentence cannot move. These limits are not written in the instructions we give the model, they are checks in our own code that run on every action, so a message that talks the model into trying something still hits the wall.

• Console commands go through three locks: the shape (one line, no chaining, no links), a deny list, and an allow list of 45 first words. Stopping the server, opping everyone, turning off the whitelist, banning an IP and clearing an area are all refused, in every mode.
• Plugins come from our catalogue of 510 vetted projects and from nowhere else. There is no install from a link anywhere in the product, so there is no prompt that produces one.
• Files stay inside the settings folders. Keys, certificates, environment files, your ops list, your whitelist, your ban lists and anything holding a password are refused by name, wherever they sit.
• Your server is never stopped or restarted without a person clicking, and nothing outside your own container is reachable at all.
• Every action is logged with who asked for it, what changed and how to undo it, so the history of a server is a list you can read back rather than something you have to trust.

The settings it does know are the 63 in server.properties plus 9 known configuration files for Paper, Purpur, Spigot, Pufferfish and Fabric, and the config folders of the plugins you have installed.

What it costs, in credits

The Copilot is included with every plan and there is nothing to order. Each server starts with 2,500 credits, and what a message costs depends on how much work it was: a short question to Pulsar is around 200 credits, a large job for Quasar runs into a few thousand. You watch the number move while it works, so there is no bill at the end that surprises you.

Buying more at once costs less per credit: 10% off from 200,000 credits, and 15% off from 500,000 credits. That discount is not a code you have to find and it is not a first order only deal, it is simply the price of that amount. You do not have to take one of the packs either: in the panel you can type your own number, anything from 10,000 to 2,000,000 credits, and the same discount applies to it. A server that runs one large Quasar job a day gets through roughly 90,000 credits in a month, so most owners buy once and forget about it for a while.

Credits do not expire and there is no monthly fee for the Copilot. If you would rather not think about it, you can switch on automatic top up: pick the level it may drop to and the pack it should buy, and it tops up from your saved card. That switch is the server owner's, not a staff member's.

Questions about the AI Copilot

Where to find it

The Copilot is in the panel of every Astroworld server, under the Copilot tab, and it is on from the first minute your server exists. You do not install anything and you do not order anything.

One thing it does deserves its own page, because it answers a question people ask before they ask about an assistant at all: the AI performance optimizer measures your live server in one pass, from tick time and tick rate to loaded entities per type, ticking chunks, memory and your plugins, and tells you in one sentence what is slowing it down. The thresholds it judges against are published there in full.

The AI security check, and what it looks at The panel the Copilot lives in Everything else that is included Installing plugins by hand Setting up crossplay by hand Reducing lag by hand Setting up permissions by hand View plans and prices Ask us a question first

The plugin count, the settings count, the command count, the step limits and the credit prices on this page are read from our own Copilot configuration when this page is built, so they change with the product. Written 30 August 2026.