Tags
Creators
Details
0.9.1+mc1.21.11
Compatibility
Required content
Changes
Magic Shulker Boxes 0.9.1
适用于 Minecraft 1.21.11 / Fabric / Java 21。
- 修复不同效果、延长版、增强版及自定义效果药水被判为同类盒的问题。药水、喷溅/滞留药水及药水箭始终比较完整药水内容和药效时长倍率。
- 同样保护可疑炖菜效果/时长、附魔书种类/等级、地图编号、烟花火箭/烟火之星内容、山羊角声音和不祥之瓶等级;不同关键内容不会自动收进同一个单类盒。
matchItemComponents=false默认保持。关键内容始终区分;开启“严格比较全部组件”后还要求自定义名称、普通装备附魔/耐久等其他组件一致。实际堆叠合并始终比较全部组件并保留原物品数据。- 拾取、容器转移、腾栏和丢出回收使用同一分类规则,修复预留回收绕过严格组件匹配的入口。已有混合内容盒保持原样,可继续取料,但不再作为单类收纳目的地。
- 保留 0.9.0 的同类盒优先收纳与独立空间不足提示。磁盘配置仍为版本 2,设置/GUI 协议仍为 v7,不新增字段、不重置已有设置。
- 覆盖真实药水拾取、箱子 Shift 转移、两种背包容量的真实客户端网络流程,以及全部关键类型与严格开关边界。
分类与严格开关的区别见使用说明。服务器与客户端来源由手动部署命令同步更新。
English
For Minecraft 1.21.11 / Fabric / Java 21.
- Fixes different potion effects, extended/enhanced variants and custom effects being classified as one storage type. Potions, splash/lingering potions and tipped arrows always compare complete potion contents and effect-duration scale.
- Also distinguishes suspicious-stew effects/durations, enchanted-book enchantments/levels, map IDs, rocket/star contents, goat-horn sounds and ominous-bottle levels. Different intrinsic payloads do not automatically share a single-type box.
- Keeps
matchItemComponents=falseby default. Intrinsic payloads always define the type; “Require identical components” additionally compares custom names, ordinary equipment enchantments/damage and all other components. Stack merging always compares complete components and preserves original item data. - Pickup, container transfers, relocation and drop recollection share the classification. Fixes reserved recollection bypassing strict component matching. Existing mixed-content boxes stay intact and remain extraction sources, but are skipped as single-type storage destinations.
- Preserves 0.9.0 matching-first storage and independent space notices. Disk configuration stays at version 2 and settings/GUI channels stay at v7, with no new fields or preference resets.
- Tests cover actual potion pickup, chest Shift transfers, real client/server flows with both free and full inventories, every intrinsic type and the strict-switch boundaries.
See the user guide for classification semantics. Manual deployment updates server and client sources together.
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:saIp4Na1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:omzSygsa:saIp4Na1"
}
