Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 months ago
Updated 2 months ago
All versions
1.2
Release
1.23 months ago 5
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client-side
Changes
After a ton of work, Runal 1.2 has received another update!
What’s new?
- Added a customizable Boss Bar Scale module.
- Added
/runaland/rucommands. - Added commands for opening the GUI, HUD Editor, Waypoints, and Team Tracker.
- Added commands for checking your ping, viewing enabled modules, toggling modules, reloading settings, and resetting layouts.
- Added built-in ScepterRPG keybinds for Warps, Class, Achievements, Pity, Shards, Player Vaults, Trash, AFK, Radio, Dance, Sigil Shop, Claim Luck, and Suicide.
- Organized keybinds into Activities, Ranks, and Safety sections.
- Added a confirmation system to the Suicide keybind to prevent accidents.
- Redesigned the Session, Performance, Event, Dungeon, Kill Counter, Armor, and Cooldown HUDs with matching bordered panels.
- Added a customizable color option for the Armor HUD.
- Improved HUD font sharpness and scaling.
- Widened the ClickGUI and improved spacing between settings.
- Made dropdown arrows larger and easier to see.
- Made long setting names fit properly without
.... - Shortened several labels, including Boss Defeat Counter to Kill Counter.
- Improved module, setting, section, and value-box font sizes.
- Added smoother, non pixelated color preview boxes.
- Made section separator lines use the full accent color.
- Made module setting sections start collapsed.
- Fixed the Hitboxes module rendering a massive blue line across the screen.
- Improved hitbox rendering so only actual players, mobs, and dropped items are outlined.
- Fixed search-bar text alignment and several other GUI spacing issues.
Design inspiration: Melinoe
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:WFnAtTj5:kdpuzi3V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WFnAtTj5:kdpuzi3V"
}

