The tick belongs to the region.
A Minecraft runtime built on Paper, without inheriting its execution model. Aurora gives every region an owner thread, one scheduler, and instrumentation that reports the same number everywhere.
Aurora Nexus is ready to run.
Signed jar · SHA-256 · manifest · SBOM
Paper compatibility, with an execution model of its own.
SourbyCraft keeps the server contract operators already know and replaces the parts that cannot survive region threading. The differences are documented, labelled, and kept behind an explicit boundary.
Region-threaded ticking
Each world region runs on its own tick thread. Aurora owns the execution model; Paper is the compatibility input, not the ceiling.
Operator instrumentation
One metrics runtime feeds /tps, /mspt, /perf, HUD bars, /aurora, and Spark. The number on the command is the number on the HUD.
SourbyMods
A native server-side mod loader with early-boot NMS and Bukkit access, a declared API generation, and one classloader per mod.
sourbyapi
The Paper API republished under the SourbyCraft group id, with first-party region API additions in dev.iyanz.sourbycraft.api.
A release with a boundary
Signed builds, staged gates, and explicit “not STABLE” labels. A feature is not called qualified because it compiled.
Compatibility is opt-in
The bridge for non-region-aware plugins is off by default and still being qualified. The core runtime does not pretend otherwise.
Every number on the command is the number on the HUD.
Observability is one runtime, not four dashboards. Commands, HUD bars, profiles, and stall traces read the same samples, with durations measured in nanoseconds and printed in real time.
- Commands
/tps,/mspt,/perf,/aurora, and/sparkdescribe one scheduler.- Stalls
- The stall recorder captures the tick, region, owner thread, and the work that overran before the watchdog acts.
- Boundary
- Metrics reflect the region model. A global TPS number is not invented to hide a per-region problem.
> tps
regions 20.0 / 20.0 / 20.0
> mspt
p50 1.8 ms p95 4.1 ms max 12.6 ms
> perf start 30s
sampling…
> perf stop
region A owner region-thread-a
region B owner region-thread-b
> aurora status
engine Aurora
policy EDF
bridge offA mod surface, not a plugin guess.
SourbyMods is a native server-side loader with a declared API generation and early access to NMS. sourbyapi republishes the Paper API under the project’s group id, with first-party region API additions. Neither promises that a Fabric or Forge mod will run.
- ML1
- A manifest, one classloader per mod, and explicit lifecycle events instead of implicit classpath luck.
- sourbyapi
- Region-aware scheduling and a read-only metrics contract in
dev.iyanz.sourbycraft. - Compatibility
- The bridge for non-region-aware plugins is opt-in, still being qualified, and does not change the core contract.
id: example-mod
name: Example Mod
version: 1.0.0
main: com.example.ExampleMod
api: 1Read before you run.
The documentation is written for the release you can download, not for an aspirational branch. Where a feature is gated, partial, or opt-in, the page says so.
Install
Requirements, checksum verification, first boot, and Docker.
OpenAurora Engine
The execution model: regions, EDF scheduling, ownership.
OpenRegions
Thread ownership, cross-region calls, and the compatibility bridge.
OpenObservability
One metrics runtime for commands, HUD, profiles, and stalls.
OpenSourbyMods
Native server mods with early NMS access and one classloader each.
OpenOperations
Commands, logs, updater modes, shutdown, Docker, and backups.
OpenRun the release. Read the boundary.
Build 48.4 is published and signed, but it is not labelled STABLE. That label is reserved for Build 49 after its gates close.