Watching a Replay ¶

Sometimes a building falls and you miss how it happened. The replay viewer lets you watch it again, in the world, as slowly as you like.

It rebuilds the building in an empty area, then plays the collapse back: the blast, the cracks, and every block that fell afterwards.

Prefer buttons over typing?

You can do all of this with in-game buttons — no commands needed. Just type /replay to open the match list and click. See Reviewing Your Match. The commands below still work as shortcuts.

Start watching¶

See what recordings exist: /replay list
Load one: /replay load <file> (use a name from the list)
Press play: /replay play

The building appears, then starts to fall apart just like it did the first time.

Loading a big recording takes a moment. You will see Loading… first, then the replay appears. The server keeps running smoothly while it loads.

Reached the end and want to see it again? Just press /replay play — it rewinds and starts over from the beginning.

Several people can watch their own replays at the same time. Each one is built in its own spot, so they never overwrite each other.

Controls¶

/replay play — start (or resume) the replay. Press it again after the replay ends to watch the whole thing over from the start.
/replay pause — freeze it where it is.
/replay speed 0.5 — go in slow-mo. Try 0.25 for very slow, or 4 to speed up.
/replay step +1 — move forward one tiny moment. Use -1 to step back.
/replay seek 01:30 — jump to a time (one minute, thirty seconds).
/replay seek @3 — jump to the third big event (like the third explosion).
/replay exit — close the replay and clear the stage.

A bar at the top shows how far through you are and what is happening right now.

When you close a replay (or step back in time), the viewer cleans up every block it put down — even blocks that were placed during the collapse. Nothing is left stuck in the world.

Overlays¶

Overlays let you watch just one kind of thing:

/replay filter cascade on — show only the blocks that fell.
/replay filter cracks on — show only the blocks that got damaged.
/replay filter direct on — show only the blocks the blast blew up directly.

Turn one off again with off (for example /replay filter cracks off). You can have several on at once.

Looking closer¶

/replay stats — a quick summary: how many blocks were blown up, how many fell, and who did the most damage.
/replay export — save the match report (player stats + structure autopsy) as a .md and a .json file next to the recording, to share outside the game. (The 📊 stats window has a button for this too.)
Click a block in the replay to see its story — who placed it, how badly it cracked, and how it finally fell.

For server admins¶

The viewer only ever opens recordings inside your recordings folder. A name that tries to point somewhere else (like ../secrets.json or a full path) is refused — it can never read files outside that folder.

Each viewer gets their own stage area, so two people can watch replays in the same world at once without overwriting each other's blocks. The stages are spread out east by stage.lane-spacing blocks — set that bigger than your largest building so they never overlap. Set stage.world to keep every stage in one safe, empty world (otherwise a stage is built in whatever world the viewer is standing in, which can paste over live terrain).

Replays clean up after themselves. If a viewer logs off mid-replay, their replay closes and its stage is cleared. When you reload or disable the plugin, every open replay is closed too.

There are two permissions (both op by default):

struxreplay.use — load, list, see stats, and exit a replay.
struxreplay.driver — drive playback: play, pause, speed, step, seek, and filter.

So you can let a crowd watch one shared stage with only struxreplay.use, while the person with struxreplay.driver is the one steering the timeline.