All versions
2.0.2
Beta
Axolostry 2.0.23 months ago 25
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Axolostry 2.0.2 focuses on expanding the breeding system, improving Vivarium gameplay, and refining hybrid management.
Added
- Added the new Offspring genetic system.
- Adult axolotls now have both Maximum Offspring and Remaining Offspring.
- Added a genetic Lifetime stat ranging from 120 to 210 seconds.
- Added detailed hybrid information when using the Magnifying Glass.
- Hybrid items now preserve their incubation progress when removed from a Vivarium.
Changed
- Parent axolotls are no longer consumed after breeding inside a Vivarium.
- Successful breeding now consumes one offspring from each parent instead.
- Maximum offspring is now limited to 5.
- Pink Axolotls crafted from a Bucket of Axolotl now start with 1–2 offspring.
- Adult axolotls gradually consume their lifetime while living inside a Vivarium.
- Multiple identical Vivarium modules can now be installed simultaneously, with their effects stacking.
- The Gene Stabilizer remains limited to one module per Vivarium.
- Crafting a Pink Axolotl now returns the Water Bucket instead of consuming it.
- Replaced the Magnifying Glass in the Analyzer recipe with an Amethyst Shard.
Fixed
- Fixed parent axolotls being removed after breeding.
- Fixed hybrid incubation progress being lost when removing hybrids from a Vivarium.
- Fixed offspring values exceeding the intended maximum.
- Improved compatibility with existing worlds by automatically clamping legacy offspring and lifetime values.
- Restored vanilla item comparison to improve compatibility with Applied Energistics 2 and Refined Storage.
- Fixed multiple breeding and Vivarium edge cases.
- Improved overall stability and data persistence.
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:WiTfOba5:72BIEwoZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WiTfOba5:72BIEwoZ"
}

