✨ LexCase
LexCase 是一款适用于 Minecraft 1.21.11 的可配置箱子与宝箱插件。它集成了虚拟钥匙、加权奖励、自定义稀有度、动画开启效果、长期运气系统以及游戏内管理员 GUI,并提供了备份和恢复玩家奖励的工具。
为服务器打造箱子,调整掉落表和开启序列,然后通过游戏内界面管理大部分设置,无需每次都要编辑 YAML 文件。
? LEXCASE — UPGRADER UPDATE

押注你的筹码。选定目标。转动轮盘。
LexCase 1.6.0 引入了升级器(Upgrader)。在 1.6.1 版本中,它已发展为一个更灵活的系统,支持组合筹码、自定义物品、指令奖励以及基于耐久度的物品价值评估。
- 3×3 输入网格中最多可容纳九个物品堆栈,外加可选的 Vault 货币贡献
- 根据
plugins/LexCase/upgraders_cost.yml 自动生成升级目标
- 基于耐久度的价值——受损的工具或武器价值低于完全修复的状态
- 自定义物品注册:支持包含名称、描述、附魔、模型数据、属性及受支持的 PDC 元数据的物品
- 针对特定升级器配置文件的指令奖励
- 可配置的成功几率、价值倍率和成本
- 仅限玩家的轮盘赌,具备加速、减速、速度自适应音效以及清晰的赢/输扇区
- LOW / MEDIUM / HIGH 粒子细节预设
使用 /upgrader 或 /lc upgrader 打开升级器。
结果在动画开始之前就已经计算完毕。轮盘仅为视觉效果;它不会改变配置好的几率。
? 升级器(The Upgrader)
升级器围绕全押(ALL IN)尝试构建。投入你的筹码,选择目标并启动滚动。如果获胜(WIN),你将获得选定的结果;如果失败(LOSE),所投入的筹码将被没收。
自动目标
LexCase 从 upgraders_cost.yml 读取相对物品价值并自动生成目标。你不需要为每次升级创建单独的配方或放置特殊的方块。
- 输入内容可包含最多九种不同的物品堆栈。
- 默认启用堆栈模式。堆栈的价值等于其单位价值乘以接受的量。
- 可以将 Vault 货币贡献添加到同一笔筹码中。一个货币单位在计算中计为一个价值点。
- 目标按价值倍率分组,并可在 GUI 中进行筛选。
- 成功几率是根据配置的价值关系和几率设置计算的。
- 可损坏物品的价值根据其剩余耐久度进行评估。不可破坏的物品不会因为磨损而打折。
upgraders_cost.yml 中的值是相对物品价值,而非直接的 Vault 收费。它们是服务器经济的起点,因此在将其用于紧密平衡的服务器之前,请审查生成的或捆绑的值。
自定义物品和配置文件
将主手物品注册为自动升级器物品价值:
/lc upgrader additem <id> <value>
/lc upgrader listitems
/lc upgrader removeitem <id>
你也可以通过 /lc admin → Upgrader Profiles 创建明确的配置文件。当你需要特定的输入、固定的几率、自定义结果、指定的成本或指令奖励(而非物品)时,配置文件非常有用。
自定义物品保存为序列化的 Bukkit/Paper ItemStacks。支持的元数据包括显示名称、描述、附魔、模型数据、属性和 PersistentDataContainer 数据。来自 MMOItems 或 MythicMobs 等插件的物品可能在它们的身份存储在 Bukkit/Paper 暴露的数据中时正常工作。如果插件将重要信息保存在私有或非便携式数据中,可能需要专用的适配器;在正式使用前,请在重启后测试有价值的自定义物品。
指令奖励
明确的升级器配置文件可以奖励配置的控制台指令,而不是物品。当玩家获胜时,指令会通过 LexCase 的待处理奖励系统进行排队。可用的占位符有:
{player} —— 玩家名称
{uuid} —— 玩家 UUID
{amount} —— 输入物品的数量
仅使用由受信任管理员配置的指令。由于外部指令可能会在服务器记录结果之前执行其操作,不确定的指令奖励可能需要手动审核,而不是自动重试。
轮盘动画
轮盘仅向尝试的玩家展示。它包含多次旋转、加速和减速、赢/输扇区、轮缘指针、速度自适应旋转音效以及最终结果显示。接近失败的呈现方式和粒子密度均可配置。
实际的成功或失败在动画开始之前就已决定。动画永远不会重新滚动或改变概率。
? 箱子和动画开启
使用 /lc setup 和管理员 GUI 在游戏内创建和管理箱子。
- 配置箱子外观和开启行为。
- 设置 Chest 计时、物品展示、奖励揭示延迟、全息图位置和开启超时。
- 设置开启条件和权限。
- 配置自动开启间隔以及同时开启/已开启箱子的限制。
- 允许对拥有指定权限的玩家跳过动画。
- 在不消耗钥匙的情况下测试奖励滚动。
- 通过管理工具克隆和管理箱子设置。
- 启用后,按住 Shift + 右键点击 已放置的箱子即可编辑。
箱子动画和计时是可配置的,因此你可以为轻量级设置使用快速开启,或为更复杂的宝箱使用较长的揭示时间。
? 奖励、稀有度和运气
根据服务器的运作方式构建奖励表。
稀有度可以拥有自定义名称、颜色、等级和权重。该系统不限于默认的四个等级;你可以定义额外的等级并调整它们与运气的交互方式。
奖励可包含具有自定义名称和描述、数量、价值及命令的 Minecraft 物品。您可以配置奖励概率以及传说级广播行为。
可选的运气与层级债务系统会追踪之前的结果,并调整未来的稀有度掷骰。您可以配置平衡上限、层级加成与惩罚、稀有度额外奖励的积累与衰减、债务的积累与衰减以及额外奖励的消耗。如果您偏好完全独立的掷骰,可以禁用此功能。
? 虚拟钥匙、奖励恢复与历史记录
钥匙以数字形式存储于每位玩家和每个箱子中。管理员可以发放、移除和检查特定箱子的余额。当开启需要多把钥匙时,LexCase 会原子性地扣除所需数量:要么扣除所有必需的钥匙,要么不扣除任何钥匙。
如果奖励无法立即交付——例如玩家离线或背包已满——它可以作为待处理奖励保留。玩家可以打开 /lc rewards 重试并领取待处理奖励。在 pending-rewards.enabled: true 的情况下,箱子奖励会在揭示之前被放入持久队列中。
使用 /lc history 或 /lc history <case-id> 查看最近的开箱记录。历史记录条目可包括箱子、稀有度、奖励、数量和 timestamp(时间戳),并提供累计开箱次数统计。
? 游戏内管理工具
大多数日常设置可通过 /lc admin 完成,包括:
- 箱子浏览器和编辑器
- 战利品表、奖励和稀有度编辑器
- 条件和视觉设置
- 升级器配置文件和选项/成本编辑器
- 测试模式
- 导入、导出、备份和恢复工具
- 运行时仪表板和诊断工具
- 可选的管理员审计日志
备份/恢复工作流在替换实时文件之前会验证归档路径和数据,并为支持的操作保留恢复副本。YAML 配置和快照使用更安全的文件替换方式,并对某些无效或中断的状态进行恢复处理。
? 状态、健康状况与性能
管理员可以使用以下命令检查插件的实时状态:
/lc status — 箱子、稀有度、奖励、钥匙、待处理奖励、活跃会话、存储模式和升级器数量
/lc health — 核心子系统的基本状态检查
/lc perf — 升级器动画计时计数器以及活跃的箱子会话、任务和实体计数
/lc perf 提供有用的运行时计数器,但不能替代完整的服务器分析器或长时间的压力测试。
? 存储与配置
YAML 是默认存储模式。 SQLite 可用于支持的玩家钥匙和运气数据。LexCase 包含数据布局迁移支持、原子文件替换、备份副本、归档导入/导出/恢复工具以及对重要数据文件的恢复检查。
主文件位于 plugins/LexCase/ 目录下:
config.yml — 常规设置、运气、存储、本地化、升级器行为及其他选项
upgraders_cost.yml — 自动升级器物品价值和注册的自定义物品
- 本地化文件 — 捆绑的英语和俄语消息
- 持久数据、历史记录、待处理奖励、迁移记录和备份
更新期间不会盲目覆盖现有的配置文件。在合并新选项或用较新的模板替换 upgraders_cost.yml 之前,请务必备份您当前的文件。自动缺失材料值仅为估算值;请根据您的服务器经济情况进行核对。
安全重载
使用 /lc reload 重新加载插件数据。当有箱子会话处于活跃状态时,正常重载将被阻止。仅在您故意希望在重载前结束活跃会话时,才使用 /lc reload force。
? 本地化与 PlaceholderAPI
LexCase 包含 en_US 和 ru_RU YAML 本地化文件。本地化更新会在保留自定义翻译的同时回填缺失的捆绑键值。
安装 PlaceholderAPI 后,LexCase 提供用于钥匙、开箱、运气、待处理奖励和运行时计数的占位符。示例如下:
%lexcase_keys_<case>%
%lexcase_case_opens_<case>%
%lexcase_total_keys%
%lexcase_player_total_opens%
%lexcase_player_luck_balance%
%lexcase_player_luck_tier_debt%
%lexcase_pending_reward_count%
%lexcase_active_sessions%
%lexcase_case_count%
%lexcase_rarity_count%
%lexcase_reward_count%
这些占位符可用于记分板、TAB 列表、全息图、菜单以及其他支持 PlaceholderAPI 的插件中。
? 更新通知
LexCase 会检查 Modrinth 上的兼容版本,并在游戏内和服务器控制台中通知管理员。更新程序使用 Modrinth 的加载器标签区分 Paper/Purpur 和 Spigot 分支,因此不会向其他分支提供特定平台的构建版本。标记为 bukkit 的版本以及没有加载器元数据的旧版本仍保持共享以确保兼容性。
⌨️ 命令
玩家
| 命令 |
描述 |
/upgrader 或 /lc upgrader |
打开升级器界面 |
/lc keys [ID] |
查看已存储的箱子钥匙 |
/lc rewards |
领取或重试待处理奖励 |
/lc history [ID] |
查看最近的箱子开箱记录 |
/lc help |
显示命令帮助 |
管理员
| 命令 |
描述 |
/lc setup |
在您所在位置创建或更新箱子设置 |
/lc delete |
删除您所在位置的箱子设置 |
/lc admin |
打开管理 GUI |
/lc givekey <ID> <player> <amount> |
发放特定箱子的钥匙 |
/lc removekey <ID> <player> <amount> |
移除特定箱子的钥匙 |
/lc status |
显示运行时状态 |
/lc health |
检查核心子系统状态 |
/lc perf |
显示升级器和箱子会话的性能计数器 |
/lc reload [force] |
重新加载配置和数据 |
/lc upgrader additem <id> <value> |
注册当前手持物品及其相对价值 |
/lc upgrader listitems |
列出已注册的自定义物品 |
✨ LexCase
LexCase is a configurable case and crate plugin for Minecraft 1.21.11. It brings together virtual keys, weighted rewards, custom rarities, animated openings, a long-term luck system and an in-game admin GUI, with tools for backups and recovering player rewards.
Build cases for your server, tune the drop tables and opening sequence, then manage most of the setup in-game instead of editing YAML every time.
? LEXCASE — UPGRADER UPDATE

