Links
Tags
Creators
Details
26.1.2-b8
Compatibility
Required content
Changes
VeryMcProto 26.1.2-b8(Carpet 模块铺开 + 三线文档体系重构)
以纯 Paper 插件形式移植 Fabric 端 Mod Protocol——协议投递型(Servux / JEI / Syncmatica)+ 行为注入型可移植子集(Carpet),面向 Minecraft 26.1.2 / Paper 26.1.2(Java 25,维护线 ver/26.1.2-dev → ver/26.1.2)。
本版内容(自 v26.1.2-b7 以来)
- Carpet 模块铺开至本线(0e278bc,61 文件原子交付):规则框架(
carpet.conf纯文本 + locked 语义)+/carpet四子命令(双层门禁)+ 18 条上游实名规则 + 假人/player全族(patches 三件套 + ActionPack + Paper Brigadier 树)+ carpet:hello 协议(HI = 上游 mod_version 逐字"26.1",禁发插件版本号)+/log日志框架(tps/mobcaps HUD 走 tab 脚、订阅跨会话持久carpet-logs.json双信号模型)+ 五条纯计算命令(/distance /info /perimeterinfo /draw /spawn)。- 本线适配 6 处:
EntityTypes常量回并、EntitySpawnRequest回退、HI 常量与字面锁、javadoc 锚点族等(对照上游 26.1 树同位形态); - 掉落伤害 per-line 决策(勿随 dev 线互抄):26.1.2 线 Paper 玩家物理敞开——假人掉落伤害经
EntityPlayerMPFake覆写isClientAuthoritative()返回 false 恢复全 vanilla 链(与 26.2 线手动驱动机制根本不同);survival 假人 40 格坠落致死实测(vanilla 公式 37 ≥ 20 血 ✓); - 移植范围终局定案:可完整等价子集全部实现完毕,其余面技术上不可能实现或无法等价,永不纳入。
- 本线适配 6 处:
- 三线文档体系重构(d1fc583 + c213af0 + 72feda8):NN- 编号 18 件重构为与 dev 线同构的模块子目录树 + 冻结归档(04/09/22/23);蒸馏归并(01+07+04+09 → architecture;09 §26.1 wire 真值 → servux/protocol §9;task 组 → schematic §9;22 七边 → syncmatica §10);31-carpet 单件拆分两件;版本字串策略三件套落库。
- 发版(f679090 + f8ef3eb):
buildNumber7 → 8(Carpet 铺开提交的预增位即发版位;首次发版提交误增至 9 已修正为 8)。
验证
./gradlew build全绿(含verifyVersionInjection);./gradlew test168/168 全绿(27 测试类,含 Carpet 7 类)- runServer 实机:四模块注册 + 假人全链(含 survival 40 格坠落致死差分)+
/carpet//log/五命令全判据通过 - 文档电池:旧路径引用零命中 + 全盘 .md 链接解析零断链;jar 内 plugin.yml version=26.1.2-b8 开箱复核
产物
VeryMcProto-26.1.2-b8.jar —— Mojang 映射 jar(26.1 起无 reobf),标准 Paper 26.1.2 服务器放入 plugins/ 直接加载。可选依赖 PacketEvents 2.14.0(仅 EasyPlace 需要,未装自动跳过)。
上一版本:v26.1.2-b7。
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:tyOxCfUJ:7i67YRTD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tyOxCfUJ:7i67YRTD"
}

