Links
Tags
Creators
Details
Licensed Apache-2.0
Published 2 years ago
Updated 2 years ago
All versions
1.20.1-1.1.0
Beta
Botanical Machinery Extra 1.20.1-1.1.02 years ago 103
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
AFTER INSTALLING THIS VERSION, THE MECHANISMS MUST BE REINSTALLED
Added:
- New mechanism - greenhouse. Due to energy, flowers and fuel, allows you to generate mana in huge quantities. Supports 8 improvements at a time
- New improvements for the greenhouse. Added 16 improvements that are compatible only with the greenhouse.
- New improvement - Infinite tree.
- Added a new spark - basic. A regular basic spark, like in botania itself
- Added the ability to put an improvement on stone and wood in the last tier of pure daisy.
- Added support for the following mods: Applied Botanics Addon (For the greenhouse, which allows you to give mana directly to me. Optional), MythicBotany (Support for flowers in the greenhouse. Optional)
- Added mana cells for ME (Requires mod Applied Botanics Addon)
Changes:
- All mechanisms work from a different class => old mechanisms installed in the world will break.
- Changed the textures of improvements
- Complete redesign of the GUI.
- Phantom items in slots became darker
- When there is an improvement on infinite water, mana, the displayed bar shimmers
- Changed crafting of improvements
Fixes:
- Fixed upgrades that the rune altar accepted
- Fixed the load of pure daisy when it is in "rest".
- Fixed phantom blocks in oreflower when it contains an upgrade for stone generation.
- Fixed the ability to take mana from the mechanism through a spark. But it only works for sparks from botanicalextramachinery!! The basic spark from botania can still take mana from the mechanism. For this, a new spark was added with the same transmission as the usual one.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:tPTR9GcJ:2EFrJlHU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tPTR9GcJ:2EFrJlHU"
}

