Locktight - 高级箱子保护与安全系统
Locktight 将箱子安全从简单的保护机制转变为引人入胜、具有战略性的游戏元素,增强了注重安全和突袭风格的服务器体验。
Folia: Folia 的支持仍处于开发阶段——它可能存在单区域 Paper 上未见的瑕疵或问题。在可能的情况下请使用 Paper;当你需要区域化调度时再尝试 Folia,并报告问题以便修复。
如果遇到任何问题,请确保首先运行最新版本,然后在 Discord 的 #PLUGIN-HELP 频道中报告该问题。
注意:如果因 LOCKTIGHT 遇到性能问题,请使用最新正式版。Alpha 1.0.4 - 1.0.9 版本由于漏斗重载任务已知存在性能问题。 请注意漏斗密集型基地,因为防止漏斗从锁定的箱子中窃取物品的逻辑。测试表明,自 A1.1.0 起的新逻辑在服务线程使用方面效率提高了 94%。请在提供的 Discord 支持频道中报告任何问题。
平台: Locktight 基于 Paper API 为 Paper(和 Folia)构建。不支持 Plain Spigot。请为你的 Minecraft 版本使用当前的 Paper(或 Folia)构建。
概述
Locktight 是一款全面的箱子保护插件,旨在为领地内的箱子提供额外的安全层,同时保持对各种服务器类型的灵活性。无论是基于领地的服务器还是突袭风格的服务器,Locktight 都提供了复杂的箱子锁定机制、可配置的信任系统以及引人入胜的撬锁游戏元素。
使用方法
- 只需注视你想要锁定的箱子并执行
/chest lock
- 从
/chest shop 购买撬棍、加固材料和 锁具工具:右键点击以锁定或解锁(规则同 /chest lock / /chest unlock),左键点击以检查(规则同 /chest inspect)
- 自 1.0.6 版本起,放置箱子时可自动锁定(可配置)—— 1.1.4 中默认值更改为 FALSE
- 锁定任何可锁定的容器:箱子、双层箱、** barrel(木桶)**、所有颜色的潜影盒 和 铜箱 (1.21)。双层箱的两侧均可进行锁定、解锁、删除和信任操作。
⚙️ 配置
主配置文件 (config.yml)
随插件分发的文件为准。以下是当前布局(值与 JAR 中的默认 config.yml 匹配;经过编辑后你的文件可能有所不同)。
# 完整的横幅头信息在 JAR 的 config.yml 中 — Paper & Folia, by MightyFinger77
# config_version — 用于迁移。除非你清楚其中的原理,否则不要更改。
config_version: 5
# 常规设置
general:
auto_lock_on_place: false # 实验性功能 — 启用风险自负
check_updates: true
close_gui_after_purchase: false
chest_lock_expiration_days: 28
chest_lock_cleanup_interval_hours: 6
debug_enabled: false
hopper_debug: false
lockpicking:
enabled: true
temporary_access_seconds: 30
success_rates:
weak: 0.005
medium: 0.05
advanced: 0.1
professional: 0.3
mythical: 1.0
alerts:
enabled: true
default_enabled: true
allow_lockpicking_offline_players: true
# lock_tool.enabled — 右键切换锁定状态;左键检查(参见 JAR 中的 config.yml)
lock_tool:
enabled: true
reinforcement:
enabled: true
resistance_increase: 0.05
max_reinforcements: 8
attempts_per_degradation: 5
# griefdefender.block_lockpick_in_trusted_foreign_claim — 可选:阻止在该领地中受信任的非领地所有者进行撬锁
# (默认 false)。请参阅完整 config.yml。
# ... world_blacklist, sound_effects, bypass_permission, griefdefender,
# economy, performance — 详见 plugins/Locktight/ 中的完整 config.yml
消息配置 (messages.yml)
自定义所有插件消息、颜色和格式。
GUI 配置 (gui.yml)
配置商店槽位布局、shop_rows(1-6 行,每行 9 个槽位,默认 5)、显示名称、描述(包括 {weak_rate} 占位符)、价格、可选的整数 custom model data,以及用于购买堆栈 名称/描述/概率 的 item: 子部分。
对于 完全自定义物品(资源包、ItemsAdder/Nexo 风格组件、非默认材质),管理员使用 /chest itemset;视觉效果来自手持物品,而 名称和描述仍遵循 gui.yml。模板存储在 plugins/Locktight/item_templates.yml 中,带有文件头字段 templates_version(与序列化堆栈内 Paper 的每个物品 schema_version 分开)。
主要功能
?️ 增强的领地安全
Locktight 与 GriefDefender 无缝集成,提供超越标准领地信任的第二层保护。拥有领地访问权限的玩家不能自动打开锁定的箱子,除非通过 /chest trust 命令明确信任。这确保了即使是被信任的玩家也必须单独授权才能访问各个箱子。可选地,griefdefender.block_lockpick_in_trusted_foreign_claim(默认 false)阻止拥有 GriefDefender 信任但不是领地所有者的玩家在该领地内进行撬锁——这对于防止同一基地中共信任的玩家互相撬锁非常有用;领地组的信任包含在内。领地所有者不受此设置的限制。
? 智能箱子锁定
- 多种容器类型:锁定 箱子(单箱和双箱)、木桶、潜影盒(所有颜色)以及 铜箱子(1.21 版本)。支持所有铜箱子变体;锁存储于方块位置,因此当铜箱子氧化或改变状态时,锁会保留。双箱被视为一个锁;从任意一侧均可执行锁定、解锁、删除和授权操作。
- 仅所有者访问:上锁的箱子可防止未经授权的访问
- 不可破坏保护:根据插件规则,上锁的箱子无法用手破坏或由爆炸摧毁
- 管理员锁 (
/chest adminlock):无法被撬开,永不过期;只有拥有 locktight.adminlock 权限的玩家才能打开或破坏它们。
- 所有者锁 (
/chest olock):只有所有者或被信任该箱子的玩家才能访问。绕过权限和管理员锁不授予访问权限。无法被撬开,永不过期。信任关系需针对每个箱子单独设置(批量信任会跳过所有者锁)。
- 领地集成:尊重领地边界和信任等级
- 可配置权限:服务器管理员可以定义哪些信任等级(CONTAINER、BUILDER、MANAGER)可以在领地内锁定箱子
? 高级信任管理
按箱子信任 (/chest trust / untrust)、批量信任 (/chest trustall / untrustall,可选半径)、与 LuckPerms 结合的群组信任 (/chest trustgroup / trustgroupall 及其取消信任变体),以及清除信任 (cleartrusts, cleartrustsgroups, cleartrustsboth)。所有者锁排除在批量/半径信任之外,必须单独进行信任设置。
? 引人入胜的撬锁系统
- 多个层级:弱、中、高级、专业级和神话级撬锁工具
- 可配置的成功率:在
config.yml 中平衡游戏玩法与安全
- 可选 GriefDefender 规则:
griefdefender.block_lockpick_in_trusted_foreign_claim ——启用后,受信任的非所有者不能在该领地内撬锁(见上方 GriefDefender 部分)。
- 游戏内商店:通过 Vault 购买撬锁工具
- 加固系统:所有者可以加固箱子以降低撬锁成功率
- 自定义物品模板:
/chest itemset (locktight.itemset) 将主手物品保存为某一等级、加固层或锁具工具的模板。商店图标和购买物品使用该堆栈的材质/模型/组件;显示名称和描述仍来自 gui.yml。物品上的标签确保撬锁/加固/锁具工具的逻辑不依赖于显示名称。/chest itemset clear <tier> 移除模板。/chest reload 重新加载 item_templates.yml。
⚙️ 灵活配置
- 基于领地的服务器:在 GriefDefender 领地内提供额外安全保护
- 袭击服务器:野外锁定与撬锁功能,支持以袭击为导向的游戏玩法
- 混合服务器:结合保护与袭击元素
服务器类型
? 基于领地的保护服务器
GriefDefender 集成尊重领地所有权和可配置信任等级,确保合适的玩家能在其区域锁定箱子。
⚔️ 袭击风格服务器
野外锁定与撬锁功能支持以袭击为导向的游戏玩法。
? 混合服务器
配置野外锁定、领地和商店/经济系统,以匹配您的安全与风险组合。
技术特性
- SQLite(内置驱动):用于存储箱子锁、信任关系、加固及相关数据
- Vault:用于商店的经济系统
- GriefDevender API:感知领地的锁定功能(软依赖)
- LuckPerms(可选):基于群组的信任管理
- Paper / Folia:支持;在 Folia 上使用安全的调度机制(插件元数据中包含
folia-supported: true)
- 可配置的过期时间:自动清理废弃的锁(管理员锁和所有者锁永不过期)
- 可锁定的容器:箱子(包括双箱)、木桶、所有颜色的潜影盒,以及服务器版本支持的铜箱子变体
优势
- 增强的安全性:超越单纯的领地信任机制
- 平衡的游戏体验:在防御与袭击之间取得平衡
- 玩家参与度:通过撬锁和加固系统提升互动性
- 灵活的部署方式:适用于各种服务器风格
- 自定义商店视觉效果:同时保留 YAML 驱动的概率和描述文本
? 权限与命令
所有权限节点
| 权限 |
描述 |
默认值 |
locktight.use |
锁定、解锁、信任、检查自己的箱子,删除自己的箱子 |
true |
locktight.shop |
访问撬锁工具商店 |
true |
locktight.lockpick |
对箱子使用撬锁工具 |
op |
locktight.lockpickget |
通过命令获取撬锁工具物品 |
op |
locktight.lockpickget.other |
向其他玩家发放撬锁工具物品 |
op |
locktight.itemset |
保存自定义撬锁工具/加固/锁具工具模板 (/chest itemset) |
op |
locktight.reload |
重新加载插件配置 |
op |
locktight.cleanup |
手动触发箱子锁过期清理 |
op |
locktight.adminlock |
创建无法被撬开的管理员锁 |
op |
locktight.ownerlock |
创建所有者锁(绕过权限/管理员锁不适用) |
op |
locktight.bypass |
绕过箱子锁(除所有者锁外),并根据规则进行检查或删除 |
op |
locktight.update |
手动检查插件更新 |
op |
locktight.* |
所有插件功能的通配符 |
op |
所有命令
| 命令 |
描述 |
权限 |
/chest lock |
锁定你正在查看的容器 |
locktight.use |
/chest unlock |
解锁你锁定的容器 |
locktight.use |
/chest trust <player> |
信任某玩家使用此箱子 |
locktight.use |
/chest untrust <player|all> |
取消对某玩家(或所有玩家)的信任 |
locktight.use |
/chest trustall <player> [radius] |
在所有(或指定半径内)你的箱子上信任该玩家;跳过所有者锁定 |
locktight.use |
| `/chest untrustall <player> [radius] |
在所有(或指定半径内)取消对该玩家的信任;跳过所有者锁定 |
locktight.use |
/chest trustgroup <group> |
在 LuckPerms 组中信任某组用户访问此箱子 |
locktight.use |
/chest trustgroupall <group> |
在所有你的箱子上信任某组用户;跳过所有者锁定 |
locktight.use |
/chest untrustgroup / untrustgroupall |
移除组的信任状态 |
locktight.use |
/chest cleartrusts / cleartrustsgroups / cleartrustsboth |
清除当前箱子上的所有信任关系 |
locktight.use |
/chest delete |
删除箱子数据(包括双箱子的两侧) |
locktight.use / locktight.bypass(适用规则) |
/chest inspect |
检查容器 |
locktight.use / locktight.bypass |
/chest shop |
打开开锁工具商店 |
locktight.shop |
/chest reload |
重新加载配置(包括 item_templates.yml) |
locktight.reload |
/chest cleanup |
清理过期的锁 |
locktight.cleanup |
/chest lockpick [tier] |
对容器使用开锁工具 |
locktight.lockpick |
/chest lockpickget [tier] [qty] [player] |
获取开锁工具/加固物品 |
locktight.lockpickget |
/chest itemset <tier|reinforcement|locktool> |
将手持物品保存为商店模板 |
locktight.itemset |
/chest itemset clear <tier|reinforcement|locktool> |
移除已保存的模板 |
locktight.itemset |
/chest adminlock |
设置管理员锁 |
locktight.adminlock |
/chest olock |
设置所有者锁 |
locktight.ownerlock |
/chest autolock |
切换放置时的自动锁定功能 |
locktight.use |
| /chest alerts | 切换开锁警报 | locktight.use |
/chest help [子命令] |
帮助 |
— |
/chest bypass |
切换绕过模式 |
locktight.bypass |
/chest update |
检查更新 |
locktight.update |
权限逻辑说明
- 检查:自己的箱子使用
locktight.use;任意箱子(按实现中的检查规则)使用 locktight.bypass。
- 删除:自己的箱子需
locktight.use;非所有者锁定的箱子根据插件规则可绕过。所有者锁定:仅限所有者进行删除。管理员锁定:需 locktight.adminlock(或 locktight.*)。
- 打开 / 破坏(普通锁):所有者/受信任玩家;非所有者锁定的容器可使用
locktight.bypass。
- 管理员锁定:不可撬开;打开/破坏/删除需
locktight.adminlock / locktight.*(按实现中规定)。
- 所有者锁定:仅限所有者或该箱子的受信任玩家;
locktight.bypass 和 locktight.adminlock 不提供访问权限。请对该箱子使用 /chest trust;trustall / trustgroupall 可跳过所有者锁定。
? 待办事项 / 未来改进
计划中的功能
- 完全模块化的等级系统:允许仅通过配置文件添加任意新的开锁等级,无需更改代码(目前,等级被硬编码到特定的商店键和配置路径中;
/chest itemset 已涵盖现有等级的自定义外观和基于 PDC 的检测)。
- 可上锁的门(门、陷阱门等)
- 可上锁的红石方块(按钮、拉杆、压力板)
- 可上锁的末影箱
- 更多可上锁的变体(例如船/矿车储物箱),在可行的情况下
已实现(不再属于 TODO)
- 可上锁的 barrels(木桶)
- 可上锁的潜影盒(所有颜色)
- 可上锁的铜箱(1.21 版本)及氧化/打蜡后的持久化支持
- 双向互动的双箱(从任一侧均可锁定、解锁、删除、信任、检查)
- Paper & Folia 支持,具备区域安全调度机制
- 自定义商店物品模板(
/chest itemset、item_templates.yml、locktight.itemset)
- 开锁工具(商店购买 +
/chest itemset locktool):右键锁定/解锁,左键检查
- 可配置的商店大小(
gui.yml 中的 shop_rows)
- 可选的受信任领地内的开锁块(
griefdefender.block_lockpick_in_trusted_foreign_claim)
欢迎提出任何建议!
Locktight - Advanced Chest Protection & Security System
Locktight transforms chest security from a simple protection mechanism into an engaging, strategic gameplay element that enhances both security-focused and raid-style server experiences.
Folia: Support for Folia is still developmental—it may have rough edges or issues not seen on single-region Paper. Use Paper when you can; try Folia when you need regionized scheduling and report problems so they can be fixed.
IF YOU RUN INTO ISSUES, BE SURE YOU ARE RUNNING THE LATEST BUILD FIRST, THEN REPORT THE ISSUE IN #PLUGIN-HELP IN THE DISCORD.
NOTE: IF EXPERIENCING PERFORMANCE ISSUES BECAUSE OF LOCKTIGHT, USE LATEST RELEASE. VERSIONS ALPHA 1.0.4 - 1.0.9 HAD KNOWN PERFORMANCE ISSUES DUE TO HOPPER HEAVY TASKS. Be wary of hopper heavy bases, due to the logic that prevents hoppers stealing from locked chests. Tests show new logic as of A1.1.0 to be 94% more efficient in terms of server thread usage. Please report any issues in the provided Discord channel for support.
Platform: Locktight is built for Paper (and Folia) using the Paper API. Plain Spigot is not supported. Use a current Paper (or Folia) build for your Minecraft version.
Overview
Locktight is a comprehensive chest protection plugin designed to provide an additional layer of security for chests within land claims while maintaining flexibility for various server types. Perfect for both claim-based and raid-style servers, Locktight offers sophisticated chest locking mechanisms, configurable trust systems, and an engaging lockpicking gameplay element.
How to Use
- Simply look at the chest you wish to lock and execute
/chest lock
- Purchase lockpicks, lock reinforcements, and a lock tool from
/chest shop: right-click to lock or unlock (same rules as /chest lock / /chest unlock), left-click to inspect (same rules as /chest inspect)
- AS OF 1.0.6, CHESTS CAN BE AUTO LOCKED ON PLACEMENT (CONFIGURABLE) — DEFAULT VALUE CHANGED TO FALSE IN 1.1.4
- Lock any lockable container: chests, double chests, barrels, all shulker box colors, and copper chests (1.21). Lock, unlock, delete, and trust work from either side of a double chest.
⚙️ Configuration
Main Configuration (config.yml)
The file shipped with the plugin is authoritative. Below is the current layout (values match the default config.yml in the JAR; yours may differ after edits).
# Full banner header is in the JAR’s config.yml — Paper & Folia, by MightyFinger77
# config_version — used for migrations. Do not change unless you know the drill.
config_version: 5
# General Settings
general:
auto_lock_on_place: false # EXPERIMENTAL — enable at your own risk
check_updates: true
close_gui_after_purchase: false
chest_lock_expiration_days: 28
chest_lock_cleanup_interval_hours: 6
debug_enabled: false
hopper_debug: false
lockpicking:
enabled: true
temporary_access_seconds: 30
success_rates:
weak: 0.005
medium: 0.05
advanced: 0.1
professional: 0.3
mythical: 1.0
alerts:
enabled: true
default_enabled: true
allow_lockpicking_offline_players: true
# lock_tool.enabled — right-click toggle lock; left-click inspect (see config.yml in JAR)
lock_tool:
enabled: true
reinforcement:
enabled: true
resistance_increase: 0.05
max_reinforcements: 8
attempts_per_degradation: 5
# griefdefender.block_lockpick_in_trusted_foreign_claim — optional: block lockpicking
# for trusted non–claim-owners in that claim (default false). See full config.yml.
# ... world_blacklist, sound_effects, bypass_permission, griefdefender,
# economy, performance — see full config.yml in plugins/Locktight/
Messages (messages.yml)
Customize all plugin messages, colors, and formatting.
GUI Configuration (gui.yml)
Configure shop slot layout, shop_rows (1–6 rows of 9 slots, default 5), display names, lore (including {weak_rate} placeholders), prices, optional integer custom model data, and the item: subsection used for purchased stack name/lore/rates.
For full custom items (resource packs, ItemsAdder/Nexo-style components, non-default materials), admins use /chest itemset; visuals come from the held item, while name and lore still follow gui.yml. Templates are stored in plugins/Locktight/item_templates.yml with a file header field templates_version (separate from Paper’s per-item schema_version inside serialized stacks).
Key Features
?️ Enhanced Claim Security
Locktight integrates seamlessly with GriefDefender to provide a second layer of protection beyond standard claim trusts. Players with claim access cannot automatically open locked chests unless explicitly trusted through the /chest trust command. This ensures that even trusted players must be specifically authorized for individual chest access. Optionally, griefdefender.block_lockpick_in_trusted_foreign_claim (default false) prevents lockpicking inside a claim by players who have GriefDefender trust there but are not the claim owner—useful so co-trusted players in one base cannot pick each other’s locks; claim group trust is included. Claim owners are not restricted by this setting.
? Intelligent Chest Locking
- Multiple container types: Lock chests (single and double), barrels, shulker boxes (all colors), and copper chests (1.21). All copper chest variants are supported; locks are stored by block location so they persist when copper chests oxidize or change state. Double chests are treated as one lock; lock, unlock, delete, and trust work from either side.
- Owner-only access: Locked chests are secure from unauthorized access
- Indestructible protection: Locked chests cannot be broken by hand or destroyed by explosions (per plugin rules)
- Admin locks (
/chest adminlock): Unpickable, never expire; only players with locktight.adminlock can open or break them.
- Owner locks (
/chest olock): Only the owner or players trusted on that chest can access. Bypass and adminlock do not grant access. Unpickable, never expire. Trust must be set per chest (bulk trust skips owner locks).
- Claim integration: Respects claim boundaries and trust levels
- Configurable permissions: Server owners can define which trust levels (CONTAINER, BUILDER, MANAGER) can lock chests within claims
? Advanced Trust Management
Per-chest trust (/chest trust / untrust), bulk trust (/chest trustall / untrustall with optional radius), group trust with LuckPerms (/chest trustgroup / trustgroupall and untrust variants), and clear trusts (cleartrusts, cleartrustsgroups, cleartrustsboth). Owner locks are excluded from bulk/radius trust and must be trusted individually.
? Engaging Lockpicking System
- Multiple tiers: Weak, Medium, Advanced, Professional, and Mythical lockpicks
- Configurable success rates: Balance gameplay and security in
config.yml
- Optional GriefDefender rule:
griefdefender.block_lockpick_in_trusted_foreign_claim — when enabled, trusted non–owners cannot lockpick in that claim (see GriefDefender above).
- In-game shop: Purchase lockpicks with Vault
- Reinforcement system: Owners reinforce chests to reduce lockpick success rates
- Custom item templates:
/chest itemset (locktight.itemset) saves the item in your main hand as the template for a tier, reinforcement, or locktool. Shop icons and purchased items use that stack’s material/model/components; display name and lore still come from gui.yml. Tags on the item ensure lockpick/reinforcement/lock-tool logic does not depend on display names. /chest itemset clear <tier> removes a template. /chest reload reloads item_templates.yml.
⚙️ Flexible Configuration
- Claim-based servers: Extra security inside GriefDefender claims
- Raid servers: Wilderness locking and lockpicking
- Hybrid servers: Mix protection and raiding
Server Types
? Claim-Based Protection Servers
GriefDefender integration respects claim ownership and configurable trust levels so the right players can lock chests in their areas.
⚔️ Raid-Style Servers
Wilderness locking and lockpicking support raiding-oriented gameplay.
? Hybrid Servers
Configure wilderness locking, claims, and shop/economy to match your mix of security and risk.
Technical Features
- SQLite (bundled driver): Chest locks, trust, reinforcements, and related data
- Vault: Economy for the shop
- GriefDefender API: Claim-aware locking (soft dependency)
- LuckPerms (optional): Group-based trust
- Paper / Folia: Supported; uses safe scheduling on Folia (
folia-supported: true in plugin metadata)
- Configurable expiration: Automatic cleanup of abandoned locks (admin and owner locks never expire)
- Lockable containers: Chests (including double), barrels, all shulker colors, copper chest variants where the server version supports them
Benefits
- Enhanced security beyond claim trusts alone
- Balanced gameplay between defense and raiding
- Player engagement via lockpicking and reinforcements
- Flexible deployment across server styles
- Custom shop visuals without losing YAML-driven rates and lore
? Permissions & Commands
All permission nodes
| Permission |
Description |
Default |
locktight.use |
Lock, unlock, trust, inspect own chests, delete own chests |
true |
locktight.shop |
Access the lockpick shop |
true |
locktight.lockpick |
Use lockpicks on chests |
op |
locktight.lockpickget |
Get lockpick items via command |
op |
locktight.lockpickget.other |
Give lockpick items to other players |
op |
locktight.itemset |
Save custom lockpick/reinforcement/lock-tool templates (/chest itemset) |
op |
locktight.reload |
Reload plugin configuration |
op |
locktight.cleanup |
Manually trigger chest lock expiration cleanup |
op |
locktight.adminlock |
Create unpickable admin locks |
op |
locktight.ownerlock |
Create owner locks (bypass/adminlock do not apply) |
op |
locktight.bypass |
Bypass chest locks (except owner locks) and inspect/delete per rules |
op |
locktight.update |
Manually check for plugin updates |
op |
locktight.* |
Wildcard for all plugin features |
op |
All commands
| Command |
Description |
Permission |
/chest lock |
Lock the container you’re looking at |
locktight.use |
/chest unlock |
Unlock your locked container |
locktight.use |
/chest trust <player> |
Trust a player on this chest |
locktight.use |
/chest untrust <player|all> |
Untrust a player (or all) on this chest |
locktight.use |
/chest trustall <player> [radius] |
Trust on all (or radius) of your chests; skips owner locks |
locktight.use |
/chest untrustall <player> [radius] |
Untrust from all (or radius); skips owner locks |
locktight.use |
/chest trustgroup <group> |
Trust a LuckPerms group on this chest |
locktight.use |
/chest trustgroupall <group> |
Trust a group on all your chests; skips owner locks |
locktight.use |
/chest untrustgroup / untrustgroupall |
Remove group trust |
locktight.use |
/chest cleartrusts / cleartrustsgroups / cleartrustsboth |
Clear trusts on this chest |
locktight.use |
/chest delete |
Delete chest data (either side of double chest) |
locktight.use / locktight.bypass (rules apply) |
/chest inspect |
Inspect container |
locktight.use / locktight.bypass |
/chest shop |
Open lockpick shop |
locktight.shop |
/chest reload |
Reload configuration (including item_templates.yml) |
locktight.reload |
/chest cleanup |
Clean expired locks |
locktight.cleanup |
/chest lockpick [tier] |
Use lockpick on container |
locktight.lockpick |
/chest lockpickget [tier] [qty] [player] |
Get lockpick/reinforcement items |
locktight.lockpickget |
/chest itemset <tier|reinforcement|locktool> |
Save held item as shop template |
locktight.itemset |
/chest itemset clear <tier|reinforcement|locktool> |
Remove saved template |
locktight.itemset |
/chest adminlock |
Set admin lock |
locktight.adminlock |
/chest olock |
Set owner lock |
locktight.ownerlock |
/chest autolock |
Toggle auto-lock on place |
locktight.use |
/chest alerts |
Toggle lockpick alerts |
locktight.use |
/chest help [subcommand] |
Help |
— |
/chest bypass |
Toggle bypass mode |
locktight.bypass |
/chest update |
Check for updates |
locktight.update |
Permission logic notes
- Inspect:
locktight.use for own chests; locktight.bypass for any (inspection rules as implemented).
- Delete: Own chests with
locktight.use; bypass for non–owner-lock chests per plugin rules. Owner locks: owner only for delete. Admin locks: locktight.adminlock (or locktight.*).
- Open / break (normal locks): Owner/trusted;
locktight.bypass for non–owner-lock containers.
- Admin locks: Unpickable; open/break/delete for
locktight.adminlock / locktight.* as implemented.
- Owner locks: Only owner or chest-trusted players;
locktight.bypass and locktight.adminlock do not grant access. Use /chest trust on that chest; trustall / trustgroupall skip owner locks.
? TODO / future improvements
Planned features
- Fully modular tiers: Allow adding arbitrary new lockpick tiers purely from config without code changes (today, tiers are wired to specific shop keys and config paths;
/chest itemset already covers custom visuals and PDC-based detection for the existing tiers).
- Lockable doors (doors, trapdoors, etc.)
- Lockable redstone blocks (buttons, levers, pressure plates)
- Lockable ender chests
- More lockable variants (e.g. boat/chest minecart storage) where feasible
Implemented (no longer TODO)
- Lockable barrels
- Lockable shulker boxes (all colors)
- Lockable copper chests (1.21) and persistence across oxidation/wax
- Double chest from either side (lock, unlock, delete, trust, inspect)
- Paper & Folia support with region-safe scheduling
- Custom shop item templates (
/chest itemset, item_templates.yml, locktight.itemset)
- Lock tool (shop +
/chest itemset locktool): right-click lock/unlock, left-click inspect
- Configurable shop size (
shop_rows in gui.yml)
- Optional trusted-claim lockpick block (
griefdefender.block_lockpick_in_trusted_foreign_claim)
All suggestions welcome!
评论 0
登录后参与评分
还没有评论,来抢沙发吧