ВЕРСИИ (9)

Spigot version. The changelog is available below the Paper/Purpur 1.6.1 version.

# Changelog – v1.6.1 (21.10.2026) ## Added - Combined Upgrader stakes: players can stake Vault money and multiple item stacks in the same attempt - Expanded the player Upgrader input area to a 3×3 grid with nine independently valued item stacks - Added a custom **Add Money** prompt and a combined stake breakdown in the UPGRADE tooltip - Added configurable input stacking with `upgrader-settings.input-stack.enabled` (enabled by default) and `max-items` - Added durability-aware automatic item valuation, so damaged tools, weapons and armor are worth less than fully repaired items; this can be disabled in `config.yml` - Added custom Upgrader item registration with `/lc upgrader additem <id> <value>`, `/lc upgrader listitems` and `/lc upgrader removeitem <id>` - Added `reward-type: COMMAND` for explicit Upgrader profiles, with console execution and `{player}`, `{uuid}` and `{amount}` placeholders - Added a durable Upgrader transaction journal with recovery and review states for attempts interrupted by a restart - Added `/lc upgrader-review` for manual review of Upgrader transactions with uncertain cost outcomes - Added `/lc reward-review` to inspect and resolve command rewards whose delivery state is uncertain - Added `/lc perf` to report Upgrader animation timing and active case-session, task and visual-entity counters - Added core-aware update streams for Paper/Purpur and Spigot, plus update notices in the server console - Added JUnit regression tests for transaction recovery, custom item serialization, durability valuation, input-stack values, archive safety, storage recovery and snapshot ordering ## Changed - Reworked the player Upgrader GUI: stake details are consolidated into the UPGRADE tooltip, the main action uses a fixed Nether Star icon, and a glass divider separates the stake and target areas - Reworked the Upgrader cost editor to support combined Vault and item costs; item subtotals and money are included in the displayed total - Expanded `upgraders_cost.yml` with category-grouped default values, value-balancing guidance and custom-item instructions - Expanded `config.yml` comments and examples to explain storage, rarity weights, luck, Upgrader profiles, stack values, durability valuation and command rewards - Kept `upgraders: {}` empty by default and clarified the distinction between automatic value-based targets and explicit Upgrader profiles - Serialized YAML snapshots on the main thread and moved disk writes to an ordered background writer that skips stale pending snapshots - Added transactional switching between YAML and SQLite key/luck snapshots, including read-back verification, rollback copies and startup recovery for interrupted switches - Reduced repeated Upgrader animation geometry calculations and added performance counters for profiling - Renamed the admin entry to **Upgrader Profiles** to clarify that it edits profiles rather than placing world-based Upgrader points - Preserved compatibility with legacy `MONEY` and `ITEMS` profile cost settings and legacy animation aliases ## Fixed - Fixed backup entries overlapping action buttons in the Backup/Restore GUI; the list now uses a dedicated area with up to 21 entries per page - Hardened archive restore against path traversal, duplicate or case-colliding paths, unsupported files, oversized archives and suspicious compression ratios - Added staged archive validation for YAML, SQLite integrity and required data files before live data is replaced - Added rollback and interrupted-restore recovery for archive restores and safer recovery for corrupted configuration, history and storage files - Improved Upgrader crash recovery by journaling attempts before consuming the input and tracking uncertain cost application without issuing unsafe automatic refunds - Made pending reward delivery more resistant to duplicate queueing and interrupted item delivery by using stable IDs and delivery receipts - Routed command rewards with uncertain dispatch outcomes to manual review instead of blindly executing them again - Fixed a partial-stack inventory transfer edge case that could duplicate items when the player's inventory had insufficient space - Removed the obsolete Upgrader-use forwarding menu and an ineffective bundled example profile superseded by automatic target generation - Added connection cleanup and a bounded busy timeout for SQLite operations

