Written entirely in C++23 and shipped as one native binary per platform. No bundled JRE and no hidden Java process. It has no garbage collector to pause, and Java and Bedrock players share the same world.
Early development
Basalt is young and not finished. Expect unexpected behaviour, missing features and changes between releases, and keep backups of anything you care about.
# verify the download (SHA256SUMS comes with each release)
sha256sum --check --ignore-missing SHA256SUMS
# make it executable and start it
chmod +x BasaltServer-*
./BasaltServer-<version>-Linux-x64They share their entire network layer through Wire: one implementation of the protocol, used by both sides.
The Minecraft server itself.
Vanilla parity is the goal for every system: same seed, same world, same drops, same redstone, same mobs, bugs included. Then a plugin platform on top of it.
One address in front of many servers.
A native proxy sharing Wire with the server: backends, forced hosts, fallback, forwarding and Java and Bedrock clients.
The plugin API is Lua and it is the fast path. Everything else is here so that moving to Basalt does not cost you what your server already runs on.
The plugin API is Lua, packaged and versioned, running in a sandbox with an instruction budget and a memory ceiling. No process boundary, no serialisation, no second heap.
Both editions join the same world. Bedrock and older Java clients are translated at the edge, built in, with no proxy and no plugins to add. Bedrock support is newer and has known limits, listed in the documentation.
The goal is the same seed, the same world, the same drops, damage, redstone and mobs. Where vanilla does something strange, Basalt aims to do the same strange thing. Parity is not complete yet.
There is no JVM heap to size and no collector that can pause the tick. Memory is managed directly, so a stutter has a cause you can profile.
Drop a Bukkit, Spigot or Paper jar into plugins/ and the server runs it on Basalt Shim, a Java machine embedded in the binary. Velocity and BungeeCord adapters for the proxy are planned.
A binary and a config folder. Nothing to install on the host and no runtime version to keep matched.
Plugins are packaged with a manifest, code, resources and metadata, and run inside a sandbox with an instruction budget. A broken plugin is stopped without taking the server down.
Text is authored in MiniMessage and rendered through the component model, never through legacy colour codes.
Plugin documentationon("player.join", function(e)
e.player:send("<gradient:aqua:green>Welcome!</gradient>")
end)The server, the proxy, the network layer they share and this site are all public. Read the code, file an issue, send a patch, or fork it and take it somewhere else.