Tags
Creators
Details
Licensed MIT
Published 6 years ago
All versions
4.0.0-neoforge
Release
CullLeaves v4.0.0 - NeoForge 1.21.12 years ago 217
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Changes
CullLeaves v4.0.0 for 1.21.1
- Many QoL improvements & Resourcepack features
- Add Malay and Malay (Jawi) translations
- Adjusted indents
- Update
ru_ru.json - Update
pack.mcmeta - 1.21 Port & Smart Azalea Leaves
- Automatically mark MidnightLib as dependency
- Fix CurseForge publishing
- Automatic upload using Unified Publishing
- Port to 1.20.4 & Migrate to NeoForge
- Zh_cn
- CullLeaves 3.2.0 - Mangrove Root Culling & Sodium fix
- Fix quilt.mod.json
- Update pack.mcmeta
- CullLeaves 3.1.0 - Update to 1.20
- Create vi_vn.json
- Add Traditional Chinese
- Stop game from launching with old Sodium versions
- Update to support Sodium 0.4.9
- I18n: zh_cn
- Update everything to 1.19.3
- Create uk_ua.json
- Fix random crashing with Sodium
- CullLeaves 3.0.0 - Forge support & better Sodium compatibility
- File size optimization
- Port to Architectury
- CullLeaves 2.3.4 - Update MidnightLib
- CullLeaves 2.3.3 - Update to 1.19
- Fixed wrong translations
- Update MidnightLib to 0.2.9
- CullLeaves 2.3.1 - Update MidnightLib and Gradle
- Remove leftover old MidnightConfig implementation
- CullLeaves 2.3.0 - MidnightLib, Brazilian & Russian Translations
- Add pt-br
- Add support Russian language
- Update to 1.17-pre1 (should also work on 1.17 Release)
- Cull Leaves 2.1.0 - MidnightConfig
- 2.0.0 - Config and Smart Leaves resourcepack!
- Rename to Cull Leaves
- Update README.md
- Rename to Cull Leaves
- Update README.md
- First version!
- Initial commit
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:GNxdLCoP:QbFPKni5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GNxdLCoP:QbFPKni5"
}
