Tags
Creators
Details
0.2.5-1.20.1
Compatibility
Required content
Changes
Changelog
Quality of Life Update – Advancements & Balance
This update focuses on progression clarity, balance tweaks, and quality-of-life improvements, while integrating content from the previous Datapack "Dive Over limits".
Added
Advancements (9 New)
Aroma Block Progression
A linear advancement chain guiding players through Aroma Blocks:
- Vitality – Obtain any Aroma Regeneration block
- Velocity – Obtain any Aroma Speed block
- Power – Obtain any Aroma Strength block
These task-type advancements introduce a clear progression path for Aroma usage.
Material Progression
- Phosphoric – Craft Phosphate Powder
- Super Fertilizer? – Craft Superphosphate
- Stellar Matter – Obtain a Nether Star Fragment
Encourages natural crafting progression from raw materials to advanced items.
Totem Progression (Challenge Advancements)
A higher-difficulty, end-game oriented chain:
- Resilient Spirit – Obtain a Totem of Regeneration
- Swift Spirit – Obtain a Totem of Speed
- Mighty Spirit – Obtain a Totem of Strength
Challenge frames highlight the rarity and importance of SubTotems.
Balance Changes
- Recipe tweaks across multiple items to improve balance and progression flow
- Adjusted crafting paths to better match early-, mid-, and late-game pacing
Removed
- Lore Music Disc
- Removed to reduce clutter and streamline progression focus
Integrated
- Added old recipes from the previous project
- Ensured all legacy content is fully usable and consistent with current systems
Summary
This update refines the overall experience by:
- Making progression clearer and more rewarding
- Reducing unnecessary or unfinished content
- Improving balance and usability
A solid foundation for future feature updates.
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:Iwg4G85t:NDMmtGxf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Iwg4G85t:NDMmtGxf"
}

