Tags
Creators
Details
1.0.0+26.3
Compatibility
Required content
Changes
1.0.0
SlotKit is MenuKit: Containers renamed, plus the slot code MenuKit 6 carried. It has its own version number and needs MenuKit 7.0.0 or newer, below 8.0.0. Mods built for Containers or for MenuKit 6's slot code need an update. The upgrading guide has the steps and an import map that rewrites the moved names.
Renamed
- The mod id
menukit-containersisslotkit, andcom.trevlar.menukit.containers.api.*iscom.trevlar.slotkit.api.*. SlotGroup, the created kind, isCreatedSlotGroup.ContainerKeys.MENDINGisBehaviorKeys.MENDING, andContainerKeysis gone.
Moved in from MenuKit
- Slot groups, categories and sets (
api.group),StorageandVirtualStorage(api.storage), the window, addresses, slot operations, gates and vetoes (api.window), andSlotGroupPanelAdapter.
Changed
- A server no longer refuses every player without SlotKit. It refuses only players missing SlotKit or a mod that declares
"bothSides": "required", and names the mods with links. Everyone else joins. - A mod that builds slots or custom menus declares
required, and namespaces its panel and menu ids with its own mod id.ContainerPanel.defineandCustomMenu.definethrow at startup otherwise, with a message naming the fix. - The join check also compares each required mod's
ContainerPanelslot groups and slot counts, and refuses a player whose copy differs, naming the mod. - Slot state carried on a shulker box is kept in
minecraft:custom_dataand stays off the network. Shulkers saved with Containers keep their contents and state.
Added
Presenceanswers what the other side runs:serverHasSlotKit,serverHasandserverHasChannelon the client,clientHasSlotKitandclientHason the server.
Removed
Address.panelandAddress.panelElement, the window's panel and element handles, and theVISIBILITYandOPACITYkeys. A panel's ownvisibleWhenandopaquedo the job.
Unchanged
- Every saved id keeps its
menukit:namespace. Worlds, player files and a mod's saved settings load with no conversion.
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:xQUBXV8I:ExS1HkwJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xQUBXV8I:ExS1HkwJ"
}

