Start and stop
Use Record BuildXD.sh to start recording when a world finishes loading, or press F6 in an open world. The pause-menu recording button and /record start are alternatives. Press F6 again or use /record stop to finish. Returning to the title, switching worlds and a normal game exit also finalize the session.
/record status shows duration, storage, images and lost-data counters. /record goal Build a safe home marks an intention. /record note I turned back because my pickaxe broke adds your explanation at that moment. Notes are optional; ordinary play is enough to collect a useful debugging record.
The REC indicator remains visible even with the ordinary HUD hidden. Recording does not pause the world or stop the companion.
What it saves
Sessions live under data/recordings/session-…/, or the recordings directory inside your chosen data root. They include game images, input and simulation events, inventory/vitals observations, submitted in-game text/commands and notes, initial/final world snapshots and quality statistics.
This records the game, not your desktop or microphone. Visible in-game chat appears in images and submitted chat is recorded as an event. There is no automatic upload and no automatic model-training job.
Images are sampled up to ten per second, at most 640 pixels wide; structured observations are sampled up to twenty per second. Minimized play can retain structured capture without normal rendered frames. Busy capture workers may skip images and count the misses. The per-session storage cap is 4 GiB.
Review it locally
From the game folder run:
python3 tools/review_recording.py data/recordings/session-…
Replace the final directory with the actual session folder. The tool writes an offline review.html timeline and review.json quality report. Add --export to create examples.jsonl, pairing images with preceding observations and following controls.
Keep unfinished/crashed sessions marked as partial. Future outcomes and privileged hidden scene labels are not the same thing as what a player could see. A recording is a sampled demonstration, not a deterministic replay or proof that an assistant learned a new skill.
Recordings are separate from world saves and can be backed up independently. Inspect visible text before sharing a recording publicly.