Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last week
All versions
1.6.0
Release
MidnightControls 1.6.0 - 1.194 years ago 8,733
Compatibility
Minecraft: Java Edition
1.19–1.19.2
Platforms
Fabric
Quilt
Supported environments
Client-side
Changes
This is a big one!
- Finally fixed camera choppiness (especially noticeable on low framerates, closes https://github.com/TeamMidnightDust/MidnightControls/issues/38)
- Asset improvements kindly contributed by @spudpiggy
- Use built-in 'scrollInHotbar' method by @TrueHorse
- Button tips now adjust properly to the scaled width of the window (closes https://github.com/TeamMidnightDust/MidnightControls/issues/95)
- Make 'Back' binding configurable (closes https://github.com/TeamMidnightDust/MidnightControls/issues/93)
- Add config option to disable the button in the controls screen (closes https://github.com/TeamMidnightDust/MidnightControls/issues/97)
- Add compatibility with the Inventory Tabs mod (closes https://github.com/TeamMidnightDust/MidnightControls/issues/100)
- Improve Emotecraft compatibility
- Add radial menu listing unbound keys (closes https://github.com/TeamMidnightDust/MidnightControls/issues/101)
- Fix disabling the HUD not hiding the tips in container screens (closes https://github.com/TeamMidnightDust/MidnightControls/issues/104)
- Fix 'Back' button not working correctly
- Fix recipe book not switching tab via shoulder buttons in Crafting Table and Furnace screens
- Support scrolling in Stonecutter
- Update to MidnightLib 0.6.1 (Several changes that make MidnightConfig screens more easily navigable using controllers)
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| midnightcontrols-1.6.0+1.19-sources.jar | Unknown | 179.66 KiB |
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:bXX9h73M:CTvplHoe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bXX9h73M:CTvplHoe"
}
