Tags
Creators
Details
Licensed MIT
Published 10 months ago
Updated last month
All versions
1.6+backport.1.21.11
Release
No Crop Trample NeoForgelast month 45
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Server-side
Client and server
Changes
No Crop Trample 1.6 for Minecraft 1.21.11
The latest No Crop Trample, brought to 1.21.11. If you are updating from 1.0.0, this is everything that changed.
What's new
- NeoForge is supported. There is now a NeoForge build 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. In 1.0.0 any player could change them.
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
- Your existing settings are kept: same file,
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).
- Fabric needs Fabric API.
- Tested on Minecraft 1.21.11 with Fabric and NeoForge, on a server and in the game client.
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:zeddH1DK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5XlZRhM5:zeddH1DK"
}

