Tags
Creators
Details
6.1.0
Compatibility
Changes
- Added the ability to create/require a custom 'scythe' item, note that if this option is enabled, it will override the other tool options.
- Added command
/scythe-itemfor this, with permissionsscythe.itemandscythe.item.othersfor if someone should be able to send the item to another player - Config has a command cooldown, can be bypassed by having the
scythe.bypass.cooldownpermission
Please note that if you use the Custom Scythe item, old versions will continue to be valid even after you have updated the config. Checks are done on a tag on the item so the item cannot be faked, and old versions will remain valid. Currently the way around this for things like crates and stuff would be to use the /scythe-item <player> as a console command, but I will be trying to figure out a better solution for those things
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:SiaCYfuX:OHO2my59"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SiaCYfuX:OHO2my59"
}


