Links
Tags
Creators
Details
0.8.8b
Compatibility
Required content
Changes
-
重构模式注册与房间系统,统一模式扩展、地图编辑与数据同步接口
-
将僵尸模式拆分为独立附属模组,主模组保留团队竞技与战术团队竞技,可单独构建与运行
-
增加地图管理工具,支持查看地图信息、重命名、删除与强制结束对局
-
统一地图创建、复活点与区域编辑的工具操作,移除对应的旧编辑命令
-
增加图形化结束传送点设置,支持单张地图编辑与新建地图默认结束点配置
-
统一地图与规则的存档目录,重构旧地图存储检查与手动迁移命令
-
完善强制结束、玩家状态恢复与实体清理流程,支持离线玩家重新登录后继续恢复
-
优化地图删除流程,先结束对局并恢复、移出成员,再归档地图,增加删除进度查看、重试与取消
-
重写项目说明、操作指南与常见问题,同步至当前版本
-
Refactored mode registration and room systems, unifying interfaces for mode extensions, map editing, and data synchronization.
-
Split Zombies mode into a standalone addon, leaving Team Deathmatch and Tactical Team Deathmatch in the main mod, which can be built and run independently.
-
Added map management tools for viewing map information, renaming and deleting maps, and forcibly ending matches.
-
Unified tool interactions for map creation, spawn point editing, and region editing, removing the corresponding legacy commands.
-
Added a graphical interface for configuring end-of-match teleport destinations, supporting both per-map settings and defaults for newly created maps.
-
Unified save directories for maps and rules, refactor legacy map storage checks and a manual migration command.
-
Improved forced match termination, player state restoration, and entity cleanup, allowing restoration to resume when offline players log back in.
-
Improved map deletion to end active matches, restore player states, and remove players before archiving the map, with support for tracking deletion progress, retrying, and cancellation.
-
Rewrote the project overview, user guide, and FAQ to reflect the current version.
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:Pkr974dO:zh5dnopt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Pkr974dO:zh5dnopt"
}

