LockTight

# 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). ```yaml # 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, **`g