MuseumWorld
MuseumWorld 是一个轻量级的 Paper 插件,它将选定的世界转换为只读的“博物馆/展示”世界。
玩家可以自由探索,同时阻止破坏性操作、物品栏修改、实体伤害以及常见的交互漏洞利用。
它适用于:
- 大厅 / 出生点 / 枢纽世界
- 展示地图
- 博物馆建筑
- 只读冒险区域
- 希望访客仅探索而不进行编辑的世界
主要功能
✅ 只读世界
您可以通过 config.yml 选择受保护的世界。
在受保护的世界中,MuseumWorld 可以阻止以下行为:
- 破坏方块
- 放置方块
- 物品栏修改
- 实体伤害
- 盔甲架操作
- 物品展示框 / 画作的交互
- 受保护的容器修改
- 涉及受保护物品栏的漏斗/物品传输
- 爆炸对方块的破坏
- 丢弃物品
- 拾取物品
- 水桶填充/倒空操作
- 打火石 / 火焰弹的使用
- 引燃火源
- TNT 引燃
- 使用床
- 使用骨粉
- 创建下界传送门
- 自然生长、扩散和腐烂的变化
- 投射物的使用(可选启用鞘翅烟花助推例外)
- 拴绳的使用
- 命名牌的使用
- 车辆的放置与破坏
- 悬挂实体的破坏/移除
✅ 只读容器
MuseumWorld 允许玩家打开选定的容器并查看内部,同时阻止物品的移动。
例如,玩家可以打开:
- 箱子
- barrels (木桶)
- 潜影盒
- 熔炉
- 漏斗
- 发射器
- 投掷器
- 酿造台
- 讲台
- 信标
但他们不能:
- 取出物品
- 放入物品
- 按住 Shift 点击物品
- 将物品拖入容器
- 通过漏斗传输移动物品
✅ 严格基于配置的防护
MuseumWorld 旨在通过 config.yml 保持可预测性和可控性。
只读方块和只读实体 仅在它们被明确列出时 才会受到保护,即出现在以下配置中:
readonly-blocks:
readonly-entities:
系统不会自动检测只读方块或实体。
这意味着门、陷阱门和栅栏门等导航方块除非服务器所有者明确将它们添加到 readonly-blocks,否则不会被阻止。
例如,如果希望玩家在博物馆世界中能够打开门,只需不将这些门添加到 readonly-blocks 中即可。
如果某个特定的门需要锁定,请手动添加它:
readonly-blocks:
- OAK_DOOR
- IRON_DOOR
这使插件完全可配置,并避免意外的防护行为。
✅ 扩展防护开关
MuseumWorld 包含了针对常见反破坏和博物馆世界用例的其他防护选项。
示例:
block-item-drop: true
block-item-pickup: true
block-bucket-use: true
block-fire-use: true
block-natural-growth: false
block-bone-meal-use: true
block-portal-creation: true
block-item-frame-rotation: true
block-armor-stand-manipulation: true
block-tnt-ignite: true
block-player-bed-use: true
block-hanging-break: true
block-vehicle-place-break: true
block-projectile-use: true
block-lead-use: true
block-name-tag-use: true
这些选项允许服务器所有者精确决定每个受保护世界的严格程度。
✅ 鞘翅支持
可以在启用投射物阻挡的同时,仍允许鞘翅烟花助推。
block-projectile-use: true
allow-elytra-firework-boost: true
启用后,玩家在滑翔使用鞘翅时仍可使用烟花火箭。
这允许在受保护的世界中使用鞘翅飞行,同时阻止其他投射物类型的交互,如鸡蛋、末影珍珠、喷溅药水等类似操作。
✅ 配置验证与安全清理
MuseumWorld 可以在启动时验证所选的配置列表。
验证器检查:
readonly-blocks
view-only-containers
readonly-entities
blocked-entity-types
如果发现无效的 Material 或 EntityType 名称,当启用时,MuseumWorld 可以自动将其移除:
auto-clean-invalid-config-values: true
在清理之前,插件可以创建 config.yml 的备份。
验证报告保存在:
plugins/MuseumWorld/logs/
配置备份保存在:
plugins/MuseumWorld/backups/
验证器 不会 修改以下内容:
locked-worlds
language
✅ 自动配置更新
当新版本的插件引入新选项时,MuseumWorld 可以自动添加缺失的配置键。
现有值将被保留。
受保护的配置键,例如:
protected-config-keys:
- locked-worlds
- language
在配置更新期间不会被覆盖。
启用此选项后,MuseumWorld 还可以更新缺失的列表值:
update-lists-on-next-reload: true
列表更新完成后,该选项会自动恢复为:
update-lists-on-next-reload: false
在自动配置更新之前,如果启用,插件可以创建备份:
backup-config-before-auto-update: true
备份存储在:
plugins/MuseumWorld/backups/
✅ 基于模板的配置重写
MuseumWorld 使用捆绑的默认配置作为模板来重写 config.yml。
这意味着自动配置更新将保留:
- 官方注释
- 键的顺序
- 新添加的解释
- 现有的用户定义值
- 自定义列表条目
- 整洁且可预测的配置布局
捆绑的默认 config.yml 充当参考布局。
活动的服务器 config.yml 保留用户值,而缺失的键和注释将从默认模板中恢复。
config-version 始终作为文件底部的最后一个键保留。
✅ bStats 指标统计
MuseumWorld 使用匿名的 bStats 指标统计功能。
bStats 帮助追踪使用该插件的服务器数量以及常见的服务器/软件版本。它不收集私人玩家数据、聊天内容、世界名称或配置值。
✅ 更新检查器
MuseumWorld 可以在启动时检查 GitHub Releases 以获取新版本的插件。
update-checker-enabled: true
notify-admins-about-updates: true
更新检查器仅通知服务器所有者/管理员。它绝不会自动下载或安装更新。
命令
主命令:
/museum
可用的子命令:
/museum version
/museum list
/museum add <world>
/museum remove <world>
/museum reload
/museum status
/museum debug <on|off|status>
/museum lockcurrentworld
/museum unlockcurrentworld
命令概览
/museum version
显示公开的插件信息。此命令对所有玩家可用,不需要 museumworld.admin 权限。
示例输出:
MuseumWorld
Version: 1.1.0
Channel: STABLE
Target API: Paper 26.1.2
Author: Tantrum90MK
/museum list
显示所有已锁定/受保护的世界。
/museum add <world>
将世界添加到受保护世界列表中。
/museum remove <world>
从受保护世界列表中移除一个世界。
/museum reload
重新加载配置文件和消息文件。
/museum status
显示插件状态、当前世界保护状态、玩家权限、游戏模式诊断、配置计数和保护切换状态。
/museum debug on
启用调试模式。
/museum debug off
禁用调试模式。
/museum debug status
显示是否启用了调试模式。
/museum lockcurrentworld
将玩家当前所在的世界添加到受保护世界列表中。
/museum unlockcurrentworld
从受保护世界列表中移除玩家当前所在的世界。
权限
museumworld.admin
允许使用管理性的 /museum 命令。/museum version 子命令是公开的,不需要此权限。
museumworld.bypass
允许绕过 MuseumWorld 的保护检查。
默认情况下,museumworld.admin 通过 paper-plugin.yml 分配给 OP 用户。
调试模式
调试模式有助于识别操作为何被阻止或被允许。
使用以下命令启用:
/museum debug on
示例调试输出:
[MuseumWorld] [DEBUG] DENIED block-break | player=PlayerName | world=WorldName | locked=true | bypass=false | reason=locked world protection
示例允许输出:
[MuseumWorld] [DEBUG] ALLOWED block-break | player=PlayerName | world=WorldName | locked=true | bypass=true | reason=player has bypass/admin permission
在测试以下情况时,调试模式非常有用:
- 受保护的世界
- 绕过权限
- 只读方块
- 只读实体
- 物品栏保护
- 投射物阻挡
- 鞘翅烟花推进行为
- 桶/火/TNT 保护
- 载体和悬挂实体的保护
游戏模式感知诊断
MuseumWorld 的状态和调试输出包含与游戏模式相关的信息。
这很有用,因为 Minecraft 的游戏模式会影响方块破坏的可能性。
例如:
SURVIVAL(生存)和 CREATIVE(创造)通常允许破坏方块。
ADVENTURE(冒险)防止正常的方块破坏。
SPECTATOR(旁观者)防止正常的方块交互。
如果玩家处于 ADVENTURE 模式,BlockBreakEvent 可能不会触发,因为 Minecraft 本身会阻止正常的方块破坏。
使用:
/museum status
来检查:
- 当前世界
- 当前世界的保护状态
- 玩家的 OP 状态
- 玩家的游戏模式
museumworld.admin 权限
museumworld.bypass 权限
- 在当前游戏模式下预期是否能破坏方块
- 重要的保护切换状态
语言
MuseumWorld 支持英语和马其顿语的消息文件。
包含的文件:
messages_en.yml
messages_mk.yml
在 config.yml 中选择语言:
language: en # 用于英语
# language: mk # 用于马其顿语
只有一个 language 键应处于激活状态。
推荐的博物馆世界设置
对于博物馆/展示世界,建议使用多层保护:
- Multiverse 世界游戏模式:
ADVENTURE
- MuseumWorld 保护:已启用
- 如果需要,使用 WorldGuard 全局区域保护
推荐的用于博物馆世界的 Multiverse 风格设置:
gamemode: ADVENTURE
hunger: false
这允许玩家在不破坏方块或丢失饥饿值的情况下进行探索。
然后,MuseumWorld 可以提供额外的保护,以防止冒险模式未能完全覆盖的交互,例如:
- 物品栏移动
- 容器修改
- 物品掉落和拾取
- 桶的使用
- 火的使用
- TNT 引爆
- 实体操控
- 投射物使用
- 物品展示框和盔甲架交互
- 载体的放置/移除
关于门、活板门和栅栏门的说明
MuseumWorld 不会自动阻挡门、活板门或栅栏门。
在许多博物馆/展示世界中,它们是正常的导航方块。
如果您想锁定特定的门、活板门或栅栏门类型,请手动将其添加到:
readonly-blocks:
示例:
readonly-blocks:
- OAK_DOOR
- IRON_DOOR
- OAK_TRAPDOOR
- OAK_FENCE_GATE
如果它们未列出,玩家可以正常使用它们。
许可证
本项目根据 GNU 通用公共许可证 v3.0 授权。
详见 LICENSE 文件。
✅ 只读容器
MuseumWorld 允许玩家打开选定的容器并查看内部,同时阻止物品移动。
例如,玩家可以打开:
- 箱子
- barrels(木桶)
- 潜影盒
- 熔炉
- 漏斗
- 发射器
- 投掷器
- 酿造台
- lectern(讲台)
- 信标
但他们不能:
- 取走物品
- 放置物品
- 按住 Shift 点击物品
- 将物品拖入容器
- 使用漏斗进行物品传输
✅ 基于配置驱动
最重要的行为均在 config.yml 中进行控制,包括:
- 锁定世界
- 只读方块
- 只读实体
- 实体伤害保护
- 消息语言
- 消息冷却时间
- 调试模式
- 配置自动更新行为
✅ 自动配置更新
当新插件版本引入新选项时,MuseumWorld 可以自动添加缺失的配置键。
现有值会被保留。
受保护的配置键,例如:
protected-config-keys:
- locked-worlds
- language
在配置更新期间不会被覆盖。
启用此选项后,MuseumWorld 还可以更新缺失的列表值:
update-lists-on-next-reload: true
列表更新完成后,该选项会自动恢复为:
update-lists-on-next-reload: false
在执行自动配置更新之前,如果启用,插件可以创建备份:
backup-config-before-auto-update: true
备份存储在以下位置:
plugins/MuseumWorld/backups/
命令
主命令:
/museum
可用的子命令:
/museum list
/museum add <world>
/museum remove <world>
/museum reload
/museum status
/museum debug <on|off|status>
/museum lockcurrentworld
/museum unlockcurrentworld
命令概览
/museum list
显示所有已锁定/受保护的世界。
/museum add <world>
将世界添加到受保护世界列表中。
/museum remove <world>
从受保护世界列表中移除世界。
/museum reload
重新加载配置和消息文件。
/museum status
显示插件状态、当前世界保护状态、玩家权限、游戏模式诊断以及配置计数。
/museum debug on
启用调试模式。
/museum debug off
禁用调试模式。
/museum debug status
显示调试模式是否已启用。
/museum lockcurrentworld
将玩家当前所在的世界添加到受保护世界列表中。
/museum unlockcurrentworld
将玩家当前所在的世界从受保护世界列表中移除。
权限
museumworld.admin
允许使用 /museum 命令。
museumworld.bypass
允许绕过 MuseumWorld 的保护检查。
默认情况下,museumworld.admin 通过 paper-plugin.yml 分配给 OP 用户。
调试模式
调试模式有助于识别操作被阻止或允许的原因。
使用以下命令启用:
/museum debug on
调试输出示例:
[MuseumWorld] [DEBUG] DENIED block-break | player=PlayerName | world=WorldName | locked=true | bypass=false | reason=locked world protection
允许操作的输出示例:
[MuseumWorld] [DEBUG] ALLOWED block-break | player=PlayerName | world=WorldName | locked=true | bypass=true | reason=player has bypass/admin permission
感知游戏模式的诊断
MuseumWorld 的状态和调试输出包含与游戏模式相关的信息。
这非常有用,因为 Minecraft 的游戏模式会影响方块破坏的可能性。
例如:
SURVIVAL(生存)和 CREATIVE(创造)通常允许破坏方块。
ADVENTURE(冒险)会阻止正常的方块破坏。
SPECTATOR(旁观者)会阻止正常的方块交互。
如果玩家处于 ADVENTURE 模式,BlockBreakEvent 可能不会触发,因为 Minecraft 本身会阻止正常的方块破坏。
使用:
/museum status
来检查:
- 当前世界
- 当前世界的保护状态
- 玩家的 OP 状态
- 玩家的游戏模式
museumworld.admin 权限
museumworld.bypass 权限
- 在当前游戏模式下预期能否破坏方块
语言
MuseumWorld 支持英语和马其顿语的消息文件。
包含的文件:
messages_en.yml
messages_mk.yml
在 config.yml 中选择语言:
language: en # 用于英语
# language: mk # 用于马其顿语
应仅激活一个 language 键。
推荐的博物馆世界设置
对于博物馆/展示世界,建议使用多层保护:
- Multiverse 世界游戏模式:
ADVENTURE
- MuseumWorld 保护:已启用
- 如有需要,使用 WorldGuard 全局区域保护
推荐的适用于博物馆世界的 Multiverse 风格设置:
gamemode: ADVENTURE
hunger: false
这允许玩家在不妨碍破坏方块或丢失饥饿值的情况下进行探索。你仍然可以击杀敌对生物。
许可证
本项目采用 GNU General Public License v3.0 许可。
详情请参阅 LICENSE 文件。
MuseumWorld
MuseumWorld is a lightweight Paper plugin that turns selected worlds into read-only “museum / showcase” worlds.
Players can explore freely, while destructive actions, inventory modification, entity damage, and common interaction exploits are blocked.
It is designed for:
- lobby / spawn / hub worlds
- showcase maps
- museum builds
- read-only adventure areas
- worlds where visitors should explore, but not edit
Key Features
✅ Read-only worlds
You choose which worlds are protected through config.yml.
In protected worlds, MuseumWorld can block:
- block breaking
- block placing
- inventory modification
- entity damage
- armor stand manipulation
- item frame / painting interaction
- protected container modification
- hopper/item transfer involving protected inventories
- explosions damaging blocks
- item dropping
- item pickup
- bucket fill/empty actions
- flint and steel / fire charge use
- fire ignition
- TNT ignition
- bed use
- bone meal use
- Nether portal creation
- natural growth, spread and decay changes
- projectile use, with optional Elytra firework boost exception
- lead use
- name tag use
- vehicle placement and breaking
- hanging entity breaking/removal
✅ View-only containers
MuseumWorld allows players to open selected containers and look inside, while blocking item movement.
For example, players can open:
- chests
- barrels
- shulker boxes
- furnaces
- hoppers
- dispensers
- droppers
- brewing stands
- lecterns
- beacons
But they cannot:
- take items
- place items
- shift-click items
- drag items into the container
- move items using hopper transfers
✅ Strictly config-driven protection
MuseumWorld is designed to be predictable and controlled through config.yml.
Read-only blocks and read-only entities are protected only if they are explicitly listed in:
readonly-blocks:
readonly-entities:
There is no automatic read-only block/entity detection.
This means navigation blocks such as doors, trapdoors and fence gates are not blocked unless the server owner explicitly adds them to readonly-blocks.
For example, if players should be able to open doors in a museum world, simply do not add those doors to readonly-blocks.
If a specific door should be locked, add it manually:
readonly-blocks:
- OAK_DOOR
- IRON_DOOR
This keeps the plugin fully configurable and avoids unexpected protection behavior.
✅ Extended protection toggles
MuseumWorld includes additional protection options for common grief-prevention and museum-world use cases.
Example:
block-item-drop: true
block-item-pickup: true
block-bucket-use: true
block-fire-use: true
block-natural-growth: false
block-bone-meal-use: true
block-portal-creation: true
block-item-frame-rotation: true
block-armor-stand-manipulation: true
block-tnt-ignite: true
block-player-bed-use: true
block-hanging-break: true
block-vehicle-place-break: true
block-projectile-use: true
block-lead-use: true
block-name-tag-use: true
These options allow server owners to decide exactly how strict each protected world should be.
✅ Elytra support
Projectile blocking can be enabled while still allowing Elytra firework boosting.
block-projectile-use: true
allow-elytra-firework-boost: true
When enabled, players can still use firework rockets while gliding with Elytra.
This allows Elytra flight in protected worlds while still blocking other projectile-style interactions such as eggs, ender pearls, splash potions and similar actions.
✅ Config validation and safe cleanup
MuseumWorld can validate selected config lists on startup.
The validator checks:
readonly-blocks
view-only-containers
readonly-entities
blocked-entity-types
If invalid Material or EntityType names are found, MuseumWorld can automatically remove them when enabled:
auto-clean-invalid-config-values: true
Before cleanup, the plugin can create a backup of config.yml.
Validation reports are saved under:
plugins/MuseumWorld/logs/
Config backups are saved under:
plugins/MuseumWorld/backups/
The validator does not modify:
locked-worlds
language
✅ Automatic config updates
MuseumWorld can automatically add missing config keys when a new plugin version introduces new options.
Existing values are preserved.
Protected config keys, such as:
protected-config-keys:
- locked-worlds
- language
are not overwritten during config updates.
MuseumWorld can also update missing list values when this option is enabled:
update-lists-on-next-reload: true
After the list update is completed, the option automatically returns to:
update-lists-on-next-reload: false
Before automatic config updates, the plugin can create a backup if enabled:
backup-config-before-auto-update: true
Backups are stored in:
plugins/MuseumWorld/backups/
✅ Template-based config rewrite
MuseumWorld rewrites config.yml using the bundled default configuration as a template.
This means automatic config updates preserve:
- official comments
- key order
- newly added explanations
- existing user-defined values
- custom list entries
- a clean and predictable config layout
The bundled default config.yml acts as the reference layout.
The active server config.yml keeps user values, while missing keys and comments are restored from the default template.
config-version is always kept as the final key at the bottom of the file.
✅ bStats metrics
MuseumWorld uses anonymous bStats metrics.
bStats helps track how many servers use the plugin and which server/software versions are common. It does not collect private player data, chat, world names or config values.
✅ Update checker
MuseumWorld can check GitHub Releases for new plugin versions on startup.
update-checker-enabled: true
notify-admins-about-updates: true
The update checker only notifies server owners/admins. It never downloads or installs updates automatically.
Commands
Main command:
/museum
Available subcommands:
/museum version
/museum list
/museum add <world>
/museum remove <world>
/museum reload
/museum status
/museum debug <on|off|status>
/museum lockcurrentworld
/museum unlockcurrentworld
Command overview
/museum version
Shows public plugin information. This command is available to all players and does not require museumworld.admin.
Example output:
MuseumWorld
Version: 1.1.0
Channel: STABLE
Target API: Paper 26.1.2
Author: Tantrum90MK
/museum list
Shows all locked/protected worlds.
/museum add <world>
Adds a world to the protected worlds list.
/museum remove <world>
Removes a world from the protected worlds list.
/museum reload
Reloads config and message files.
/museum status
Shows plugin status, current world protection status, player permissions, gamemode diagnostics, config counts and protection toggle states.
/museum debug on
Enables debug mode.
/museum debug off
Disables debug mode.
/museum debug status
Shows whether debug mode is enabled.
/museum lockcurrentworld
Adds the world where the player is currently standing to the protected worlds list.
/museum unlockcurrentworld
Removes the world where the player is currently standing from the protected worlds list.
Permissions
museumworld.admin
Allows use of administrative /museum commands. The /museum version subcommand is public and does not require this permission.
museumworld.bypass
Allows bypassing MuseumWorld protection checks.
By default, museumworld.admin is assigned to OP users through paper-plugin.yml.
Debug mode
Debug mode helps identify why actions are blocked or allowed.
Enable it with:
/museum debug on
Example debug output:
[MuseumWorld] [DEBUG] DENIED block-break | player=PlayerName | world=WorldName | locked=true | bypass=false | reason=locked world protection
Example allowed output:
[MuseumWorld] [DEBUG] ALLOWED block-break | player=PlayerName | world=WorldName | locked=true | bypass=true | reason=player has bypass/admin permission
Debug mode is useful when testing:
- protected worlds
- bypass permissions
- read-only blocks
- read-only entities
- inventory protection
- projectile blocking
- Elytra firework boost behavior
- bucket/fire/TNT protections
- vehicle and hanging entity protections
Gamemode-aware diagnostics
MuseumWorld status and debug output include gamemode-related information.
This is useful because Minecraft gamemodes affect whether block breaking is possible.
For example:
SURVIVAL and CREATIVE normally allow block breaking.
ADVENTURE prevents normal block breaking.
SPECTATOR prevents normal block interaction.
If a player is in ADVENTURE mode, BlockBreakEvent may not fire because Minecraft itself prevents normal block breaking.
Use:
/museum status
to check:
- current world
- current world protection status
- player OP status
- player gamemode
museumworld.admin permission
museumworld.bypass permission
- whether block breaking is expected to work in the current gamemode
- important protection toggle states
Language
MuseumWorld supports English and Macedonian message files.
Included files:
messages_en.yml
messages_mk.yml
Select language in config.yml:
language: en # for English
# language: mk # for Macedonian
Only one language key should be active.
Recommended museum-world setup
For museum/showcase worlds, it is recommended to use multiple protection layers:
- Multiverse world gamemode:
ADVENTURE
- MuseumWorld protection: enabled
- WorldGuard global region protection if needed
Recommended Multiverse-style settings for museum worlds:
gamemode: ADVENTURE
hunger: false
This allows players to explore without breaking blocks or losing hunger.
MuseumWorld can then provide additional protection against interactions that Adventure mode does not fully cover, such as:
- inventory movement
- container modification
- item dropping and pickup
- bucket use
- fire use
- TNT ignition
- entity manipulation
- projectile use
- item frame and armor stand interaction
- vehicle placement/removal
Notes about doors, trapdoors and gates
MuseumWorld does not automatically block doors, trapdoors or fence gates.
They are normal navigation blocks in many museum/showcase worlds.
If you want to lock a specific door, trapdoor or fence gate type, add it manually to:
readonly-blocks:
Example:
readonly-blocks:
- OAK_DOOR
- IRON_DOOR
- OAK_TRAPDOOR
- OAK_FENCE_GATE
If they are not listed, players can use them normally.
License
This project is licensed under the GNU General Public License v3.0.
See the LICENSE file for details.
✅ View-only containers
MuseumWorld allows players to open selected containers and look inside, while blocking item movement.
For example, players can open:
- chests
- barrels
- shulker boxes
- furnaces
- hoppers
- dispensers
- droppers
- brewing stands
- lecterns
- beacons
But they cannot:
- take items
- place items
- shift-click items
- drag items into the container
- move items using hopper transfers
✅ Config-driven
Most important behavior is controlled in config.yml, including:
- locked worlds
- read-only blocks
- read-only entities
- entity damage protection
- message language
- message cooldown
- debug mode
- config auto-update behavior
✅ Automatic config updates
MuseumWorld can automatically add missing config keys when a new plugin version introduces new options.
Existing values are preserved.
Protected config keys, such as:
protected-config-keys:
- locked-worlds
- language
are not overwritten during config updates.
MuseumWorld can also update missing list values when this option is enabled:
update-lists-on-next-reload: true
After the list update is completed, the option automatically returns to:
update-lists-on-next-reload: false
Before automatic config updates, the plugin can create a backup if enabled:
backup-config-before-auto-update: true
Backups are stored in:
plugins/MuseumWorld/backups/
Commands
Main command:
/museum
Available subcommands:
/museum list
/museum add <world>
/museum remove <world>
/museum reload
/museum status
/museum debug <on|off|status>
/museum lockcurrentworld
/museum unlockcurrentworld
Command overview
/museum list
Shows all locked/protected worlds.
/museum add <world>
Adds a world to the protected worlds list.
/museum remove <world>
Removes a world from the protected worlds list.
/museum reload
Reloads config and message files.
/museum status
Shows plugin status, current world protection status, player permissions, gamemode diagnostics, and config counts.
/museum debug on
Enables debug mode.
/museum debug off
Disables debug mode.
/museum debug status
Shows whether debug mode is enabled.
/museum lockcurrentworld
Adds the world where the player is currently standing to the protected worlds list.
/museum unlockcurrentworld
Removes the world where the player is currently standing from the protected worlds list.
Permissions
museumworld.admin
Allows use of /museum commands.
museumworld.bypass
Allows bypassing MuseumWorld protection checks.
By default, museumworld.admin is assigned to OP users through paper-plugin.yml.
Debug mode
Debug mode helps identify why actions are blocked or allowed.
Enable it with:
/museum debug on
Example debug output:
[MuseumWorld] [DEBUG] DENIED block-break | player=PlayerName | world=WorldName | locked=true | bypass=false | reason=locked world protection
Example allowed output:
[MuseumWorld] [DEBUG] ALLOWED block-break | player=PlayerName | world=WorldName | locked=true | bypass=true | reason=player has bypass/admin permission
Gamemode-aware diagnostics
MuseumWorld status and debug output include gamemode-related information.
This is useful because Minecraft gamemodes affect whether block breaking is possible.
For example:
SURVIVAL and CREATIVE normally allow block breaking.
ADVENTURE prevents normal block breaking.
SPECTATOR prevents normal block interaction.
If a player is in ADVENTURE mode, BlockBreakEvent may not fire because Minecraft itself prevents normal block breaking.
Use:
/museum status
to check:
- current world
- current world protection status
- player OP status
- player gamemode
museumworld.admin permission
museumworld.bypass permission
- whether block breaking is expected to work in the current gamemode
Language
MuseumWorld supports English and Macedonian message files.
Included files:
messages_en.yml
messages_mk.yml
Select language in config.yml:
language: en # for English
# language: mk # for Macedonian
Only one language key should be active.
Recommended museum-world setup
For museum/showcase worlds, it is recommended to use multiple protection layers:
- Multiverse world gamemode:
ADVENTURE
- MuseumWorld protection: enabled
- WorldGuard global region protection if needed
Recommended Multiverse-style settings for museum worlds:
gamemode: ADVENTURE
hunger: false
This allows players to explore without breaking blocks or losing hunger. You can still kill un-friendly mobs.
License
This project is licensed under the GNU General Public License v3.0.
See the LICENSE file for details.
评论 0
登录后参与评分
还没有评论,来抢沙发吧