
SlideAway
SlideAway automatically hides your hotbar and shifts your health, hunger, XP, and armor bars down when you're fully safe full health, full hunger, not sprinting, no recent damage. The moment danger hits or you start moving fast, everything snaps back ins
1.0
Compatibility
Changes
SlideAway 1.0
Features
- Automatic hotbar slide-out after standing still and being safe for 10 seconds, the hotbar smoothly slides off the bottom of the screen
- Smooth bidirectional animation ease-out lerp in both directions; slide-out (~300 ms) and slide-back (~250 ms) feel natural and fluid
- Status bars shift down hearts, hunger, armor, and air-bubble bars slide down into the vacated hotbar space and remain fully visible
- XP bar stays aligned the experience bar moves down with the status bars, keeping the correct visual hierarchy
- Sprinting freezes the countdown running neither starts nor cancels the slide; the HUD stays hidden while you sprint and reappears only on real danger
- Scroll wheel & number keys bring the HUD back any hotbar slot change (mouse scroll or keys 1–9) immediately slides the HUD back up and restarts the 10-second countdown
- Danger auto-restore taking damage, losing health, or losing hunger instantly slides the HUD back up regardless of sprint state
Technical
- Built against the 26.1.x unobfuscated Mojang mapping set no
officialMojangMappings()needed - Uses Fabric Loom 1.16
splitEnvironmentSourceSets()all code lives insrc/client/ - Mixin targets confirmed via
javapbytecode analysis of the 26.1.2 client jar:Gui#extractHotbarAndDecorationsouter translate covering items + health bars + XP barGui#extractItemHotbarinner extra translate to push item slots fully off screen
- JOML
Matrix3x2fStack(pushMatrix/translate/popMatrix) replaces the legacyPoseStackAPI - Zero keybinds · Zero config files · Zero dependencies beyond Fabric API
Compatibility
| Dependency | Version |
|---|---|
| Minecraft | 26.1.2 |
| Fabric Loader | >= 0.19.2 |
| Fabric API | 0.145.4+26.1.2 |
| Java | >= 25 |
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:O0ERLUJP:EOJ6bkfu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O0ERLUJP:EOJ6bkfu"
}
