Lodehost
What you can ask it
You type in a chat box in the panel, in normal sentences. It is not a menu and not a list of instructions for you to follow: when it answers, the work is done or it says exactly where it stopped.
- Why did my server crash last night, and make sure it does not happen again
- Install a land claim plugin and set it up so players can protect their base
- The server lags every evening, find out why and fix what you can
- Turn on keep inventory and set the difficulty to hard
- Set up four staff ranks with prefixes and the permissions each rank needs
- Check my server for security problems
On a job of any size it takes a backup first, without being asked, and checks that the backup finished before it changes anything. Your nightly backups are there as well, underneath.
Two engines: Pulsar and Quasar
| Engine | Steps in one message | Made for |
|---|---|---|
| Pulsar | Up to 8 | A question, one setting, one plugin, a crash explained, the server status |
| Quasar | Up to 30 | Whole setups, several plugins that work together, performance tuning, deep digging through files |
| Auto | Picks one per message | Leaving the choice to the panel, which is what most owners do |
A step is one use of a tool followed by reading what came back. Quasar keeps going until the job is finished or the steps run out, and then tells you what is done and what is still open.
The 20 tools it works with
This is the whole list. What is not on it, the Copilot cannot do. Ten tools only read, seven change something and keep an undo, and three wait for your click in the careful modes. One of those, a restore, waits in every mode.
| Kind | Tools |
|---|---|
| Read only | Live status, performance check, folder listing, reading a file, the recent console log, installed plugins, the plugin catalogue, current settings, security check, backup list |
| Changes, with an undo | Install a plugin, turn a plugin back on, change settings, set a startup variable, send a console command, write a config file, take a backup |
| Waits for you | Turn a plugin off, restart the server, restore a backup |
| Limit | Number |
|---|---|
| Plugins it can install, all from our own catalogue | 510 |
| server.properties settings it knows | 63 |
| Known server config files it can write | 9 |
| Console commands it is allowed to send, by first word | 45 |
| Checks in the security scan | 31 |
The plugin catalogue is the same one behind the plugin installer. It has no tool that installs a plugin from a link, so no message can make it fetch a jar from somewhere else.
Three modes: how much it may do without asking
| Mode | Goes through on its own | Still waits for your click |
|---|---|---|
| Ask first | Nothing. Every change is a card with an Apply button | Everything |
| Accept edits | Settings, config files, installing plugins, backups | A restart, turning a plugin off, commands that touch a player, a restore |
| Auto | Everything on its allowed list, restarts included | A restore |
You choose the mode per message, under the chat box. A restore replaces every file on the server, so it waits for a person in every mode, and it takes a backup of the current state before it starts.
Every change can be taken back
- Per change. A setting keeps its old value, a config file keeps the version before, an installed plugin can be removed, and a console command stores the command that reverses it.
- Per message. One button takes back everything a message changed, in reverse order, so you end up where you started and not halfway.
- Per server. Before a large job it takes a full backup, which is the layer under the undo.
Every action is logged with who asked for it, what changed and how to undo it. Staff members use the Copilot with their own rights, so it never does more for them than they could do themselves.
It remembers your server and your rules
The Copilot keeps a memory per server. Part of it is measured, such as your server type, version, plugins and plan, so it does not start every chat by looking around. The other part you write: house rules of up to 2,000 characters, such as never remove the permissions plugin or take a backup before anything big.
House rules can only make it more careful. A rule can never give the Copilot a permission its safety checks refuse.
How the Copilot is paid for
The Copilot comes with every plan, from Camp to Ultimate, and every server starts with credits to use it. A message costs credits according to how much work it was: a short Pulsar question costs little, a long Quasar job more. You see the number move while it works.
| More credits | How |
|---|---|
| Ready packs | From 25,000 credits, bought in the panel |
| Your own amount | Anything from 10,000 to 2,000,000 credits |
| Volume discount | 10% off from 200,000 credits, 15% off from 500,000 |
| Automatic top up | Optional, set by the server owner |
The price of each pack is shown in the panel before you buy.
Written and checked against the panel by the Lodehost team, last reviewed on 17 September 2026.
