Tags
Creators
Details
0.8.0+mc1.21.11
Compatibility
Required content
Changes
Magic Shulker Boxes 0.8.0
适用于 Minecraft 1.21.11 / Fabric / Java 21。
- 移除 MSB 的 Carpet 假人手持补货及工具损坏补货。假人统一使用 GCA,MSB 不再监听假人 tick/drop,也不提供对应设置、许可、命令、GUI 或快捷键。
- GCA 需同时开启
fakePlayerAutoReplenishment与fakePlayerAutoReplenishmentFormShulkerBox,后者负责潜影盒来源;来源顺序与补货行为由 GCA 控制。 - 旧版本 2 设置若含
carpetRefill或同名许可,先保存原字节.pre-0.8.0.bak,再只移除这些旧项。其余服务端、客户端和 UUID 个人设置保持原值;冲突备份和无效文件不覆盖。 - 设置策略/偏好与 GUI 协议使用 v6,需客户端和服务端同时升级;磁盘配置仍为版本 2。原理图
refill_v4、IPNrestock_v2和末影箱来源协议保持不变。 - 保留普通玩家的 IPN、原理图、合成补货、容器/交易收纳和 Carpet 堆叠盒兼容。其余 20 个布尔设置快捷键仍默认未绑定。
- 使用真实 Carpet/GCA 验证跨未满盒和第二盒连续放置铁砧;关闭 GCA 时 MSB 不自动补货。
GCA 开启命令和升级说明见使用说明。发布后定时任务可以下载暂存,正式部署及服务器重启仍由手动部署命令控制。
English
For Minecraft 1.21.11 / Fabric / Java 21.
- Removes MSB Carpet fake-player hand refilling and replacement after tool breakage, including tick/drop hooks, settings, permissions, commands, GUI controls and key bindings. GCA owns fake-player replenishment.
- Enable both GCA
fakePlayerAutoReplenishmentandfakePlayerAutoReplenishmentFormShulkerBox; the second enables shulker sources. GCA controls ordering and replenishment behavior. - Version-2 settings containing
carpetRefillor its permission are backed up byte-for-byte to.pre-0.8.0.bak, then only those retired entries are removed. Other server, client and UUID preferences are preserved. Invalid files and conflicting backups stay unchanged. - Policy/preferences and GUI channels use v6, requiring both sides to update. Disk configuration remains version 2; schematic
refill_v4, IPNrestock_v2and ender-source protocols retain their formats. - Preserves ordinary-player IPN, schematic and crafting refilling, container/trade storage and Carpet stacked-box compatibility. The remaining 20 boolean preference key bindings default to unbound.
- Real Carpet/GCA tests place anvils continuously across a partially used box and a second box. MSB does not replenish fake players when GCA is disabled.
See the user guide for GCA commands and upgrade details. Scheduled downloads can stage this release; manual deployment controls activation and restarts.
Optional dependencies
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:omzSygsa:I9Vco2h7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:omzSygsa:I9Vco2h7"
}