# 🚀 LexCase 1.6.0 — Upgrader Update LexCase 1.6.0 introduces a completely new **Upgrader** system and expands the plugin with a dedicated risk/reward gameplay mechanic. ## 🎰 New — Upgrader System * Added a new **Upgrader** subsystem with dedicated core logic and GUI interfaces. * Added player-facing Upgrader menu accessible through: * `/upgrader` * `/lc upgrader` * Added configurable **ALL IN** upgrade attempts. * Players can put an item at risk and attempt to upgrade it into a selected target item. * Added configurable success chances for individual upgrade options. * Added configurable target multipliers such as `1.5x`, `2x`, `5x`, `10x`, etc. * Added configurable upgrade costs: * `FREE` * `MONEY` * `ITEMS` * Added **Vault** integration for money-based Upgrader costs. * Added support for multiple item costs per upgrade option. ## 📈 Automatic Upgrade Targets * Added `upgraders_cost.yml` for configurable item values. * Added automatic generation of upgrade targets based on configured item values. * Added automatic multiplier calculation for generated targets. * Added configurable chance calculation based on target value. * Added configurable minimum and maximum success chances. * Added support for custom Upgrader definitions alongside automatically generated ones. ## 🎰 New Roulette Animation Replaced the previous Upgrader presentation with a dedicated roulette-style animation. * Added a high-speed roulette spin with acceleration and deceleration. * Added multiple configurable full rotations. * Added dedicated WIN and LOSS zones. * Added a precision pointer represented by a single visible dot. * Added a visual circumference around the pointer trajectory. * Added a central display of the target item. * Added near-miss handling for failed attempts that stop close to the WIN zone. * Added configurable final wobble before the result. * Added final `WIN` / `LOSE` presentation. * Removed unnecessary intermediate result messages from the final animation. ### 👤 Player-Only Animation The Upgrader animation is rendered specifically for the player performing the attempt. Other players do not see the active Upgrader roulette animation. This keeps the animation personal to the player and prevents multiple simultaneous Upgrader sessions from appearing visually mixed together. ## 🔊 Improved Roulette Audio * Added continuous spin sound during the roulette animation. * Spin sound frequency dynamically follows the pointer speed. * Sounds are played more frequently while the roulette is moving quickly. * Sound intervals progressively increase as the roulette slows down. * Added dedicated success and failure sounds. ## ✨ Particle System * Added configurable particle detail levels: * `LOW` * `MEDIUM` * `HIGH` * Particle density can now be adjusted according to server performance and visual preferences. * Reduced unnecessary particle updates during animation. * Optimized roulette geometry rendering to reduce the number of particle operations. * Reduced repeated entity and display updates where possible. ## 🧰 New Upgrader Administration Added a dedicated administration workflow for Upgraders: * Upgrader list * Upgrader editor * Input item editor * Upgrade option editor * Result item editor * Chance configuration * Multiplier configuration * Cost editor * Animation configuration * Enable / disable controls * Custom Upgrader management ## ⚙️ Configuration Added dedicated Upgrader configuration options for: * Automatic target generation * Item value registry * Success chance calculation * Chance limits * Upgrade multipliers * Animation duration * Rotation count * Particle detail * Roulette geometry * Pointer position * Pointer visual settings * Spin sound behaviour * Near-miss behaviour * Final wobble * Result display timing ## 🛠️ Internal Improvements * Added a dedicated Upgrader service layer. * Separated Upgrader business logic from GUI and animation logic. * Added dedicated models for Upgrader definitions and options. * Added reusable cost and economy services. * Improved handling of configurable ItemStack-based upgrade results. * Added additional validation for Upgrader configuration values.

# Changelog – v1.5.0 (18.09.2026) ## 1.5.0 ### Reliability - Added persistent pending-reward delivery for failed/offline/full-inventory item rewards and failed command rewards. - Isolated reward delivery errors per roll so one broken reward does not stop subsequent rewards. - Added immediate durable flush when a pending reward is queued. - Added safe `/lc reload` semantics that preserve active sessions by default and an explicit `/lc reload force` path. - Made key consumption exact/atomic for normal case openings and hardened key arithmetic against integer overflow. - Hardened reward-weight arithmetic against integer overflow. ### Player experience - Added `/lc keys [ID]`. - Added `/lc rewards`. - Added `/lc history [ID]`. - Added persistent recent case history. - Added join-time retry for pending rewards. ### Admin experience - Added `/lc status`. - Added `/lc health`. - Added pending-reward count to the dashboard. - Added rarity pagination and editable numeric rarity tiers. ### Integrations - Added PlaceholderAPI placeholders for case-specific keys/open counts, total opens, Luck values and pending rewards. - Improved the Modrinth update checker to consider only listed release versions compatible with Paper/Purpur and the current Minecraft major/minor series. ### Data and migration - Added schema-versioned `history.yml` and `pending-rewards.yml` files. - Added atomic write + backup handling for the new files. - Added a one-time **1.4.x → 1.5.0** startup migration marker. - Added automatic timestamped pre-migration backups with SHA-256 manifests. - Added protection against starting on a newer unsupported LexCase data schema. - Existing 1.4.x key/luck data remains in its compatible schema; no destructive conversion is performed.

