Links
Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 9 months ago
Updated 3 weeks ago
All versions
Note: Configuration files from version 0.5.5b and earlier are no longer compatible with newer versions and must be removed manually, otherwise they may cause crashes. Starting from version 0.6.5b and later, installing the
0.6.5b
Beta
COD Pattern 0.6.5b7 months ago 149
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Changes
(cn)
v0.6.5b
- 迁入并整合 FPSM 核心、地图工具与复活点工具,地图与对局流程现可由模组内部统一维护
- 增加
frontline与teamdeathmatch双模式支持,战术团队竞技加入动态复活点候选与出生安全校验 - 增加
/cdp map地图管理命令链,支持地图创建删除、出生点管理、结束传送点设置与持久化保存 - 优化房间加入、离开、选边、观战回战斗、房间列表与玩家名单同步逻辑,并重构房间界面交互
- 调整局内 HUD 与对局表现,优化击杀播报、结算显示、敌我高光与敌方血条规则
- 增加武器黑名单与配件黑名单配置,并在背包改枪流程中对黑名单配件做安装过滤与保存拦截
- 增加房间内饱食度锁定机制,并全局禁用 TaCZ 原生改枪界面,统一改为使用 COD Pattern 背包改枪流程
(en)
v0.6.5b
- Migrated and integrated the FPSM core, map tools, and respawn-point tools, allowing maps and match flow to be maintained entirely within the mod
- Added support for both
frontlineandteamdeathmatch; tactical team deathmatch now includes dynamic respawn point candidates and spawn safety checks - Added the
/cdp mapmap management command chain, supporting map creation and deletion, spawn point management, end teleport point setup, and persistent saving - Optimized room join, leave, team selection, spectator return-to-battle, room list, and player list synchronization logic, and reworked the room UI interactions
- Adjusted the in-match HUD and gameplay presentation, improving killfeed, results display, friendly/enemy highlighting, and enemy health bar rules
- Added weapon blacklist and attachment blacklist configuration, with blacklisted attachments blocked during installation and prevented from being saved in the backpack gunsmith flow
- Added an in-room hunger lock mechanism, and globally disabled the native TaCZ gunsmith interface, fully replacing it with the COD Pattern backpack gunsmith flow
**###### 注意:0.5.5b与其旧版本配置文件不再适用于新版本,需要手动移除,否则有可能导致崩溃,自0.6.5b与其以后版本,不再需要安装fpsmatch模组作为前置依赖
Note: Configuration files from version 0.5.5b and earlier are no longer compatible with newer versions and must be removed manually, otherwise they may cause crashes. Starting from version 0.6.5b and later, installing the fpsmatch mod as a required dependency is no longer necessary.**
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:MryiGJZ1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Pkr974dO:MryiGJZ1"
}

