Moon Spire

中文更新日志

新增内容

• 新增塔附魔台。篝火房会生成附魔台，玩家可以在休整阶段消耗青金石为塔内卡组中的卡牌附魔。
• 新增青金石塔内材料，并加入默认材料体系和奖励来源。
• 新增 8 种可叠加卡牌附魔：锋利、火焰附加、破甲、忠诚、横扫之刃、保护、快速装填、耐久。

修复内容

• 修复塔附魔台使用原版附魔台方块实体校验时可能崩溃的问题。塔附魔台现在使用专用方块实体并保留原版书本动画。
• 修复开发者中心保存反馈可能先于服务端确认显示成功的问题。保存现在必须等待服务端确认，路线规则、怪物组容量、资源上传或写盘失败都会显示明确失败反馈。
• 修复被编辑的内置房间可能继续覆盖内置模板的问题。保存被改动的内置房间时会复制为自定义房间，并更新相关引用。

玩法系统

• 篝火房现在同时提供篝火、制卡台和附魔台。篝火、制卡台和附魔台都可以重复打开，房间只有在玩家按 N 主动确认后才会完成。
• 附魔台会为当前玩家卡组抽取最多 3 个可用附魔选项。同一房间重复打开会保持本房间选项，刷新选项或成功附魔后会重新抽取。
• 每次附魔消耗 1 个青金石，为 1 张适用卡牌叠加 1 级对应附魔；刷新附魔选项同样消耗 1 个青金石。青金石不足时不能附魔或刷新。

卡牌与牌组

• 锋利提高攻击伤害；火焰附加让攻击命中的目标获得烧伤；破甲提高攻击带格挡目标时的伤害；横扫之刃让单体攻击额外波及其它敌人。
• 保护提高卡牌获得的格挡量；快速装填在打出时抽牌；忠诚让本回合打出的牌有机会返回手牌；耐久让带消耗的牌抵消消耗。
• 忠诚和耐久在战斗中使用战斗副本等级。忠诚会在作用方回合结束时恢复到本场战斗基础等级，耐久不会自动恢复，战斗结束后这些战斗内消耗不会写回永久卡牌。
• 战斗中的卡组、手牌、抽牌堆和弃牌堆查看会显示当前战斗副本的实时附魔状态；已消耗的牌不再出现在战斗卡组视图中。

界面与反馈

• 新增附魔台界面，支持查看本次附魔选项、青金石数量、附魔说明，并从可适用卡牌列表中选择目标卡牌。
• 卡牌现在会显示紫色附魔行、动态附魔提示和附魔闪光效果，附魔后的基础伤害或格挡数值会在卡面上直接反映。
• 优化篝火房关键选择期间的返回逻辑。玩家从附魔台、制卡台等界面打开顶部背包、卡组、地图或暂停菜单后，关闭附加界面会回到当前关键选择。
• 优化制卡台界面和卡牌网格行为。制卡台只保留底部完成按钮，顶部卡组入口在战斗中会更稳定地切换或关闭当前卡组视图。

开发者与整合包工具

• 内置篝火房结构补放塔附魔台；缺失附魔台的默认篝火房在加载、保存或生成时会自动补齐。
• 默认材料新增 minecraft:lapis_lazuli 青金石，说明为用于制作卡牌与附魔的材料。
• 内置洞穴战斗房新增青金石战后材料掉落；内置宝箱房新增两条彼此独立的青金石宝箱材料掉落。
• 奖励配置中“概率掉多个”继续按多条独立掉落实现，每条概率独立掷骰；概率字段使用 0 到 1 的小数语义。

技术实现

• 卡牌附魔现在写入卡牌 NBT、网络同步、复制、渲染缓存和服务端战斗结算流程，确保永久卡牌和战斗副本状态分层处理。
• 服务端权威校验附魔台距离、当前选项、卡牌归属、附魔适用性和青金石消耗，客户端只负责展示选择与反馈。
• 开发者房间保存会正规化被编辑的内置房间并补齐缺失内置房间，减少旧房间覆盖、内置模板缺失或默认结构不一致造成的运行时差异。
• 开发者中心保存改为以服务端回执作为成功依据，并在保存失败时保留当前表单内容，避免失败保存误清空管理员正在编辑的数据。

