The Minecraft server software that beats Paper on its own turf.
A high-performance PaperMC hard-fork that runs your Fabric/NeoForge mods and Bukkit/Spigot/Paper plugins together on one server — with roughly half the RAM and up to 2.3× faster chunk loading. Free to download and self-host, or run it fully tuned on Victus Cloud.
// system report — measured, not marketing
Faster chunk generation (dedicated nodes)
Less idle RAM than default ZGC
Spigot / Bukkit / Paper compatible
Lower far-mob AI tick cost (DAB)
Run mods and plugins on one server
Most server software makes you pick a lane — a modded Forge/Fabric world, or a Bukkit/Spigot/Paper plugin world. Victus Engine runs both at once, so your favourite mods and your whole plugin toolkit live on a single instance.
Fabric & NeoForge mods
Load the modern mods players actually run — you don't have to force everyone onto a mod-free server to keep your plugins.
Your full plugin toolkit
Every Bukkit/Spigot/Paper plugin keeps working right alongside the mods — economy, claims, anti-cheat, permissions, all of it.
Isolated + safe-mode
The hybrid layer is a self-contained module with a tested-compat safe-mode that auto-disables known-bad mod↔plugin combos, so one bad pairing can't sink the server. Pure-plugin instances never load a byte of it.
Mods · Fabric/NeoForge
Plugins · Bukkit/Spigot/Paper
one process · mods + plugins · tested-compat safe-mode
Serious performance — without breaking a single plugin
Every win here is measured on real hardware against a well-tuned stock Paper, not asserted. Compatibility is never the price of speed.
100% plugin compatible
A true PaperMC hard-fork — every Spigot, Bukkit and Paper plugin runs unchanged. Performance is never bought at the cost of your plugin list.
Roughly half the RAM
G1 + Aikar tuning + JDK 25 compact object headers + an elastic heap that gives memory back to the OS. Measured ~0.8 GB idle where default ZGC sat near 1.5 GB — same world, same plugins.
Up to 2.3× faster chunk loading
On a dedicated node the engine auto-uncaps Moonrise's chunk worker threads (which Paper keeps conservative for shared hosting). Shared/oversold nodes stay safe — it never steals a neighbour's cores.
Async chunk send + anti-stall watchdog
Chunk packets serialize off the main thread with Paper's in-order rail, and a watchdog guarantees every reserved slot is released — no permanent "Loading terrain" even if a worker dies.
Distance-throttled mob AI (DAB)
Far-away mobs tick their sensing, pathfinding and goals less often — cutting entity-AI cost while combat, mounts and nearby players always stay full-rate.
Hosting-first observability
A built-in Prometheus endpoint (chunk threads, async-send throughput, watchdog recoveries) and a /victus lag doctor that ranks tick offenders and suggests one-click, reversible fixes.
What actually changes vs stock Paper
A plain diff — red is a Paper default, green is what Victus Engine does instead. Hover a line for the why.
# Paper stays conservative so shared nodes don't fight; the engine detects a dedicated box and lets Moonrise use the cores.
# Compact headers shrink every object; G1 + an elastic heap hand memory back to the OS.
# Chunk threads, async-send throughput and watchdog recoveries are scraped out of the box.
# Every reserved packet slot is guaranteed to release — no permanent "Loading terrain".
# The hybrid layer runs both runtimes in one process behind a tested-compat safe-mode.
Get Victus Engine
Pick a build, grab the jar, run it. No account required, nothing to unlock.
victus@cloud:~$ victus fetch dev-26.2
resolving dev-26.2 … verified ✓- Async chunk-send anti-stall watchdog
- Dedicated-node chunk auto-tuning (~2.3× faster generation)
- Built-in Prometheus metrics + /victus lag doctor
- G1 + JDK 25 compact object headers — ~half the idle RAM of default ZGC
The runnable Paperclip server jar — java -jar victus-server.jar --nogui.
Optional: adds the /victus command + a Prometheus metrics endpoint. Drop into plugins/.
Quickstart
# Java 25 required
java -Xms2G -Xmx4G -jar victus-server.jar --noguiFirst boot writes a documented victus.yml. Drop plugins in plugins/ as usual.
What it does — and what it honestly doesn't
We'd rather you trust the numbers than be disappointed by them.
stdout
- Runs Fabric/NeoForge mods and your Bukkit/Spigot/Paper plugins on one server.
- Cuts RAM ~in half and boots faster, with your whole plugin stack loaded.
- Generates chunks ~2.3× faster on dedicated multi-core boxes.
- Stays 100% compatible on the default single-thread tier.
- Ships crossplay-ready (validated with Geyser, Floodgate and ViaVersion).
# won't pretend
- Promise a magic "100× TPS" — the tick is largely serial; no fork changes that.
- Speed up chunk gen on tiny/shared nodes (it stays conservative there on purpose).
- Enable experimental parallel/regionized ticking by default (it's opt-in and still hardening).
- Require our hosting — the jar runs anywhere Java 25 does.
Questions, answered honestly
> Does Victus Engine work with my existing plugins?
Yes — that's the whole point. Victus Engine is a hard-fork of PaperMC, so any Spigot, Bukkit, or Paper plugin runs unchanged. The default single-thread mode is 100% API-compatible; only the opt-in, experimental parallel-ticking tier changes threading, and it stays off by default.
> Can I run mods and plugins on the same server?
Yes — it's one of Victus Engine's headline features. It runs Fabric/NeoForge mods alongside your Bukkit/Spigot/Paper plugins on a single server, with the hybrid layer isolated behind a tested-compat safe-mode that auto-disables known-bad mod↔plugin combinations. Pure-plugin servers stay lean and never load it.
> How do I install it?
Run it like any Paper jar: java -Xms<size> -Xmx<size> -jar victus-server.jar --nogui. On first boot it writes a documented victus.yml you can tune, and your plugins go in the plugins/ folder as usual.
> How much faster is it, really?
Honestly measured, not marketing: on a dedicated multi-core node it generates chunks about 2.3× faster than stock Paper (by uncapping the chunk worker threads Paper deliberately keeps conservative for shared hosting), and it idles at roughly half the RAM of a default Generational-ZGC setup thanks to G1 + JDK 25 compact object headers. It is not a magic 100× — no server software is, and we won't pretend otherwise.
> Is it free? Is it open source?
The builds are free to download and self-host. Victus Engine is a PaperMC fork under the GPL; the compiled server and plugin jars are published on GitHub Releases.
> What Minecraft version does it support?
The current build targets Minecraft 26.2 on Java 25, and ships ViaVersion-friendly so older clients can connect through a proxy or the bundled compatibility layer.
> Do I have to use Victus Cloud hosting to run it?
No — the jar runs anywhere Java 25 runs, on your own box or any host. Hosting with Victus Cloud simply tunes it for you out of the box (elastic-RAM flags, dedicated-node chunk threads, metrics wired up).
Run the faster server.
Download the jar and self-host, or spin it up pre-tuned on Victus Cloud in about 60 seconds.