Links
Tags
Creators
Details
Licensed CC0-1.0
Published 5 months ago
Updated 2 days ago
All versions
1.1.0-fabric-26.2
Release
CropXP Fabric 26.22 days ago 19
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Server-side
Client and server
Required content
Changes
CropXP 1.1.0
- Added server-authoritative configuration in
config/cropxp.json. - Added in-game configuration screens. Fabric uses Cloth Config; Forge and NeoForge use their native Mods-screen Configure buttons and vanilla widgets.
- Added
/cropxp configfor every loader. Singleplayer owners can edit every setting; dedicated-server settings are read-only in game and are changed inconfig/cropxp.jsonby the server owner. - Loader Configure buttons can edit the local
config/cropxp.jsonat any time, including from the title screen; these local settings never override a dedicated server. - Added configurable XP range, chance, Creative rewards, break rewards, right-click rewards, and automatic
CropBlockdetection. - Added per-block enablement, XP/chance overrides, and custom mature-state properties for modded crops.
- Added special handling for nether wart, cocoa, sweet berries, pitcher crops, and berry-bearing cave vines.
- Added right-click harvest rewards with mature-to-harvested transition checks and duplicate prevention.
- Added atomic configuration saves, backups, validation, unresolved-mod warnings, and revision conflict protection.
- Clients without CropXP can still join a CropXP server and receive its gameplay behavior.
- Added Fabric 1.21, Forge 1.20.1, NeoForge 1.21.1, and NeoForge 1.21.11 releases to the public matrix.
- Added Forge 1.21.1 and Fabric, Forge, and NeoForge releases for Minecraft 26.2.
License: CC0-1.0.
Optional dependencies
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:d3lKBDnb:lci05XyB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d3lKBDnb:lci05XyB"
}