Risk your stake. Pick a target. Spin the wheel.
LexCase 1.6.0 introduced the Upgrader. In 1.6.1, it has grown into a more flexible system with combined stakes, custom items, command rewards and durability-aware item values.
- Up to nine item stacks in a 3×3 input grid, plus an optional Vault money contribution
- Automatic upgrade targets generated from
plugins/LexCase/upgraders_cost.yml
- Durability-aware values — a damaged tool or weapon is worth less than a fully repaired one
- Custom item registration for items with names, lore, enchantments, model data, attributes and supported PDC metadata
- Command rewards for explicit Upgrader profiles
- Configurable success chances, value multipliers and costs
- Player-only roulette with acceleration, braking, speed-adaptive sounds and clear WIN/LOSE sectors
- LOW / MEDIUM / HIGH particle-detail presets
Open the Upgrader with /upgrader or /lc upgrader.
The result is calculated before the animation begins. The roulette is visual only; it does not change the configured chance.
? The Upgrader
The Upgrader is built around an ALL IN attempt. Put in your stake, choose a target and start the roll. On WIN, you receive the selected result; on LOSE, the accepted stake is lost.
Automatic targets
LexCase reads relative item values from upgraders_cost.yml and generates targets automatically. You do not need to create a separate recipe or place a special block for every upgrade.
- The input can contain up to nine different item stacks.
- Stack mode is enabled by default. The value of a stack is its unit value multiplied by the accepted amount.
- A Vault money contribution can be added to the same stake. One currency unit counts as one value point for the calculation.
- Targets are grouped by value multiplier and can be filtered in the GUI.
- The success chance is calculated from the configured value relationship and chance settings.
- Damageable items are valued according to their remaining durability. Unbreakable items are not discounted for wear.
The values in upgraders_cost.yml are relative item values, not a direct Vault charge. They are a starting point for your server economy, so review the generated or bundled values before using them on a tightly balanced server.
Custom items and profiles
Register an item from your main hand as an automatic Upgrader item value:
/lc upgrader additem <id> <value>
/lc upgrader listitems
/lc upgrader removeitem <id>
You can also create explicit profiles through /lc admin → Upgrader Profiles. Profiles are useful when you need a specific input, a fixed chance, a custom result, a chosen cost or a command reward instead of an item.
Custom items are saved as serialized Bukkit/Paper ItemStacks. Supported metadata includes display names, lore, enchantments, model data, attributes and PersistentDataContainer data. Items from plugins such as MMOItems or MythicMobs may work when their identity is stored in data exposed by Bukkit/Paper. If a plugin keeps important information in private or non-portable data, a dedicated adapter may be needed; test valuable custom items after a restart before using them live.
Command rewards
An explicit Upgrader profile can award a configured console command instead of an item. Commands are queued through LexCase's pending-reward system when the player wins. Available placeholders are:
{player} — player name
{uuid} — player UUID
{amount} — amount of input items
Only use commands configured by a trusted administrator. Because an external command may carry out its action before the server records the result, an uncertain command reward can require manual review rather than an automatic retry.
Roulette animation
The roulette is shown only to the player making the attempt. It includes multiple rotations, acceleration and deceleration, WIN/LOSE sectors, a pointer at the edge of the wheel, speed-adaptive spin sounds and a final result display. Near-miss presentation and particle density are configurable.
The actual success or failure is decided before the animation starts. The animation never rolls again or changes the probability.
? Cases and animated openings
Create and manage cases in-game with /lc setup and the admin GUI.
- Configure case appearance and opening behaviour.
- Set chest timing, item presentation, reward reveal delays, hologram positions and opening timeouts.
- Set opening conditions and permissions.
- Configure auto-opening intervals and limits on simultaneous/opened chests.
- Allow animation skipping for selected permissions.
- Test reward rolls without consuming keys.
- Clone and manage case setups through the admin tools.
- When enabled, edit a placed case with Shift + right-click.
Case animations and timings are configurable, so you can use a quick opening for a lightweight setup or a longer reveal for a more elaborate crate.
? Rewards, rarities and luck
Build a reward table around the way your server works.
Rarities can have custom names, colours, tiers and weights. The system is not limited to the default four tiers; you can define additional tiers and tune how they interact with luck.
Rewards can include Minecraft items with custom names and lore, amounts, values and commands. You can configure reward chances and legendary broadcast behaviour.
The optional Luck & Tier Debt system tracks previous results and adjusts future rarity rolls. Configure balance limits, tier boosts and penalties, rare-bonus accumulation and decay, debt accumulation and decay, and bonus consumption. Disable it if you prefer fully independent rolls.
? Virtual keys, reward recovery and history
Keys are stored digitally for each player and case. Administrators can grant, remove and inspect case-specific balances. When an opening requires several keys, LexCase consumes the required amount atomically: either all required keys are taken or none are.
If a reward cannot be delivered immediately — for example, because the player is offline or their inventory is full — it can be kept as a pending reward. Players can open /lc rewards to retry and claim pending rewards. With pending-rewards.enabled: true, case rewards are placed in the durable queue before the opening reveal.
Use /lc history or /lc history <case-id> to view recent openings. History entries can include the case, rarity, reward, amount and timestamp, with aggregate opening counts also available.
? In-game admin tools
Most day-to-day setup can be handled through /lc admin, including:
- Case browser and editor
- Loot table, reward and rarity editors
- Conditions and visual settings
- Upgrader Profiles and option/cost editors
- Test mode
- Import, export, backup and restore tools
- Runtime dashboard and diagnostics
- Optional admin audit log
The backup/restore workflow validates archive paths and data before replacing live files, and keeps recovery copies for supported operations. YAML configuration and snapshots use safer file replacement, with recovery handling for certain invalid or interrupted states.
? Status, health and performance
Administrators can use these commands to check the live plugin state:
/lc status — cases, rarities, rewards, keys, pending rewards, active sessions, storage mode and Upgrader count
/lc health — basic status checks for the core subsystems
/lc perf — Upgrader animation timing counters and active case-session, task and entity counts
/lc perf provides useful runtime counters, not a substitute for a full server profiler or a long-duration load test.
? Storage and configuration
YAML is the default storage mode. SQLite is available for supported player key and luck data. LexCase includes data-layout migration support, atomic file replacement, backup copies, archive import/export/restore tools and recovery checks for important data files.
Main files live in plugins/LexCase/:
config.yml — general settings, luck, storage, locales, Upgrader behaviour and other options
upgraders_cost.yml — automatic Upgrader item values and registered custom items
- Locale files — bundled English and Russian messages
- Persistent data, history, pending rewards, migration records and backups
Existing configuration files are not blindly overwritten during updates. Back up your current files before merging new options or replacing upgraders_cost.yml with a newer template. Automatic missing-material values are estimates; check them against your own server economy.
Safe reloads
Use /lc reload to reload plugin data. A normal reload is blocked while case sessions are active. Use /lc reload force only when you deliberately want active sessions finalized before reloading.
? Locales and PlaceholderAPI
LexCase includes en_US and ru_RU YAML locales. Locale updates backfill missing bundled keys while preserving custom translations.
When PlaceholderAPI is installed, LexCase provides placeholders for keys, openings, luck, pending rewards and runtime counts. Examples:
%lexcase_keys_<case>%
%lexcase_case_opens_<case>%
%lexcase_total_keys%
%lexcase_player_total_opens%
%lexcase_player_luck_balance%
%lexcase_player_luck_tier_debt%
%lexcase_pending_reward_count%
%lexcase_active_sessions%
%lexcase_case_count%
%lexcase_rarity_count%
%lexcase_reward_count%
These can be used in scoreboards, TAB, holograms, menus and other PlaceholderAPI-supported plugins.
? Update notifications
LexCase checks Modrinth for compatible releases and notifies administrators in-game and in the server console. The updater separates Paper/Purpur and Spigot streams using Modrinth loader tags, so a platform-specific build is not offered to the other stream. Releases tagged bukkit, plus older releases without loader metadata, remain shared for compatibility.
⌨️ Commands
Players
| Command |
Description |
/upgrader or /lc upgrader |
Open the Upgrader |
/lc keys [ID] |
View stored case keys |
/lc rewards |
Claim or retry pending rewards |
/lc history [ID] |
View recent case openings |
/lc help |
Show command help |
Administrators
| Command |
Description |
/lc setup |
Create or update a case setup at your location |
/lc delete |
Remove the case setup at your location |
/lc admin |
Open the admin GUI |
/lc givekey <ID> <player> <amount> |
Give case-specific keys |
/lc removekey <ID> <player> <amount> |
Remove case-specific keys |
/lc status |
Show runtime status |
/lc health |
Check core subsystem status |
/lc perf |
Show Upgrader and case-session performance counters |
/lc reload [force] |
Reload configuration and data |
/lc upgrader additem <id> <value> |
Register the held item and its relative value |
/lc upgrader listitems |
List registered custom items |
评论 0
登录后参与评分
还没有评论,来抢沙发吧