Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated 5 months ago
All versions
1.0.3
Release
Moon Spire 1.0.35 months ago 25
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
中文更新日志
调整内容
- 召唤物与分裂子体在出生时会继承召唤者或父体的水平朝向,减少生成后朝向突变。
修复内容
- 修复战斗中世界目标命中依赖滞后目标结果的问题,改为按战斗相机射线直接命中当前存活战斗单位。
- 修复目标被击退或移动后,世界中的鼠标指向、高亮和点击选中不能立刻跟随新位置恢复的问题。
- 修复旧 hover 蓝框可能残留,以及敌方或友方单位点击后黄色选中反馈不一致的问题。
玩法系统
- 玩家现在可以直接通过世界中的鼠标指向或左键点击来 hover / 选中当前存活目标。
- 敌方与其它玩家方或友方单位都可以保持黄色选中;本地玩家自己仍只显示蓝色 hover,不进入黄色常驻选中。
- 单体友方目标规则保持不变:不包含自己,拖牌目标合法性不改。
界面与反馈
- 条目区与世界实体的目标高亮反馈继续保持同步,蓝色 hover 与黄色选中的显示条件统一。
- 世界实体、目标条目与点击选中反馈在多人战斗里更一致。
English Changelog
Changed
- Summoned units and split offspring now inherit the horizontal facing of their summoner or parent when they appear, reducing abrupt facing changes on spawn.
Fixed
- Fixed world target detection in battle relying on stale targeting results; live combatants are now hit directly from the battle camera ray.
- Fixed world hover, highlight, and click selection not immediately recovering after a target is knocked back or moved to a new position.
- Fixed lingering blue hover outlines and inconsistent yellow selection feedback after clicking enemy or allied units.
Gameplay
- Players can now directly hover or select live battle targets through world aiming or left click.
- Enemies and other player-side or allied units can keep a yellow selection outline, while the local player still only uses blue hover feedback and never enters persistent yellow selection.
- Single-ally targeting rules are unchanged: self is still excluded, and drag-to-play target validation stays the same.
UI And Feedback
- Target highlighting stays synchronized between list entries and world entities, with unified rules for blue hover and yellow selection feedback.
- World entities, target entries, and click-selection feedback behave more consistently in multiplayer battles.
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:WAerIRpA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1CX6WnPt:WAerIRpA"
}