# Changelog – v1.4.0 (03.08.2026) ## Added * YAML remains the default storage mode, with SQLite available as an opt-in path * Safe locale migration that backfills missing keys without overwriting custom translations * `TextDisplay`-based holograms to reduce entity load on busy servers * Stacked loot summary output that merges identical drops into one line * Async export/import/restore flows with GUI progress feedback * Case templates for cloning full setups, including loot, visual settings, and conditions * Import/export presets for rarities and loot tables * PlaceholderAPI support for dynamic server placeholders * Admin audit log with a config toggle * Case geometry caching for chest positions, footprint, and space validation * Performance dashboard panels for active sessions, average session duration, entities per case, and storage size * Reload duration reporting in localized reload messages * Backup GUI slot fixes so backup entries no longer overwrite action buttons ## Changed * Storage keeps YAML as the safe default for existing 1.3.0 servers * Locale handling now merges bundled translations into existing user files instead of replacing them * GUI text now shows translated messages consistently after reload * Reward and backup operations now use debounce and async paths where appropriate * Case editing now supports template-driven cloning and preset-based transfer workflows * Hologram rendering now uses a lighter implementation for better server performance * Admin tooling now includes more detailed diagnostics and audit visibility ## Fixed * Locale keys that could fall back to raw IDs during migration * `gui.common.yes` / `gui.common.no` / `gui.common.true` / `gui.common.false` fallback handling * Reload language switching so `/lc reload` no longer requires a full server restart * Reward summary localization and stacked loot display * Backup GUI slot collisions * Storage-mode and GUI compatibility issues uncovered during build verification * Several API compatibility issues during the 1.4.0 rollout ## Notes * Paper 1.21.11 and Java 21 remain the target platform * YAML remains the default storage path for public upgrades from 1.3.0 * SQLite, audit logging, and advanced admin tooling are controlled upgrades rather than forced migrations

# Changelog – v1.3.0 (31.07.2026) ### Added * Added a new admin GUI workflow for browsing and editing cases. * Added direct case editor access with Shift + right-click on a placed case. * Added support for case-specific keys in `/lc givekey` and `/lc removekey`. * Added a dedicated admin menu entry via `/lc gui` and `/lc admin`. * Added new GUI permissions for admin access and direct editor access. * Added optional opening conditions that can require a permission to use a case. * Added `update-check` support in the main configuration. ### Fixed * Fixed command usage and permissions to match the current case/key workflow. * Fixed locale handling so translated text is loaded from language files consistently. * Fixed case storage and runtime data handling for setups, keys, and luck profiles. * Fixed the public README to reflect the current feature set and command structure. ### Changed * Changed the admin tool layer into a GUI-driven workflow. * Changed key management from generic player keys to case-specific keys. * Changed the command structure so key management now includes a case ID. * Improved configuration organization for cases, rarities, locales, luck, and debug settings. * Improved update notifications and general release clarity for server admins. ### Technical * Added new GUI infrastructure and editor menus for future admin tooling. * Expanded project structure with GUI, prompt, and menu listener services. * Improved maintainability by separating admin tools, menus, and core case logic.

# Changelog – v1.2.0 (28.07.2026) ### Added * Added strict configuration validation during startup and reload. * Added detailed diagnostics for invalid `rarities` and configuration entries. * Added automatic storage backups for `keys.yml` and `luck.yml` before saving. * Added storage schema versioning with support for future data migrations. * Added protection preventing players from opening multiple cases simultaneously. * Added spawn area validation before both case placement and case opening to prevent overlapping structures. ### Fixed * Fixed several issues that could break the automatic case opening sequence. * Fixed reward finalization edge cases caused by failed visual reveal states. * Fixed problems related to placing multiple case locations in close proximity. * Fixed locale configuration defaults and corrected language/fallback order. * Removed unnecessary development files from release archives. ### Changed * Refactored the case lifecycle into separate services for lifecycle management, visual handling, and reward finalization. * Improved overall project architecture, making the codebase easier to maintain and extend. * Updated the README to match the current configuration structure and localization system. * Improved reward summary output by merging identical rewards into a single message with the total amount for both players and the server console. * Improved update notifications by migrating them to Adventure Components with clickable links and hover text. ### Technical * Improved configuration safety by preventing invalid case configurations from silently using fallback rewards. * Improved internal storage reliability and preparation for future database backends such as SQLite. * Improved maintainability through cleaner service separation and stricter validation flow.

# Changelog – v1.1.0 (27.07.2026) - **Fixed**: Resolved several critical bugs and edge-case errors affecting stability. - **Fixed**: Patched an issue with data persistence under specific conditions. - **Changed**: Refactored the underlying architectural structure to improve code modularity and maintainability.