A server admin toolkit for Sable and Create Aeronautics. Find lag-causing airships, freeze runaways, undo accidental griefing, and stop guessing which contraption was on the server when it crashed.
NeoForge 1.21.1 only. Server-only install. No client mod required.
"Shtreimel" is the fur hat worn over a sable lining. It's a hat that goes on top of Sable. The name is a joke; the mod is not.
You run a Sable or Create Aeronautics server. Eventually one of these happens:
/stop./sable remove on the wrong contraption and you have nothing to roll back to.Shtreimel gives you commands for every one of those.
When a dimension's physics gets hot, Shtreimel picks the most-likely-suspect contraption and prints one line in the server console with its position, owner-given name, UUID, and bounding box.
Example console line:
[shtreimel.lag] lag suspect dim=minecraft:overworld ewma=7.43ms max60=18.20ms uuid=8a1f... name="Big Blimp" plot=(10005,10003) center=(124.0,72.5,-88.3) bb=24x10x32 suspect=83
If your server is heavier or lighter than typical, run /shtreimel lag autotune after a few hours of normal play and it prints recommended thresholds for the config.
You can also pull a live ranking on demand:
/shtreimel rank/shtreimel physics-stats/shtreimel list/shtreimel freeze <uuid>/shtreimel freeze nearest/shtreimel unfreeze <uuid>freeze pins a contraption in place without pausing physics for the whole dimension. The pin sticks across server restarts.
/shtreimel delete uuid <uuid> --confirm/shtreimel delete at <x> <y> <z> --confirm/shtreimel delete nearest --confirmdelete runs Sable's own removal path. Same cleanup as /sable remove.
/shtreimel archive save <uuid>/shtreimel archive list/shtreimel archive restore <uuid> <archiveId>archive save writes the contraption's full block data to disk. restore brings it back, optionally with the same UUID. Per-contraption undo.
/shtreimel info <uuid>
Pose, bounding box, mass, center of mass, reaction wheels, queued forces, network drift, who's currently inside it, who's tracking it, lag-score breakdown. In-game, the header has clickable [teleport], [freeze], [archive] buttons.
/shtreimel at <x> <y> <z>/shtreimel in <fromPos> <toPos>/shtreimel near/shtreimel who <uuid>/shtreimel watch <uuid>at says which contraption is at a block position. in lists every contraption in a region. near lists what's around the calling player. who says which players are inside a contraption right now. watch subscribes a staff member to live pose updates for a contraption for N seconds (great for following an airship live).
/shtreimel tp <uuid>/shtreimel tp player <playerName> <uuid>/shtreimel tp backTeleports to the top of the contraption's bounding box. tp back returns you to where you were.
/shtreimel audit tail/shtreimel audit since 1h/shtreimel audit by Steve/shtreimel audit uuid <uuid>Every destructive command (delete, freeze, archive save) writes a single line to <world>/shtreimel/audit.log. Query it from in-game.
When Sable's physics tick crashes, Shtreimel adds a block to the crash report listing every loaded contraption (UUID, name, position, bounding box) and per-dimension physics timing.
With no permissions mod installed, Shtreimel uses vanilla op levels:
delete, freeze, archive save / restore / prune).--confirm token. Server console and RCON are op 4.If you run a permissions mod (LuckPerms, FTB Ranks, etc.), the named nodes are:
shtreimel.observeshtreimel.deleteshtreimel.delete.confirm_bypassshtreimel.audit.readmods/.shtreimel-neoforge-1.21.1-<version>.jar from the Files page into the same mods/ folder.<world>/serverconfig/shtreimel-server.toml and reloads when you edit the file.That's it. Nothing to install on your players' clients.
| Component | Required version |
|---|---|
| Minecraft | 1.21.1 |
| NeoForge | 21.1.219 or newer |
| Java | 21 |
| Sable | 1.2.1 or newer (required) |
| Sable Companion | bundled with Sable, no separate install |
| Create | optional |
| Create Aeronautics | optional |
The "lag suspect" picker is a heuristic. Sable advances physics in a fused tick and doesn't expose per-contraption timing through any stable API, so Shtreimel cannot tell you "this contraption used 4ms of Rapier physics time last tick." It ranks by cheap proxies that usually correlate with cost: size, footprint, loaded chunks, block-entity count, speed, network drift, reaction wheels, queued forces, intersecting entities. Treat a high suspect score as somewhere to start looking, not as a verdict.
MIT. Bundled LICENSE file in the jar.