TRB Core

Features

• One scheduler: one per-tick callback for every connected plugin, with a shared game-thread time budget per tick (0.5 ms by default). Long jobs are time-sliced, and the scheduler pauses during world saves.
• One background worker: connected plugins hand file writes and other heavy work to one shared thread instead of each running their own. Disk writes wait until a world save has finished.
• One clock calibration: Core measures the server's timers once, and connected plugins reuse that instead of each calibrating on load.
• Shared events: player death, login, logout and world-save events, with each game hook installed only while a plugin uses it.
• Per-plugin timing: trbcore perf shows the game-thread time each connected plugin uses.
• Fully optional: plugins detect Core at runtime, in any load order, and fall back to their own code when it is missing or unloaded.

Works with every TRB plugin

Every TRB plugin supports Core but never requires it. With Core loaded, plugins hand their timers, background work and disk writes to Core instead of each running their own threads, disk writes wait until world saves finish, and they share one clock calibration. Without Core, each plugin runs on its own exactly as before.

Commands

trbcore status	Scheduler, events, worker and connected plugins
trbcore perf	Game-thread time per plugin, clock and budget stats
trbcore events / jobs / commands	Subscriptions, scheduled jobs and routed commands
trbcore selftest	Built-in checks
trbcore bench / bench result / bench stop	Short time-sliced benchmark on your server
trbcore reload	Re-read config.json

Configuration

Admin-only, in chat /trbcore, console and RCON. The command name, tick budget, worker, clock and shared display settings are in config.json.