Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 years ago
Updated 5 months ago
All versions
1.0.5
Release
Forestry: Community Edition 1.0.52 years ago 553
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Required content
Changes
Forestry 1.0.5
- Fixed wild beehives not having particle effects
- Fix biogas engine lava tank accepting any fluid
- Fix still not working
- Added
forestry_fruitstag toforge:fruitsitem tag + fruit tags for each fruit added by Forestry:forge:fruits/cherryfor Cherryforge:fruits/walnutfor Walnutforge:fruits/chestnutfor Chestnutforge:fruits/lemonfor Lemon, the same tag used by Fruits Delightforge:fruits/plumfor Plumforge:fruits/datefor Dateforge:fruits/papayafor Papaya
- Replaced ICheckPollinatable and IPollinatable with new IPollenType API.
- A pollen type allows Forestry bees, butterflies, and Alveary Sieves to handle non-tree pollen types.
To use, register a new IPollenType in
IForestryPlugin#registerPollen.
- A pollen type allows Forestry bees, butterflies, and Alveary Sieves to handle non-tree pollen types.
To use, register a new IPollenType in
- Fixed bug where "default" variants of Forestry leaves would never be used
- Fixed bug where fruit ripeness would sometimes not persist
- ACTUALLY make saplings and other items usable in the composter (#35)
- Increase energy storage of Bottler, Still, Fermenter by 10x
- Fixed bug where species would be able to mutate with themselves.
- Add haploid breeding option
- Fixed nether biome climates
- Savannah biomes are now WARM/ARID instead of HOT/ARID, making their climate distinct from the desert biomes.
- Fix pipette textures
- Fix bees not planting flowers (#53)
- Fix bronze crafting recipe only producing 1 ingot instead of 4 (#54)
Supplementary resources
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:2oORTOi2:Y51tZAXc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2oORTOi2:Y51tZAXc"
}


