Links
Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
MenuKit 2.0.0
A re-architecture - simpler and more unified, not bigger.
Three unifications:
- ONE WINDOW. Creating a slot and interacting with it are now separate. One window interacts with anything addressable - a vanilla slot, a created slot, an element, a panel - the same way.
- One region placement + reactive sizing. Three placement systems collapsed into one; every panel now auto-fits the screen (wraps its width, scrolls its height) at any GUI scale. The old relative-verb placement and lambda anchors are gone.
- Inertness and opacity, system-complete: hidden is inert, a visible opaque panel blocks click-through, whatever it covers is inert - one law.
Plus an adaptive-layout foundation, widget-gallery fixes, HUD text folded into the core (wrapping) label, and an everywhere-default for injected panels.
Breaking: this is a clean API break - the old slot/placement API does not compile against 2.0.
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:R3BZelHc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3vGajyPr:R3BZelHc"
}

