0.3.0-1.21.11-Fa
Compatibility
Changes
RuneDelta 0.3.0
Released: Mar 9, 2026
This update introduces the new Rune Discovery and Mastery systems, major UI fixes, and expanded boss and progression mechanics.
Highlights
- Added Rune Discovery system with progressive rune reveal
- Added Rune Mastery and Rune Family Mastery skill trees
- Major Codex / Metrics / Builds UI fixes
- Overhauled boss loot systems for major vanilla bosses
- Added dimension and source-gated rune progression
- Multiple stability and crash fixes
Core Fixes
- Fixed RuneDelta advancement tab visibility and advancement trigger flow
- Fixed codex, builds, and metrics UI layout issues (wrapping, overlap, centering, scaling)
- Fixed mastery and family UI interaction behavior
- Reduced excessive rune tooltip and debug chat spam
- Fixed discovery and encryption display issues across Codex and metrics pages
- Fixed several crash scenarios tied to UI page rendering and corrupted jar edge cases
Rune Discovery & Codex Systems
Added a progressive rune discovery system.
- Undiscovered runes start obfuscated
- Reduced rune effectiveness while undiscovered
- Rune reveal progresses through activation usage
- Codex mirrors reveal state with progress counters
- Added rarity-based discovery targets (basic → top-tier)
- Added randomized reveal behavior (not strictly left-to-right)
- Added creative-mode override (fully revealed runes in creative)
- Added obfuscation support to metrics and recommended builds pages
Mastery Systems
Added new progression trees.
Rune Mastery Tree
Branches include:
- Discovery
- Power
- Acquisition
Rune Family Mastery Tree
Includes:
- Family progression page
- Set-bonus progression scaling
Additional improvements:
- Clearer branch and category structure
- Added progress indicators (x/x tracking)
- Improved unlock user experience
- Added detailed effect and multiplier descriptions
- Tuned mastery pacing to prevent overly fast progression
- Added ascended ranks for family mastery (rank 2 support)
- Set bonuses now scale with ascended family mastery
Boss / Raid / Crusader Changes
- Reduced big crusader raid size to better match legacy balance
- Reduced Warlord guaranteed fragment drop to 9
Boss Loot Packages
Major vanilla bosses now drop:
- 1 Legendary Rune
- 2 Utility Items
- 27 Rune Fragments (enough for infusing 3 runes)
Additional changes:
- Added weighted legendary rune pools per boss (Dragon / Wither / Warden)
- Added boss rune memory to prevent duplicate legendary drops
- Added boss-specific weighted utility drop tables
- Runebosses now despawn when the player dies
Beastmaster Improvements
- Fixed mount handling and hostility logic
- Updated spear material behavior across tiers
Rune / Item / Gameplay Adjustments
- Tightened mining fragment proc restrictions to intended tool scope
- Adjusted utility item and set bonus behavior for design parity
- Updated Cyberboots behavior
- Removed wind charge
- Fixed jump timing
- Fixed slow-fall behavior
Glint System Updates
- Stabilized glint behavior for intended targets
- Added fallback direction logic when rune interaction fails
World & Drop Progression
- Added dimension-based rune drop restrictions
- Added source-gated rune acquisition paths
- Boss
- Dungeon
- Dimension
- Endgame
- Added cypher gating for top-tier rune unlock paths
Advancements
- Added advancement coverage for mastery and family progression
- Added boss, mastery, and family advancement chains
- Fixed advancement schema issues preventing tab population
Stability & Packaging
- Hardened build and deploy workflow
- Added jar validation checks
- Improved logging and issue tracking
Version updated to 0.3.0.
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:zRt1M6RM:cwTSv2KD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zRt1M6RM:cwTSv2KD"
}

