Aurora region engine
Each world region runs on its own tick thread. Paper remains the compatibility input; Aurora owns the execution model and the scheduler inside SourbyCraft.
A Minecraft runtime with its own execution model.
A Paper fork built around Aurora: region-threaded ticking, first-party operator tooling, and a native path for server-side mods.
SourbyCraft treats Paper as an upstream implementation source, not as the architectural ceiling. Aurora can replace execution paths when measurement and correctness justify it, while the Bukkit and Paper surface stays the compatibility contract.
The current target is Minecraft 26.2 on Java 25. SourbyMods are server-side only; Fabric and Forge mods do not load. Compatibility, AWF multi-profile work, and the older-plugin bridge are explicitly gated rather than presented as finished.
Each world region runs on its own tick thread. Paper remains the compatibility input; Aurora owns the execution model and the scheduler inside SourbyCraft.
One metrics runtime behind /tps, /mspt, and /perf, an /aurora operator hub, HUD bars, and a Spark bridge — built into the server instead of bolted on.
A native server-mod format for mods/*.jar with early-boot NMS and Bukkit access, a declared API version, and one classloader per mod.
The Paper API republished under the SourbyCraft namespace, with region-threaded scheduling and a read-only metrics contract for plugins.
Aurora is not a thin patch bundle. The compatibility bridge for older plugins is opt-in and still being qualified; the core runtime is the product.
Signed builds, staged release gates, and a first-boot library bootstrap. A build is not called stable until the release gates say so.
Tell us what you are running and where it hurts. We will route the brief to the right system.
Start a brief