Links
Tags
Creators
Details
26.2-b1
Compatibility
Required content
Changes
VeryMcProto 26.2-b1(MC 26.2 线升级)
以纯 Paper 插件形式移植 Fabric 端协议 Mod(Servux / JEI / Syncmatica),面向 Minecraft 26.2 / Paper 26.2(Java 25)。dev/main 线已承载 26.2;26.1.2 转入维护对(ver/26.1.2 / ver/26.1.2-dev)。
升级要点(协议面零变化,可无缝换服)
- 协议面:对照上游八仓(masa 系
LTS/26.2七仓 + JEI26.2分支)26.1/26.2 两树逐文件字节级实证零变化——五通道协议版本 3/2/2/3/2、metadata 字段、C2S 类型集、DataTag 载体、malilib 16MB 重组上限、JEI 10 通道与配方转移算法全部逐字节相同;客户端门禁期待前缀随版本号变为servux-fabric-26.2,由版本注入链天然满足 - 构建面:dev bundle
26.2.build.129-stable;paperweight 2.0.0-beta.24;PacketEvents 2.14.0(2.13.0 起即支持 26.2,2.14.0 增 26.3);plugin.yml 的 api-version 模板化'${mcVersion}'(手写同步点消亡,随唯一版本来源展开) - NMS 漂移(编译驱动,126 个 NMS 触面文件仅 4 处错误,全修):
EntityType.PLAYER常量迁至新常量类EntityTypes;EntityType.create需EntitySpawnRequest;BlockTags.CONCRETE_POWDER→CONCRETE_POWDERS - Schema 数据版本表:servux 侧 +4 条 26.3 前瞻 + 枚举改名;syncmatica 侧 +8/−1(随上游删除
SCHEMA_26_1_RC1) - Paper 行为实证重核(26.2.build.129 dev bundle 源码直读):
CraftPlayer.sendPluginMessage的channels().contains门控、PaperCommonConnection.packetListener反射字段、handleUseItemOn1.0000001 逐轴校验、BlockPlaceEvent capture 时序——全部存活同构
验证
- test 113/113 全绿(19 测试类);
./gradlew build+ 版本注入终检通过(jar 内 plugin.ymlversion: '26.2-b1'/api-version: '26.2') - Paper 26.2(build 129)实机起服:
VeryMcProto v26.2-b1加载启用(api-version'26.2'两段式接受)、servux / JEI(mezz/JustEnoughItems 30.39.0)/ Syncmatica 三模块 + EasyPlace(PacketEvents 2.14.0 运行时)全部就绪、零 ERROR - 协议常量与载体均经 LTS-26.2 客户端源码逐字钉死;迁移方法论与全部实证记录见
docs/09-DELIVERY.md§26.2
产物
VeryMcProto-26.2-b1.jar —— Mojang 映射 jar(26.1 起无 reobf),标准 Paper 26.2 服务器放入 plugins/ 直接加载。需 EasyPlace(Tweakeroo 精确放置)时另装 PacketEvents 2.13.0+(可选,未装则优雅跳过)。
上一版本:v26.1.2-b5;旧版本线(MC 1.21.11):v1.21.11-b2。
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:bxTt86an"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tyOxCfUJ:bxTt86an"
}

