Tags
Creators
Details
All versions
0.7.0+mc1.21.11
Release
Magic Shulker Boxes 0.7.0 (Fabric 1.21.11)3 weeks ago 5
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
Magic Shulker Boxes 0.7.0
适用于 Minecraft 1.21.11 / Fabric / Java 21。
- 新增 Carpet 假人主手/副手自动补货,
carpetRefill=true默认开启;物品用完或工具损坏后先找普通背包,再从随身潜影盒补充,无需 IPN 或客户端。 - 消耗品保持组件一致,工具仅忽略耐久损耗。保留空瓶等使用余留物;堆叠盒需要独立拆分栏位,无法安全补货时不修改物品。主动丢弃、换手、切栏和不安全菜单状态不取物。
- 延续按字段许可与 UUID 个人设置。显式
playerEditableSettings清单保持原值;允许个人修改新选项时,可执行/msb admin permission carpetRefill true。新增个人快捷键默认未绑定,共 21 个布尔设置快捷键。 - 设置策略/偏好与 GUI 协议升至 v5,设置同步与图形界面需要两端升级;磁盘配置仍为版本 2,不重置已有配置。原理图
refill_v4、IPNrestock_v2与末影箱来源协议保持不变。 - 保留 0.6.1 的管理员玩家设置、聊天命令预览、容器/交易收纳、末影箱来源、原格工具回存及合成补货默认开启。
- 服务器部署工具支持两模组的五分钟检查与独立暂存;正式启用和重启由手动部署命令另行控制,CCO 只用于客户端分发。
English
For Minecraft 1.21.11 / Fabric / Java 21.
- Adds server-side Carpet fake-player main-hand/offhand refilling, enabled by default through
carpetRefill. Exhausted items or broken tools use loose backpack supplies before carried shulker boxes, without IPN or a client. - Consumables match all components; tools ignore damage only. Bottles and other use remainders are preserved. Stacked sources need a separate split slot; failed plans leave items unchanged. Explicit drops, swaps, hotbar changes and unsafe menus do not extract items.
- Retains UUID preferences and field permissions. Existing explicit
playerEditableSettingslists remain unchanged; use/msb admin permission carpetRefill trueto allow editing the new option. All 21 boolean preference key bindings default to unbound. - Policy/preferences and GUI channels use v5; both sides must update for settings synchronization and the GUI. Disk configuration remains version 2 without resets. Schematic
refill_v4, IPNrestock_v2and ender-source protocols retain their formats. - Preserves 0.6.1 administrator controls, clickable command previews, container/trade storage, ender sources, exact-slot tool returns and enabled-by-default crafting refilling.
- Server deployment tools support five-minute checks and isolated staging for both mods. Administrators control activation/restarts through the manual deployment command; CCO stays client-only.
See the user guide and release staging/deployment.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible 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:omzSygsa:O6h0wfLS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:omzSygsa:O6h0wfLS"
}
