0.2.2
Compatibility
Required content
Changes
โจ New HUD Styles โ six visual design languages for the Event Timer and Task panels: Classic, Glassmorphism, Neobrutalism, Neumorphism, Flat and Minimalism. Each panel picks its own style independently under HUD โ HUD Editor (Event Timer Panel / Task Panel). Highlights: Glassmorphism is a translucent frosted pane with a light edge and top sheen; Neobrutalism uses neon turquoise + neon yellow (thick border, hard offset shadow and the panel text); Neumorphism has soft extruded bevels; Flat is dark grey/black with a subtle accent bar; Minimalism drops the chrome down to a faint scrim. The background-opacity slider still applies, clamped sensibly per style.
๐ง Improved Task detection via /tasks list โ the Task Tracker now reads your Slayer/Adventure tasks from the /tasks list chat output instead of opening the /tasks GUI. No more GUI flicker, and it re-reads automatically on entering SkyBlock. Task world awareness โ Adventure gather/mine tasks now show the target world and only count blocks broken in that world. A generic "resources" task counts any block, while specific resources (Sandara Diamonds, Warped/Crimson Trees, Amethyst Cluster, and more) are matched by name. Task auto-refresh now also triggers when a task expires or when you skip one in the Task Point Shop, so the new task loads without checking manually. Fishing locations corrected โ Electric Eel now points to Tangleroot, one-word in-game fish names (e.g. Shulkercrab) are recognized, and the Wolfhaven spelling is fixed. ManaMod Presence โ the online endpoint now always returns every player, but anyone who disabled Show Me as ManaMod User no longer appears in the tab-list highlight. That toggle is back in settings (on by default).
๐งช Groundwork All SVAs menu โ custom textures โ the menu is now prepared to display custom item textures again automatically, the moment ManaCube exposes the item model in their SVA API. (Since Minecraft 1.21.4 custom textures come from the item_model component, which the API doesn't currently return โ so the menu can't rebuild them until that field is added.)
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:Nmj0sRES:cU4r1m0Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Nmj0sRES:cU4r1m0Q"
}

