Menu access and Discord logs

The server owner controls access from /rz → Access. Access is saved for the player's account/license, not a temporary server ID or a single character.

The ? buttons and hover hints explain the controls, using the same help and switches as the script settings.

Grant access

1. Select an online player.
2. Enable All scripts, including future scripts, or open Choose scripts and enable individual scripts. Search by display name or resource name; the counter shows how many are selected. Searching preserves your choices.
3. Leave Can manage access off unless this person should grant, edit and revoke other people's access.
4. Click Grant access. The player can open /rz.

Selecting specific scripts grants only those scripts. Installing another RZ script does not automatically add it. Selecting all scripts includes scripts installed later.

Access to a script allows changing its menu settings. This is not a read-only viewer. It does not grant ownership, data cleanup or permission to change the Discord destination. The owner and owner ACE remain unrestricted.

Edit or revoke

Under People with access, expand Edit permissions, change the selection and click Save permissions. Revoke access requires a second click to confirm.

The open menu refreshes when permissions change. If no access remains, it closes. The server checks permissions again on every save; hiding a script is not the only protection.

Access managers can delegate only permissions they already have. They cannot edit their own access, change the owner, or modify another account whose access is broader than theirs. Existing administrators from the previous full-access system keep their permissions until the owner edits or revokes them.

Editing with another administrator

When one administrator saves a script, other open menus with access to that script receive its updated settings. This is event-driven, only for open authorized menus; it does not broadcast to every player or poll continuously. Unchanged fields reuse the existing menu data, and large changes use the latent transfer path.

If you have unsaved changes, they stay in your form and saving is paused. Choose Use saved settings to discard your draft, or Keep my changes to retain the fields you edited on top of the latest saved settings. Review those fields before saving: this choice can overwrite another administrator's edits to them. For lists, the edited field is the whole list.

The server allows one configuration write at a time per product and checks the menu revision. A simultaneous or stale save is rejected instead of silently replacing the first save. Database changes use a transaction. Test this with both menus open, including a save while the other person has unsaved edits.

Discord administration logs

Only the owner sees this box in Access. It is disabled by default and shared across the installation.

1. Select Default channel and access logs under Log destination.
2. Enter a Discord webhook URL, enable Enable administration logs, then click Save log settings.
3. To route a script separately, select it in Log destination (search by name or resource name). Choose Use default channel, Use a different channel, or Do not log this script, then save.

The default channel receives access changes and administrative changes for scripts using the default. A custom script channel receives that script's configuration and cleanup logs. The global enable switch controls every administration channel, including custom ones. You can also leave the default URL empty and configure only custom script channels; access logs then have no destination.

Saved URLs stay on the server and are never sent back to the menu. Leave a URL field blank to retain its saved value. Remove webhook requires confirmation: for the default channel it clears its URL and disables all administration logging; for a script it clears that script's URL and returns it to the default channel. Cancel keeps the saved webhook unchanged. Existing Discord messages are kept.

Logs include:

• The actor's player name, server ID and account/license.
• Successfully saved configuration changes: script, menu section/plant, setting label and before/after values. Boolean values and choices use readable names instead of internal keys or hashes.
• Granted, edited and revoked access, including the previous and new permissions.
• Successful data cleanup and configuration resets.

Each message starts with the script name and resource name, followed by the action, details and a separate Actor field. Platform-wide access changes use RZ Platform as their heading. Administration messages use the acting person's panel language, independently of the script's gameplay language.

For example: RZ Herbs · rz_herbs → Configuration saved → Base settings › Script active: Enabled → Disabled.

Secret fields and URLs are hidden. Large tables such as spawn groups are summarized by record/position counts, not thousands of coordinates. A batch save creates one summary, showing up to 20 changed settings and a count for the remainder.

These are administration logs. Gameplay collection/eating logs remain configured in the individual script and use its configured gameplay language. Herbs messages show the script, collection/consumption action, plant name, result and player details.

Discord delivery runs separately from the saved change. A Discord failure does not undo a save or freeze the menu. Delivery is best effort: the queue is bounded and is not a permanent history or an automatic retry system.

Two-player test

1. As owner A, edit B's access to only Herbs and turn Can manage access off.
2. As B, open /rz: Herbs should be available; other scripts, Access and Data cleanup should not be available.
3. As B, save a reversible Herbs setting. A should see the saved value.
4. As A, grant all scripts, then reduce B back to Herbs while B keeps the menu open. Check the list refreshes.
5. Enable access management for B and verify B can only delegate scripts B can configure.
6. Revoke B's access while B has the menu open. It should close, and reopening should show access denied.
7. Configure a test Discord destination and save one ordinary setting. Check the actor, script, translated menu labels and before/after values. Set a different channel for Herbs and verify its configuration logs go there while access changes still use the default channel. Test a secret field: its value must be hidden.

Restart the updated resources after installing the new version. The SDK creates the added database fields automatically; existing owner claims, settings and delegates are preserved.