English Changelog

Added

• Added the tower Enchanting Table. Campfire rooms now generate an enchanting table, letting players spend Lapis Lazuli during rest rooms to enchant cards in their tower deck.
• Added Lapis Lazuli as a tower material and connected it to the default material and reward systems.
• Added 8 stackable card enchantments: Sharpness, Fire Aspect, Armor Piercing, Loyalty, Sweeping Edge, Protection, Quick Charge, and Durability.

Fixed

• Fixed the tower Enchanting Table potentially crashing when vanilla enchanting-table block-entity validation was used. The tower Enchanting Table now uses its own block entity while keeping the vanilla book animation.
• Fixed Developer Center save feedback potentially reporting success before server confirmation. Saves now wait for the server result, and route-rule, monster-group capacity, asset-upload, or disk-write failures show clear failure feedback.
• Fixed edited built-in rooms potentially continuing to overwrite built-in templates. Modified built-in rooms are now copied into custom rooms and related references are updated.

Gameplay

• Campfire rooms now provide the campfire, Card Forge, and Enchanting Table together. All three can be opened repeatedly, and the room only completes when the player confirms completion with N.
• The Enchanting Table rolls up to 3 available enchantment options for the current player's deck. Reopening the same room keeps its options, while refreshing or applying an enchantment rolls new options.
• Each enchantment costs 1 Lapis Lazuli and adds 1 level of the chosen enchantment to 1 valid card; refreshing enchantment options also costs 1 Lapis Lazuli. Options and refresh are disabled without enough Lapis Lazuli.

Cards And Decks

• Sharpness increases attack damage; Fire Aspect applies Burn to attack targets; Armor Piercing increases damage against targets with Block; Sweeping Edge makes single-target attacks also hit other enemies.
• Protection increases Block gained from cards; Quick Charge draws cards when played; Loyalty can return played cards to hand this turn; Durability can prevent Exhaust on cards that would be exhausted.
• Loyalty and Durability use battle-copy levels during combat. Loyalty restores to the battle's base level at the acting side's turn end, Durability does not automatically restore, and these combat-only level changes are not written back to permanent cards after battle.
• In-combat deck, hand, draw-pile, and discard-pile views now show the current battle-copy enchantment state; exhausted cards no longer appear in the in-combat deck view.

UI And Feedback

• Added the Enchanting Table screen, including enchantment options, Lapis Lazuli count, enchantment descriptions, and a valid-card picker for the selected enchantment.
• Cards now show purple enchantment lines, dynamic enchantment tooltips, and enchantment glint, and enchanted base damage or Block values are reflected directly on the card face.
• Improved return behavior during campfire-room critical choices. When players open the top backpack, deck, map, or pause menu from enchanting or forging screens, closing the attached view returns to the current critical choice.
• Improved the Card Forge screen and card-grid behavior. The Card Forge now keeps only the bottom Done button, and the top deck entry more reliably toggles or switches combat deck views.

Developer And Modpack Tools

• Built-in campfire room structures now include the tower Enchanting Table; default campfire rooms missing the table are filled in during load, save, or generation.
• Added minecraft:lapis_lazuli as a default material, described as a material used for card crafting and enchanting.
• Added a Lapis Lazuli post-battle material drop to the built-in cave battle room, and added two independent Lapis Lazuli chest material drops to the built-in chest room.
• Reward configurations continue to represent "chance to drop multiple" as multiple independent drop entries, with each probability rolled separately; probability fields use decimal values from 0 to 1.

Technical

• Card enchantments are now included in card NBT, networking, copying, render caching, and server-side combat resolution, keeping permanent cards and battle-copy state separated.
• The server authoritatively validates enchanting-table distance, current options, card ownership, enchantment applicability, and Lapis Lazuli cost; the client only handles presentation and selection feedback.
• Developer room saves now normalize edited built-in rooms and append missing built-in rooms, reducing runtime differences from old room overrides, missing templates, or inconsistent default structures.
• Developer Center saves now treat the server acknowledgement as the source of truth and preserve the current form on failure, avoiding accidental loss of administrator edits after failed saves.