Introduction
What Storia is, what it adds to Folia, and which parts make up the project.
Storia is Minecraft server software for large communities. It is a fork of Folia, which is itself built on Paper, so it keeps Folia's regionized multithreading: nearby chunks are grouped into independent regions that tick in parallel on different CPU cores. On top of that, Storia adds features aimed at making a busy server feel like single player for everyone on it.
Storia is Italian for "history". The logo is a row of columns, like the entrance of a museum.
What Storia adds#
| Feature | In one sentence | Docs |
|---|---|---|
| RAM world | Worlds live in RAM and are written to disk in the background. | RAM world |
| Fast pregeneration | /storia pregen uses every core but one and can be resumed. |
Chunk pregeneration |
| Tick guard | A crowded spot like spawn stays smooth: the crowd thinks less, the players are not limited. | Tick guard |
| Per-player budget | Only players who add load themselves (flying fast) get a shorter view distance while it is busy. | Per-player budget |
| Faster physics | Entity pushing is about 3× faster with identical results. Redstone is untouched. | Performance & tuning |
| Faster world generation | Optimized noise sampling; terrain is identical to vanilla for the same seed. | Performance & tuning |
| Terrain offload | The heaviest step of terrain generation can run on other machines, encrypted. | Offloading terrain |
| Storia Proxy | A Velocity fork with 50 placeholders for MOTD, tab list and messages. | Proxy setup |
Design rules#
Everything in Storia follows three rules:
- Vanilla results. The same seed produces the same terrain, and entities are pushed in the same order with the same random rolls. Changes to terrain and physics are verified bit for bit against the original code.
- Redstone never stops. No optimization pauses, slows or skips redstone, and by default nothing lowers the simulation distance, so farms and machines near players keep running.
- Safe fallbacks. If RAM is short, worlds load from disk. If a worker is slow or gone, the server generates terrain itself. A feature failing never takes the server down with it.
The programs#
For the full picture of how they connect, see How Storia works.
| Program | What it does | Java |
|---|---|---|
| Storia | The Minecraft server. | 25 |
| Storia Worker | Computes terrain for a Storia server on another machine. | 25 |
| Storia Relay | Shares terrain work between any number of workers. | 21+ |
| Storia Proxy | Velocity with built-in placeholders, tab list and MOTD. | 21+ |
All four are published on the downloads page and on GitHub Releases.
Is Storia right for my server?#
Storia is a good fit when:
- you have many players who spread out (survival, SMP, large towns, skyblock islands),
- your machine has several CPU cores, and
- your plugins support Folia (see Plugin compatibility).
If your server is small, or relies on plugins that only support Paper, Paper is the simpler choice. Folia's threading model changes how plugins must schedule work, and Storia inherits that.
Next: Getting started.