Links
Tags
Creators
Details
3.2.0+26.2
Compatibility
Required content
Changes
What's Changed
This update adds nested submenus, macros, and a lot of quality-of-life improvements to slot editing and the icon picker.
- Added nested radial menus: a slot can now open a submenu with its own slots. There's also an option to recenter the cursor when a submenu opens or closes.
- Added a "Run Macro" slot mode that chains several actions into one slot. A macro can mix chat messages, commands, keybinds, shortcuts, MaLiLib hotkeys and delays, and you can drag actions to reorder them. A new Stop All Macros keybind stops every running macro.
- Added an optional background blur when the radial menu is open, synced with the reveal animation.
- Added a tint color option for icons and glyphs.
- Added Copy, Paste and Reset buttons to the slot editor, so you can share slot setups through the clipboard.
- Added a "Recent" tab to the icon picker. Icons you pick show up there automatically, and you can right-click any icon to favorite it.
- Improved icon picker search and added hints to the slot editor's input fields.
- Added an "Optimize Radial Config" button that permanently removes leftover submenu and macro data from slots whose mode was changed.
- The config screen's live preview now shows the full activation area when the menu background is hidden.
- Added a cubic easing curve to the hover animation.
- Optimized rendering, and improved config validation and sanitization.
- Fixed the blur level resetting when switching submenus.
- Fixed the item icon tab's initial search not working.
- Fixed grid icon tabs not centering properly.
- Added Simplified Chinese (zh_cn) and Indonesian (id_id) translations.
Full Changelog: https://github.com/velolib/radial/compare/v3.1.0...v3.2.0
Optional dependencies
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:g52fu7eA:pMOutbvD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:g52fu7eA:pMOutbvD"
}

