Included content
| Name | |
|---|---|
User Changes:
This update extends the expression syntax to support nbt and block properties.
nbt field to item stacks, entities and block entities.This Allows you to access NBT data like so: this_entity.nbt.Air. You should avoid NBT access, as it can get extremely slow.
properties field to *states.This can be used to access block state properties like so: block_state.properties.candles.
short_circuit to defaulted, all_of, any_of. If true, commands will terminate immediately upon the condition failing.hasContext and structContainsKey now accept VarArgs.Dev Changes:
runTriState to EventExecutors.| Name | |
|---|---|
| File | Type | Size | |
|---|---|---|---|
| commander-0.4.0-1.20.4-build.10-sources.jar | Unknown | 75.84 KiB |
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.
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:86bUtxWv:AeHVKpVl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:86bUtxWv:AeHVKpVl"
}