VoidVault 0.2.1

🔐 New Permission: voidvault.ui

Server owners can now grant or deny access to vault commands independently from the base voidvault.use permission.

The new voidvault.ui permission controls:

• /vv and /voidvault (opening Vault 1)
• /vv <number> (opening a specific vault)
• /vv ui and /voidvault ui (opening the multi-vault selector)

Existing behavior is preserved for other commands:

• /vv rename — still controlled by voidvault.use
• /voidvault reload — still controlled by voidvault.admin.reload
• /voidvault open — still controlled by voidvault.admin
• /voidvault import enderchest — still controlled by voidvault.admin.import

⚡ Automatic Permission Registration

All VoidVault permissions are now automatically registered with the Hytale permission system on plugin startup and config reload.

Permissions appear in LuckPerms and other permission managers without requiring manual commands.

Registered permissions:

• voidvault.use
• voidvault.ui
• voidvault.admin
• voidvault.admin.reload
• voidvault.admin.import
• all slot tier permissions (voidvault.slots.*)
• all vault tier permissions (voidvault.vaults.*)
• legacy enderchests.* permissions

🧹 Clean Permission Prefix

The plugin group has been updated from tblack.voidvault to voidvault, removing the tblack. prefix from all auto-generated permission nodes.

🌍 Localization

Added translated messages for the new no_permission.ui error in all supported languages:

• English (en-US)
• Portuguese (pt-BR)
• Russian (ru-RU)
• Simplified Chinese (zh-CN)
• Ukrainian (uk-UA)

📦 Config Changes

A new uiPermission field has been added to the commands section of the config. The config file is updated automatically on first load — no manual editing required.

💎 Summary

VoidVault 0.2.1 gives server owners fine-grained control over vault access while keeping full compatibility with existing setups and permission configurations.

More control. Cleaner permissions. Ready out of the box.