Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 3 days ago
All versions
1.6+backport.1.20-1.20.4
Release
No Crop Trample Fabric3 days ago 24
Uploaded by
Compatibility
Minecraft: Java Edition
1.20–1.20.4
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
No Crop Trample 1.6 for Minecraft 1.20 – 1.20.4
The latest No Crop Trample, brought to 1.20 through 1.20.4. This is the first release for these versions, so everything from earlier releases is included.
What's new
- NeoForge and Forge are supported. There are now NeoForge (1.20.4 only) and Forge (1.20.1 only) builds next to the Fabric one.
- Empty farmland protection. Unplanted farmland no longer turns back into dirt when you walk or jump on it. This is on by default; turn it off with
/nocroptrample empty offor in the config screen. - Stems count as crops. Farmland under pumpkin and melon stems, including a grown stem with its fruit, is treated as planted.
- Modded crops work. Crops from other mods that use the standard crops tag are recognized as planted.
- Only operators can change settings.
player,mob,emptyandreloadneed permission level 2. Anyone can still look at the current settings with/nocroptrample status.
Fixes
- A damaged config file no longer crashes the game; the mod falls back to the default settings.
- Options missing from an older config file are switched on instead of ignored.
Good to know
- The config file is
config/nocroptrample.json. - The mod works on the server. Installing it on clients is optional and only adds the config screen (Mod Menu on Fabric, the Mods list on NeoForge and Forge).
- Fabric needs Fabric API. Java 17 is required.
- NeoForge is supported on 1.20.4 only; NeoForge 1.20.2 and 1.20.3 are not. Forge is supported on 1.20.1 only (Forge 47.1 or newer).
- Tested on Fabric 1.20, 1.20.1 and 1.20.4, NeoForge 1.20.4 and Forge 1.20.1 servers, and played in game on Fabric 1.20.1 and 1.20.4, NeoForge 1.20.4 and Forge 1.20.1. 1.20.2 and 1.20.3 share the same code but were not tried one by one.
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:5XlZRhM5:XVWKTY2J"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5XlZRhM5:XVWKTY2J"
}

