Repository navigation
SF_MagicExpansion 1.1.15
MagicExpansion 1.1.15 — automatic Slimefun Tick Monitor sampling
This maintenance release repairs the SF Timings Machine / Slimefun Tick Monitor that could remain at Tick:0ms and currentTick:0ms until an operator manually ran /sf tick top.
Tick Monitor repair
- A loaded Tick Monitor now requests a detailed Slimefun profiler sample automatically instead of only reading whatever old detailed sample happens to exist.
- All placed monitors share one coordinator. At most one profiler request is outstanding, and a new automatic sample is requested no more often than once every ten seconds after the previous request completes or fails.
- Multiple monitors in the same world/chunk share one chunk timing lookup per completed sample.
- Missing data displays
Waiting for sample; failed or overdue sampling displaysSample unavailable; old cached results are explicitly marked stale. A genuine measured0msremains a valid measurement. - Hologram and menu labels are clarified to
Slimefun totalandThis chunk, with sample age shown in the menu. These values are sampled Slimefun processing durations, not server TPS or MSPT. - The existing item ID, recipe, storage, energy behavior, hologram positions and break/place cleanup remain unchanged.
Scope
This change does not alter Black Market trades, receipts, fishing, item/research IDs, recipes, stored machine data or configuration defaults. It does not reset existing Tick Monitor blocks.
The monitor deliberately uses Slimefun's existing detailed profiler request path rather than installing another repeating server task. If the Slimefun ticker is paused, the monitor also stops updating.
Validation
The candidate includes regression coverage for first-use sampling, shared requests, chunk deduplication, cooldowns, unanswered requests, timeout recovery, stale data, genuine zero timings, inactive chunk pruning, partial-read failure and the actual Slimefun PerformanceSummary delivery protocol.
Release promotion requires the versioned candidate to pass the repository unit suite, Paper/Purpur API checks and published-core full-stack gates. A live server acceptance check is still recommended because automated CI cannot prove hologram rendering, every historical world state, arbitrary third-party interaction or Folia region-thread behavior.
Upgrade
Stop the server normally and back up the server/plugins data before replacing the JAR. Install only one MagicExpansion JAR and start normally; do not use /reload. Existing Tick Monitor blocks should begin requesting their own sample after ticking, without needing /sf tick top.