Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 2 weeks ago
All versions
1.2.0
Beta
Cyber-Cultivator-Bio-Synthesis 1.2.02 weeks ago 25
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Updates
- Added variants of deep slate silicon ore and rare earth ore
- The condenser now consumes glass bottles to produce purified water; the inventory limit is 16 bottles
- Added the optional bilingual Patchouli biosynthesis research manual
- Four machines now feature redstone control modes (Ignore/High/Low) and three-stage comparator outputs
- Added Forge IItemHandler facet automation capabilities and semantic tags to four machines
- Refined breeding culture formulas and the serum quality inheritance chain
- Configuration files have been moved to the
serverconfigdirectory and are now saved with the world archive
Fixes
- Fixed an issue where the S-02 visual enhancement outline was visible to other players
- Fixed an issue where the source of the ‘Neural Overload’ effect was missing and where effects from different serums were cross-linked
- Fixed an issue where client configurations were not synchronised with the server
- Fixed an issue where NBT quality information was missing from matured products in cultivation slots
- Fixed an issue where the JEI recipe page did not match the actual crafting results
- Fixed an issue where
clearRemovedcaused a server deadlock during block loading - Fixed an issue where ‘Neural Overload’ was still triggered after the effects of other mods had been removed
- Fixed an issue where the S-02 outline target persisted after a player’s death and respawn
- Fixed an issue where progress was not triggered when right-clicking to collect a spliced offspring whilst in stealth mode
- Fixed an issue where deep slate ore lacked the Forge ore tag, resulting in it not being recognised by other mods
- Fixed an issue where filling multiple slots of a filling machine with the same type of raw material caused an automation deadlock
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:L51LrAgb:Z3wqXeTS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L51LrAgb:Z3wqXeTS"
}

