RZ menu guide

The shared /rz menu manages installed RZ scripts that include it. You do not need to install a separate menu resource. Each script keeps its own settings; two scripts using the same field name do not share that value.

One menu for your compatible scripts

Install and start an RZ product that supports the menu: it appears directly in the script list. Learn the panel once and use it for future compatible products too. Each product guide explains its own settings and links to this manual for the shared tools.

Your path: First access → Find your script → Save → Grant access → Discord logs.

First access

Run /rz in game. If no owner is configured, the setup popup shows the console claim command with your current server ID. Run that command in the server/txAdmin console, then reopen /rz.

rz owner claim <player-server-id>

Replace the placeholder with the real ID; it is not always 1. This claims the owner's account/license, not only that connection or character.

Alternatively, a server administrator can configure the owner ACE:

add_ace group.rz_owner rz.owner allow
add_principal identifier.license:YOUR_LICENSE group.rz_owner

Use the actual license identifier. ACE takes precedence over the command-based owner. If an owner already exists and another player has no permission, that player sees access denied, not the first-owner setup.

First access — Show the owner setup popup and where its console command appears.

Find your script

The menu opens on Home, with no product selected. Installed scripts are listed on the left; select one to open its configuration. Use the script tabs for its main categories and the searchable group selector for long lists such as plants.

Hover hints explain individual controls. A ? button opens longer help where the author supplied it. The quick index jumps to settings within the current page. The assistance link opens the support report; use it together with actual console errors.

Navigation and help — Show the installed scripts list, product tabs, a help button and the quick index.

Change and save settings

• Change fields and click Save all to apply them together. Invalid values prevent the whole batch from saving; fix the highlighted setting and retry.
• Discard changes removes your unsaved draft for this script.
• Restore default prepares the default value; save to apply it.
• For global/custom fields, Use global follows the script's global value. Custom values are exceptions. Use global for all changes that setting for every item after saving.
• Adding an item or plant choice to an editor is separate from saving the entire configuration. Confirm the row, then save the script.
• Position capture records a draft location. A “not saved” marker means teleporting there does not persist it.

Save all applies changes to the running script and keeps your settings for future starts. Ordinary menu changes do not require a server restart.

Two administrators at once

When one person saves, other authorized open menus receive the changed product. Closed menus do not receive these UI updates.

If you have unsaved changes, they remain visible and saving pauses. Choose Use saved settings to discard your draft, or Keep my changes to keep your edited fields on top of the new server values. Review before saving: keeping a changed list can overwrite the other person's changes to that whole list.

If someone saves before you, the menu warns you: review the differences before confirming your change.

Shared editing conflict — Show the warning with Use saved settings and Keep my changes while a draft is still visible.

Language and appearance

The top language control changes your panel language, including script labels and help. It is saved for your account. A script's own language setting controls gameplay texts for players; changing it does not change your personal panel language.

The color control selects a background, accent palette or custom color. Opacity ranges from 70% to 100%, with 90% as the default. Appearance preferences are saved for your account.

Minimize hides the panel behind a small restore button without closing the session. It is for observing the game: menu mouse focus remains active. Restore it to return to the same editing session; close the menu when you want to resume normal gameplay controls.

Personal appearance — Show the language menu, color panel and opacity control. A separate image can show the minimized restore button.

Give other people access

1. As owner, open /rz → Access and select an online player.
2. Allow all scripts, including future ones, or select only the scripts this person should manage. Use search for long lists.
3. Leave access management disabled if they only need to configure scripts.
4. Click Grant access: the player can open /rz.

Access is saved for the account/license. It allows editing the granted scripts, not just viewing them, and does not grant ownership or data cleanup. Use the people-with-access list to save changed permissions or revoke access. Already open menus update too.

Granting access — Show a selected player, script search and the grant button. Hide real license identifiers.

Record changes on Discord

Administration logs are in Access, visible to the owner. You do not need to repeat the setup inside every script.

1. Prepare a webhook in the Discord channel that should receive the logs.
2. Select the default destination and paste its URL into the administration logs box.
3. Enable administration logs and click Save log settings.
4. To use another channel for a script, select that script as the destination, choose a different channel, enter its webhook and save. You can also exclude the script from logging.

The default channel receives access changes and changes for scripts using it. Dedicated channels receive the selected script's changes. The global switch controls all administration logging.

Saved URLs are not displayed: a blank field does not mean the webhook was deleted. Leaving it blank preserves the URL; use Remove webhook and confirm to delete it. Messages use the acting person's panel language, the script name and readable setting labels.

Gameplay logs, such as Herbs collection and eating, are separate and configured in the product. More about permissions, destinations and removal →

Log destinations — Show the default channel, script selector and logging switch. Never show a webhook URL.

A recorded change — Show a Discord message with script name, action and before/after values. Blur personal identifiers.

Updates

Script updates appear under Updates and in the console when the resource starts. The menu displays installed and published versions and the available changelog. Opening /rz checks for new release information without requiring a full server restart. An unavailable check is not proof that the installed version is current.

Updates are installed manually by downloading the complete package. Keep the original folder name, saved database settings and reviewed public customizations. A known mandatory update can prevent gameplay for the affected product.

Updates — Show an actual update notice and readable changelog. Use real version numbers from the test package.

Data cleanup

This owner-only area resets saved settings or removes stored data for a selected product. Read the action and confirmation carefully and back up important configuration first. A reset returns settings to the defaults supplied by that version of the product; gameplay follows the product's configuration-change handling.

Data cleanup is not an update step. Do not delete shared rz_platform_* tables manually to remove one script: they also hold owner, access and other product information.

Data cleanup confirmation — Show the selected product, the action and its confirmation before execution.