> For the complete documentation index, see [llms.txt](https://matt-creppet.gitbook.io/matt-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://matt-creppet.gitbook.io/matt-docs/storage.md). # Storage, updates and recovery ## Files ``` plugins/RegenZone/ config.yml profiles/ fast-build.yml arenas/ practice.yml practice.rzs practice.rzs.bak practice.rzs.pending session.active archived/ ``` `practice.yml` holds bounds, world UUID, arena settings and subzones. `practice.rzs` is the compressed baseline snapshot. `.bak` contains the previous known-good capture. `.pending` contains tracked positions and absolute deadlines. `session.active` helps detect an incomplete shutdown. Snapshot files use a palette plus block indices. They are not editable schematic files and are not WorldEdit schematics. ## Normal restart On clean shutdown, pending positions and deadlines are saved. A clean startup can restore them without scanning the entire area. Absolute deadlines can expire while the server is offline; eligible work runs after startup subject to loading, waiting and safety rules. Full interval schedules restart from a fresh interval after loading. Inactivity starts from a fresh quiet period. This release does not persist an exact match clock or automatic-interval countdown across restarts. ## Incomplete shutdown If the session marker remains, pending metadata is missing or invalid, a snapshot changed, or a job was interrupted, selective modes first perform a read-only audit in bounded batches. The audit discovers differences without restoring the world or locking the entire arena. Differences recovered without a known deadline receive the base `block-delay-seconds` from detection time. The original event category and material-delay decision are not available after an unrecorded crash. A crash audit can discover changes from causes that were not normally tracked; filters still apply before restoration. The plugin allows a bounded wait for disk work during shutdown. A forced process termination can interrupt that work; the next startup uses recovery checks rather than assuming everything was saved. ## Replace or recover a snapshot ``` /rz guardar practice confirmar ``` This captures the current region and replaces the baseline. The previous readable snapshot is written to `.bak` first. ``` /rz recuperar practice confirmar ``` This restores the backup snapshot file. It does not immediately write blocks into the world. Use `/rz regen practice` afterward when you want to apply it. One previous capture is retained, not an unlimited history. Keep external backups of the data folder and world if you need longer retention. ## Cancel, retry and archive Cancellation stops queued work but does not reverse completed block changes. Cancelling without disabling automation may allow pending work to be scheduled again. `/rz reintentar practice` clears an operation error and requests a full restoration when a readable snapshot exists in memory. It does not fix damaged files or make missing materials valid. Correct those causes first. `/rz borrar practice confirmar` copies available arena files into `arenas/archived/` and unregisters the arena. It does not remove the arena's world blocks. Archived data can be recovered manually with the server stopped. A snapshot file may remain at its former path; the missing active YAML prevents it from being registered as an arena. ## Manual editing Do not change an arena's bounds in YAML while keeping an incompatible snapshot. The loader checks that the saved region and YAML region agree. Create another arena for a different region. Stop the server before editing arena files, subzone mappings or pending storage. Never remove `session.active` after an abnormal shutdown simply to suppress the audit; doing so can hide changes that were not saved. When upgrading from 0.1.0 or 0.2.0, existing snapshots remain readable. New keys use fallback defaults. Notably, 0.3.0 defaults direct player-break item and experience drops to `false`; set them explicitly to `true` if your arena should retain normal drops. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://matt-creppet.gitbook.io/matt-docs/storage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.