Tags
Creators
Details
1.2.1
Compatibility
Changes
AquaBreeder 1.2.1
Balancing & Progression Update
- Reworked Aqua Rod XP balancing and level progression.
- Catch XP now scales better with fish category, rarity, quality and Aqua Rod level.
- Improved fish category weighting: higher rod levels now find more Medium/Rare fish, while Starter fish still remain in the pool.
- Starter and Medium fish can now roll better quality and rarity more often with higher rod levels.
- Very Rare and Endgame fish remain special jackpot catches.
- Luck Surge has been rebalanced and now scales more carefully depending on fish category.
- Golden Hook has been reworked into a bonus-catch ability with a 50% chance to grant a second fish.
- Time Flow now reduces one active breeding slot by 5% of its remaining time, with a minimum of 2 minutes and a maximum of 15 minutes.
- Breeding quality has been rebalanced so perfect 100% fish are harder to obtain.
- Fish category now affects breeding quality progression.
- Improved Tempo talents: Reaktionsgefühl now visibly increases the green hit area, and Ruhiger Marker now noticeably slows the moving marker.
- Improved Energy Overload feedback and usefulness.
- Rare catch broadcasts are now stricter and only trigger for truly special catches.
- Sell GUI now has more space.
- Fixed aquarium fish getting stuck in locked slots after aquarium level changes.
- Added sound feedback when a breeding slot is finished.
- Fixed parent fish not refreshing their breeding usage immediately after claiming breeding results.
Important Note
Existing Aqua Rods may still show old XP/progression values in their lore after updating. The updated XP curve is fully reflected after the Aqua Rod reaches a new level or when a new Aqua Rod is created/given.
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:6jZH1hcP:hCIepqiO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6jZH1hcP:hCIepqiO"
}

