> 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/administration.md). # Menus, profiles and subzones ## Arena menu Open `/rz menu ` while in game. The menu uses restrained gold and gray text, short small-cap headings and ordinary inventory items. It is a focused settings panel, not a second copy of every advanced command. Available controls: * Cycle through the four regeneration modes. * Enable or pause automatic scheduling. * Increase the base individual delay by one second with left-click, or decrease it with right-click. * Toggle restoration of original air. * Toggle direct player-break item drops. * Cycle chat, action-bar and disabled announcements. * Toggle floor protection. * Read current processing status and pending count. Editing requires `regenzone.configure` as well as menu access. The menu executes the same validated setting commands used in chat. It does not bypass busy-state rules. Inventory clicks and drags are cancelled within the menu interaction so its display items cannot be taken or replaced. Advanced settings, including category delays, material mappings, profiles, subzones and custom messages, use commands or configuration files. ## Profiles Profiles store a complete set of arena rules in `plugins/RegenZone/profiles/.yml`. They do not contain bounds, world UUID, blocks, pending jobs or subzones. ``` /rz profile save practice fast-build /rz profile list /rz profile apply training fast-build confirmar ``` Use `confirmar` when replacing an existing profile: ``` /rz profile save practice fast-build confirmar ``` Applying a profile replaces the destination arena's settings and resets its interval schedule. Existing pending individual deadlines remain unchanged. Existing subzones retain their own copied rules; profile application does not update them. Profiles are snapshots of settings, not live links. Editing the source arena later does not change saved profiles or arenas that previously used them. ## Subzones A subzone is a non-overlapping cuboid inside one arena. It shares the parent's snapshot and scheduling mode, while overriding supported local rules. It does not create an independent timer engine or another arena snapshot. 1. Select a smaller cuboid entirely inside an existing arena. 2. Pause or wait for the parent arena if it is busy. 3. Create the subzone: ``` /rz subzone practice create floor ``` 4. Configure local behavior: ``` /rz subzone practice set floor break-delay-seconds 3 /rz subzone practice set floor place-delay-seconds 15 /rz subzone practice set floor drop-items false /rz subzone practice set floor protect-player-floor true ``` For protected decoration: ``` /rz subzone practice create decoration /rz subzone practice set decoration protect-when-idle true ``` Supported local keys: ``` protect-when-idle drop-items drop-experience restore-air protect-player-floor track-placements track-explosions track-natural-changes block-delay-seconds break-delay-seconds place-delay-seconds include-materials exclude-materials ``` The parent mode, interval, inactivity period, empty-arena waiting, chunk-loading behavior, outer boundary protection and announcements remain shared. Individual local delays matter when the parent's mode uses individual deadlines. Subzones copy the parent's settings when created. They do not dynamically inherit later parent changes. Material-delay mappings are copied too; editing those mappings for a subzone requires stopping the server and editing its `settings.material-delays` section in the arena YAML. The in-game `material` command edits the parent arena mapping. Subzones may touch at adjacent block faces but may not share blocks. They must lie entirely inside the parent region. A maximum of 64 subzones per arena prevents unbounded per-event lookups. Use separate arenas when you need completely independent modes and schedules. ``` /rz subzone practice list /rz subzone practice delete decoration confirmar ``` Deleting a subzone removes its local settings only. It does not alter world blocks or the parent's snapshot. The parent rules apply to those positions afterward. --- # 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/administration.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.