Tags
Creators
Details
7.0.0+26.3
Compatibility
Required content
Changes
7.0.0
MenuKit is a UI library only now. Everything about slots moved to SlotKit, a separate library built on MenuKit, and what 6.x deprecated is gone. Mods built for MenuKit 6 need an update. Upgrading to 7.0.0 has the steps, and tells you whether your mod needs SlotKit.
Moved to SlotKit
- Slot groups, categories, sets and
Storage(api.slot), the window, addresses, slot operations, gates and vetoes (api.window), andSlotGroupPanelAdapter. SlotKit keeps their saved text, so choices a mod saved stay valid. A mod that uses any of them adds SlotKit and changes those imports. - MenuKit no longer patches slot clicks, drops, hoppers, dispensers or the inventory. SlotKit does.
Removed
ControlStyleand its helpers, andstyle(ControlStyle)onButton,DropdownandDropdownMulti. They did nothing since 6.1.0. Delete the call.Tabs.SIDEBAR_SCROLLBAR_WIDTH. UseScrollContainer.TRACK_WIDTHon a container screen, 6 on an options screen.MKTooltip.MIN_WRAP_WIDTH. Nothing read it.- The window's panel and element handles and the
VISIBILITYandOPACITYkeys. A panel's ownvisibleWhenandopaquedo the job.
Changed
Declarationsmoved tocom.trevlar.menukit.api.Declarations. ItsrequireOpenis public, so a library built on MenuKit freezes its own declarations with MenuKit's.
Added
AnchorandAnchorPanelAdapterplace a panel around a rectangle a mod names and supplies on any screen, such as the pause menu's buttons. Panels on one anchor stack in its regions.api.host, for a library that ships its own screens.OwnHostlays out a screen's own panels and joins them to MenuKit's claims and draw order, andSlotScreenHookroutes hover and clicks to slots drawn in panels.
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:3vGajyPr:sFDpHwbh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3vGajyPr:sFDpHwbh"
}

