Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated 5 months ago
All versions
1.0.5
Release
Moon Spire 1.0.55 months ago 17
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
中文更新日志
调整内容
- 优化战斗单位条目布局与信息展示,生命、速度、头像和状态信息现在更清晰。
- 优化手牌、牌堆、卡组列表和卡牌预览的显示性能,减少大量卡牌或重复卡牌场景下的界面卡顿。
- 优化开发者中心在编辑大量卡牌、怪物和效果时的列表刷新与输入性能。
修复内容
- 修复联机和服务器环境下保存开发者中心自定义 PNG 资源可能不稳定的问题。
- 修复目标无效、手牌变化或服务端拒绝出牌时,客户端可能提前播放成功出牌动画的问题。
- 修复自定义 PNG 卡图在缩放、旋转或扇形手牌中可能溢出卡图区域的问题。
- 修复部分没有实际击退速度的战斗伤害仍播放击退偏移的问题。
- 修复战斗单位状态图标过多时,条目显示、提示框位置和鼠标判定可能异常的问题。
玩法系统
- 出牌表现现在以服务端判定结果为准;出牌失败时,卡牌会按失败流程返回手牌。
- 优化战斗状态层数变化反馈,获得或失去状态时会显示对应的增减提示。
界面与反馈
- 优化战斗单位列表显示,只保留当前存活单位,并改善指向目标时的列表滚动表现。
- 新增状态层数变化的世界反馈,并优化伤害、治疗、格挡和状态变化同时出现时的显示层次。
- 优化假死亡单位的战斗表现,倒下后会隐藏模型并播放短暂消散反馈,减少残留视觉状态。
- 优化本地 PNG 卡图、自定义卡面和战斗牌堆弹窗的加载表现,资源补齐期间仍会稳定显示已有卡牌内容。
开发者与整合包工具
- 提高单人、局域网和专用服务器环境下开发者中心自定义资源保存的一致性。
- 优化远程客户端自定义 PNG 的上传、保存和预览同步,降低联机编辑资源时的失败概率。
- 优化开发者中心大量效果行的输入框性能,滚动编辑时会保留未保存的输入内容。
- 优化卡牌和怪物搜索列表刷新性能,减少大量数据下的重复刷新开销。
技术实现
- 改善出牌结果确认、状态变化同步和开发者资源同步的底层处理,提高联机战斗与开发者中心保存稳定性。
English Changelog
Changed
- Improved combatant entry layout and information display, making health, Speed, portraits, and status information clearer.
- Improved display performance for hand cards, piles, deck lists, and card previews, reducing UI stutter with large or repeated card lists.
- Improved Developer Center list refresh and input performance when editing large card, monster, and effect sets.
Fixed
- Fixed unreliable saving of custom Developer Center PNG resources in multiplayer and server environments.
- Fixed invalid targets, changed hands, or server-rejected card plays potentially showing a successful card-use animation too early.
- Fixed custom PNG card art potentially overflowing its art area while cards were scaled, rotated, or displayed in a fanned hand pose.
- Fixed some battle damage feedback playing knockback movement even when no actual knockback velocity was produced.
- Fixed combatant entries with many status icons causing display, tooltip position, or mouse hit-detection issues.
Gameplay
- Card-use presentation now follows the server's final result; when a card play fails, the card returns to the hand through the failure flow.
- Improved feedback for battle status stack changes, showing clear increase or decrease indicators when statuses are gained or lost.
UI And Feedback
- Improved combatant list display so it only shows currently living combatants and scrolls more reliably when aiming at a target.
- Added world feedback for status stack changes and improved the display order when damage, healing, Block, and status changes appear together.
- Improved fake-death presentation so units hide their model after falling and play a short dissipating feedback, reducing leftover visual states.
- Improved loading behavior for local PNG card art, custom card faces, and battle pile popups, keeping available card content visible while resources finish loading.
Developer And Modpack Tools
- Improved consistency of Developer Center custom-resource saving across single-player, LAN, and dedicated-server environments.
- Improved upload, saving, and preview synchronization for custom PNGs selected by remote clients, reducing failures during multiplayer resource editing.
- Improved input performance for large Developer Center effect lists while preserving unsaved input during scrolling.
- Improved card and monster search-list refresh performance, reducing repeated refresh work with large data sets.
Technical
- Improved underlying handling for card-use result confirmation, status-change synchronization, and developer resource synchronization, improving stability for multiplayer battles and Developer Center saves.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:1CX6WnPt:RmQSqHTd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1CX6WnPt:RmQSqHTd"
}

