Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated 5 months ago
All versions
1.1.1
Release
Moon Spire 1.1.15 months ago 103
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
中文更新日志
新增内容
- 新增放弃登塔之旅按键,默认使用 R。玩家在塔内世界、路线图、卡牌奖励界面和塔内战斗界面都可以用它放弃整支队伍当前登塔之旅;普通非塔战仍使用 R 取消当前战斗。
修复内容
- 修复多人登塔中离线队员可能阻塞路线投票、奖励领取、战斗房触发、篝火恢复、战斗回合推进或目标选择的问题;当前只等待在线且仍属于跑局的队员。
- 修复全队离线后塔内战斗被清理时可能导致当前跑局丢失或怪物组占用未恢复的问题;成员重登后会按当前阶段继续。
玩法系统
- 塔内战斗房开战时,队伍现在会聚集到实际进入触发区的玩家附近,并使用服务端安全编队落点,而不是回到房间玩家出生点。
界面与反馈
- 优化地面单位受击击退表现,后退时会带有短促跳起观感;创造飞行玩家和空中、悬浮单位仍保持平滑位移。
技术实现
- 登塔等待集合改为只统计在线队员,并在登录、离线、投票、领奖、篝火和战后回调中统一推进等待状态。
- 放弃登塔由客户端发送请求,服务端权威结束整支队伍当前跑局并同步终止对应塔内战斗。
- 断线玩家不再参与战斗存活目标收集、快照发送和塔战结算阻塞,减少多人登塔断线后的卡死情况。
English Changelog
Added
- Added an Abandon Tower Run keybind, bound to R by default. Players can use it from the tower world, route map, card reward screen, and tower battle screen to abandon the current run for the whole party; regular non-tower battles still use R to cancel the current battle.
Fixed
- Fixed offline party members potentially blocking route votes, reward claiming, battle-room triggers, campfire recovery, battle turn progress, or target selection during multiplayer tower runs; these waits now only count online members who still belong to the run.
- Fixed the current run potentially being lost, or the selected monster group remaining consumed, when a tower battle was cleaned up after the whole party disconnected; returning members can continue from the current run stage.
Gameplay
- Tower battle rooms now gather the party near the player who actually entered the trigger area, using server-side safe formation placement, instead of returning everyone to the room player-spawn point.
UI And Feedback
- Improved grounded knockback feedback so ground units make a short hop while being pushed back; creative-flying players and airborne or hovering units still use smooth movement without the hop.
Technical
- Tower-run waiting sets now count only online members, with shared advancement handling across login, logout, voting, reward claiming, campfires, and post-battle callbacks.
- Abandoning a tower run is now requested by the client and resolved authoritatively by the server, ending the current run for the whole party and synchronizing any matching tower battle shutdown.
- Disconnected players are skipped for battle alive-target collection, snapshot sending, and tower-battle resolution blockers, reducing stuck states after multiplayer tower-run disconnects.
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:dnF3GsDQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1CX6WnPt:dnF3GsDQ"
}

