# Installing it

> One file for both halves, plus STYGION Library from 0.3.4. Pick the Keystone for your Minecraft version, drop both in mods, start the server.

Source: https://stygion.eu/docs/keystone/install
Updated: 2026-10-30

**Keystone is one file, and from 0.3.4 a small second one beside it: [STYGION Library](https://www.curseforge.com/minecraft/mc-mods/stygion-library).** The same jars go in `mods/` on a server and in `mods/` on a player's client — there is no server edition and no client edition. What a server decides is not what the mod contains but what it *requires* of the people joining.

Everything Keystone does today is done by the server, so the server is where the file goes and nobody joining needs anything. The parts that have to draw something on somebody's screen — chat in full colour, the map, screens that look designed rather than like a chest — are the half that runs on a client, and when they arrive they are in this same file.

## Which file

Keystone runs on **NeoForge**. From 0.3 every release carries two Keystone files, one per Minecraft version, and their names say which is which:

```
keystone-neoforge-1.21.1-<version>+1.21.1-neoforge.jar
keystone-neoforge-26.2-<version>+26.2-neoforge.jar
```

Take the one that matches your Minecraft version. The wrong one does not half-work — it refuses to load and says so in the console, which is the answer you want rather than a server that starts and behaves strangely.

**From 0.3.4 Keystone needs [STYGION Library](https://www.curseforge.com/minecraft/mc-mods/stygion-library) beside it** — one file, `stygion-library-<version>.jar`, the same for 1.21.1 and 26.2. It carries the third-party libraries Keystone keeps its data and its off-site backups with (SQLite and SFTP), unmodified and with their licences; Keystone's own jar is then only our own code. Without it NeoForge stops at the loading screen and names the missing mod. On CurseForge it is installed with Keystone as a dependency, and STYGION Launcher installs it for you. Keystone 0.3.3 and older carry those libraries inside and do not need it.

**Fabric** was supported up to 0.2.x. The last Fabric build stays on CurseForge and keeps working, but it gets no further updates; a Fabric server that wants what comes next moves to NeoForge, and its `config/keystone/` and `keystone/` folders carry over unchanged.

## Putting it in

1. Stop the server.
2. Drop both files into `mods/`: Keystone and STYGION Library.
3. Start the server again.

A player who wants Keystone's client half (or plays single-player with it) puts the same two files in their own `mods/`.

That is the whole of it. On the first start Keystone writes two things next to your world:

- `config/keystone/` — one settings file per part of the mod, each one commented. Every setting there can also be changed from the game, the console or the editor, so you never have to come back here unless you want to.
- `keystone/` — its database. Ranks, tickets, punishments, votes, everything a player holds. Back it up with your world; it is one file.

## What leaves the machine, and when

**No IP address is ever written down.** An address exists only for as long as somebody is connecting, and what reaches the database instead is a *place*: a one-way token under a key your server made for itself and keeps in its own folder. The same machine still reads as the same machine — which is the only thing anything ever asks — and nobody, us included, can turn a place back into an address.

What can go out, and nothing else:

| Where | What | When |
|---|---|---|
| Mojang | A player's name, or their id | Only on an **offline-mode** server, to put their real skin on them and to check that a bought name is not being worn by somebody else. A server that checks with Mojang already asks nothing. |
| Discord | Chat, and a player's name in the avatar link | Only once you give it a bot token. |
| MineSkin | The picture somebody linked with `/skin <link>` — the image and nothing else, no name, no id | Only when a player runs that command. A blank setting turns it off. |
| An assistant provider | The question, with secrets stripped before it goes | Only once you write an address and a key in. It can be any provider, or none. |
| An error tracker (Sentry or GlitchTip) | A failure with Keystone's code in its stack: the exception type, its frames, the version and the loader; the exception's message only after secrets, addresses, e-mails, URLs, file paths, UUIDs and anything quoted are removed — **no player names, addresses or chat** | Only once you write `errors.dsn` in `keystone.toml`. Off by default, and the jar carries no address. The same failure at most once in ten minutes. |
| stygion.eu | Five minutes of tick timings once a day, your mod list, and what the machine is — **no server name, no address, no player, and no id of any kind, not even a random one** | On by default. It is what the [public figures](https://stygion.eu/performance) are built out of, and there is nothing in it that could be traced back to your server. |

**Turning that last one off:**

```
/keystone set bench.share-live false
```

Emptying `bench.send-to` stops everything this part of the mod could ever send, including a run you publish by hand.

Besides that there is **no update check and no call home**: a server in online mode with no bot token, no assistant key, no `errors.dsn` and `bench.share-live` off contacts nobody at all.

## What Java it needs

Whatever the game needs, which is Java 21 for Minecraft 1.21.1 and Java 25 for 26.2. If your server already starts, you already have the right one.

## Checking it worked

The console says so on startup:

```
[Keystone] Keystone is running. <n> modules, 1.21.1 on neoforge.
[Keystone] running on STYGION Library 1.0.0
[Keystone] [api] local API on http://127.0.0.1:25586
```

`<n>` is the number of modules that are running; a module that is off is not counted. If that first line does not appear, the file is for the wrong loader or the wrong Minecraft version, or STYGION Library is missing — see [When something is wrong](/docs/keystone/troubleshooting).

## Updating

Replace the file and restart. Settings and the database are kept, and anything new arrives with its default already in place, so an update never asks you to fill something in before the server will start.

**Updating to 0.3.4 or later from 0.3.3 or older:** add STYGION Library at the same time. Library itself changes rarely; a Keystone release says when it needs a newer one, and NeoForge names the version it wants if yours is too old.

**One thing an update does not do:** change a setting you already have. A default that improves in a new version only applies to servers that never touched it — yours keeps the value it has. If a release note says a default moved and you want the new one, set it yourself.

## Removing it

Take the file out and restart. Your world is untouched — Keystone never writes to it. The `config/keystone/` and `keystone/` folders stay where they are, so putting it back later finds everything as it was; delete them if you want it gone properly.
