Tags
Creators
Details
forge-1.20.4-0.3
Compatibility
Changes
0.3-1.20.1:
-
Neoforge release. Changes identical to those in the Forge version:
-
Improved the automatic dyeing (via hoppers) behavior at the Dyeing Station. Both - items required for dyeing and items created by the station - will now pass through the hoppers in stacks instead of one item at a time. This only applies to hoppers that are directly in contact with the Dyeing Station.
-
Change introducing ClientPlayerHelper for greater security against errors.
-
Added sound when some action failed related to tree/leaves
-
Removed unnecessary trigger
-
Fixed a bug that caused the following information to appear in startup logs: "Couldn't parse element loot_tables:grasses:blocks/*Block name"
-
Added new 'Additional Drop System' (as an extension of the above amendment) and consequently the Config File "additional_drops.toml". Which allows you to change or add additional drops to destroyed blocks. By default, adds BOP mod saplings if that mod is present (to solve the problem of the above error). However, supports any blocks and items, so it is easy to set an additional drop. More information: https://github.com/DanteTooMayCry/Grasses/wiki/Additional-Drop-System
-
Auto pruners without Silk Touch can now also mine (instead of only destroy) blocks like leaves and vines (not work for blocks from others mods, due to vanilla hard coded loot condition relating to shears as item instead of shears like items).
-
Auto pruners can be now used in Dispenser
-
Fixed resetting color case when change vines FERTILE state
-
Fixed drop appearing in creative mode when destroy blocks with automatic pruner.
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:IQUg4yhn:9L2Ie7of"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IQUg4yhn:9L2Ie7of"
}

