## [1.1.4] - 2025-12-18

### Added
- **Bulk Trust Commands**: `/chest trustall <player>` & `/chest untrustall <player>` to manage trust across all owned chests at once. `/chest untrust all` command removes trusts for all players/groups on all owned locks
- **LuckPerms Integration**: Group-based trust management with four new commands:
- `/chest trustgroup <group>` and `/chest trustgroupall <group>` - Trust all players in a LuckPerms group
- `/chest untrustgroup <group>` and `/chest untrustgroupall <group>` - Remove trust for all players in a group
- **Clear Trust Commands**: Three new commands to clear trusts from a targeted chest:
- `/chest cleartrusts` - Removes all player trusts from the chest you're looking at
- `/chest cleartrustsgroups` - Removes all group trusts from the chest you're looking at
- `/chest cleartrustsboth` - Removes all player and group trusts from the chest you're looking at
- **Admin Bypass for Trust Commands**: Players with `locktight.bypass` permission can now trust/untrust on any chest they're looking at, even if they don't own it
- **Inspection Enhancement**: `/chest inspect` now displays trusted groups in addition to trusted players
- **Per-Player Auto-Lock Toggle**: New `/chest autolock` command allows players to toggle auto-lock on place for themselves, regardless of the global config setting. Preferences are saved to the database and persist across server restarts and player disconnects/reconnects

### Changed
- **Breaking Protection**: Chests now remain unbreakable even after being unlocked with `/chest unlock`. Breaking protection is only removed when chest metadata is completely deleted (e.g., via `/chest delete`). This prevents accidental chest destruction while still allowing access when unlocked. This also applies to lockpicked chests - they remain protected from breaking
- Updated command usage and tab completion for new subcommands
- Updated `messages.yml` with new messages and bumped version string to 4
- Added LuckPerms as a soft dependency
- Changed `general.auto_lock_on_place` default value to `false`
- Database schema updated to store per-player auto-lock preferences in `alert_preferences` table

### Fixed
- Fixed bug where `/chest delete` command wouldn't properly delete both sides of double chests, it now removes all metadata completely
- Verified and ensured all double chest handling logic is consistently implemented across all database operations
- Fixed update checker to properly handle dev versions - dev builds with higher base versions no longer show false update alerts, and dev builds will be prompted to update when release versions of the same base version are published. Also added support for dev-to-dev version comparison (e.g., Dev1a → Dev1b, Dev3b → Dev4a)
- Fixed edge case sometimes prematurely closing lock cache cleanup causing SQLite "closed pointer" console error during expired chest lock cleanup