? Virtual Chests
Virtual Chests 是一款轻量且功能强大的 Paper 插件,赋予服务器管理员对谁可以访问私人虚拟箱子的完全控制权。
无需在世界中放置物理箱子,玩家可以将物品安全地存储在仅他们自己能访问的虚拟箱子中。管理员通过权限来控制访问权限,使该系统既灵活又安全。
✨ 特性
- ? 基于权限的访问控制 – 轻松授予或限制箱子访问权限。
- ? 私有虚拟存储 – 无需物理箱子,物品免受恶意破坏者的侵害。
- ?️ 可配置 – 轻松管理玩家可访问的虚拟箱子数量。
- ? 无缝集成 – 与现有的权限插件(LuckPerms、PermissionsEx 等)兼容。
- ? 历史与恢复系统 – 查看过去的箱子状态,预览快照,并即时恢复旧版本。
? 使用场景
- 为捐赠者提供额外的存储空间作为奖励。
- 将解锁更多箱子作为成就奖励。
- 在不依赖领地插件的情况下保护物品栏。
⚙️ 使用方法
? 权限
使用简单的权限控制对虚拟箱子的访问:
virtualchests.use → 使用基础命令所必需。
virtualchests.open.X → 授予访问编号为 X 的箱子权限(例如 virtualchests.open.1)。
virtualchests.multiple.3 → 授予访问箱子 1–3 的权限。
virtualchests.multiple.5 → 授予访问箱子 1–5 的权限。
virtualchests.multiple.10 → 授予访问箱子 1–10 的权限。
virtualchests.admin → 允许管理员打开其他玩家的虚拟箱子。
virtualchests.update → 加入服务器时获取更新通知
? 示例:如果你希望玩家拥有五个私人箱子,只需给他们分配 virtualchests.multiple.5 权限即可。
? 命令
/chest → 列出所有命令
/chest <number> → 打开指定编号的自己的虚拟箱子。
/chest <number> <player> → (仅限管理员) 打开另一名玩家的虚拟箱子。
/chest <number> <player> history → (仅限管理员) 显示指定玩家虚拟箱子的历史记录。
/chest <number> <player> history -page <page> → (仅限管理员) 显示箱子历史记录日志的特定页面。
/chest <number> <player> history <id> view → (仅限管理员) 打开历史箱子快照的预览。
/chest <number> <player> history <id> restore → (仅限管理员) 将箱子恢复到所选的历史快照。
/chest transfer <player_from> <player_to> → (仅限管理员) 转移所有箱子。
/chest transfer <player_from> <player_to> <number> → (仅限管理员) 转移单个箱子。
/chest transfer <player_from> <player_to> <number> <number_dest> → (仅限管理员) 将单个箱子转移到不同的目标编号。
? 注意: 基础命令 /chest 可以在 config.yml 中重命名。
⚙️ 可配置选项
Virtual Chests 提供了一个灵活的 config.yml,以便你根据服务器需求调整插件:
- 选择你的存储类型:SQLite(默认)或 MySQL。
- 设置每个箱子的行数(1–6)。
- 更改基础命令名称以匹配你的服务器风格。
- 自定义消息和箱子名称以适应你的语言或格式偏好。
- 完全自定义所有与历史相关的消息、分页按钮和日期格式。
- 使用以下选项控制存储的历史记录量:
keep_last: 每个箱子保留的历史条目数量(设为 -1 以保留所有记录)。
history_page_size: 在历史命令中每页显示的条目数量。
? 提示: 配置文件易于编辑,有助于你为社区量身定制插件体验。
? Virtual Chests
Virtual Chests is a lightweight and powerful Paper plugin that gives server admins full control over who can access private, virtual chests.
Instead of cluttering the world with physical chests, players can securely store their items in virtual chests that only they can access. Admins control access through permissions, making this system both flexible and safe.
✨ Features
- ? Permission-based access – Grant or restrict chest access with ease.
- ? Private virtual storage – No physical chest needed, items are safe from griefers.
- ?️ Configurable – Easily manage how many virtual chests players can access.
- ? Seamless integration – Works with existing permission plugins (LuckPerms, PermissionsEx, etc.).
- ? History & restore system – View past chest states, preview snapshots, and restore older versions instantly.
? Use Cases
- Reward donators with extra storage.
- Unlock additional chests as achievement rewards.
- Protect inventories without relying on claim plugins.
⚙️ Usage
? Permissions
Control access to virtual chests using simple permissions:
virtualchests.use → Required to use the base command.
virtualchests.open.X → Grants access to chest number X (e.g., virtualchests.open.1).
virtualchests.multiple.3 → Grants access to chests 1–3.
virtualchests.multiple.5 → Grants access to chests 1–5.
virtualchests.multiple.10 → Grants access to chests 1–10.
virtualchests.admin → Allows admins to open other player's virtual chests.
virtualchests.update → Get update notification on join
? Example: If you want players to have five private chests, simply give them virtualchests.multiple.5.
? Commands
/chest → Lists all commands
/chest <number> → Opens your own virtual chest with the given number.
/chest <number> <player> → (Admin only) Opens another player’s virtual chest.
/chest <number> <player> history → (Admin only) Shows the history for the specified player’s virtual chest.
/chest <number> <player> history -page <page> → (Admin only) Displays a specific page of the chest’s history log.
/chest <number> <player> history <id> view → (Admin only) Opens a preview of the historical chest snapshot.
/chest <number> <player> history <id> restore → (Admin only) Restores the chest to the chosen historical snapshot.
/chest transfer <player_from> <player_to> → (Admin only) Transfer all Chests.
/chest transfer <player_from> <player_to> <number> → (Admin only) Transfer single Chest.
/chest transfer <player_from> <player_to> <number> <number_dest> → (Admin only) Transfer single Chest with different destination.
? Note: The base command /chest can be renamed in the config.yml.
⚙️ Configurable Options
Virtual Chests comes with a flexible config.yml so you can adapt the plugin to your server:
- Choose your storage type: SQLite (default) or MySQL.
- Set the number of rows per chest (1–6).
- Rename the base command to match your server style.
- Customize messages and chest names to fit your language or formatting preferences.
- Fully customize all history-related messages, pagination buttons, and date formatting.
- Control how much history is stored using:
keep_last: Number of history entries to keep per chest (-1 to keep all).
history_page_size: Number of entries shown per page in the history command.
? Tip: The configuration is easy to edit and helps you tailor the plugin for your community.
评论 0
登录后参与评分
还没有评论,来抢沙发吧