Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 years ago
Updated 2 months ago
All versions
14.1.0
Release
autoswitch 14.1.07 months ago 21.5K
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Changes
14.1.0
- Fix an error when writing data to the config file
- Remove unnecessary
ORstatements from the default config - Allow eliding
type=<enchantment|item>intoolslist, offhand selectors, andenchantmentsdefinitions - Fix usage of neoforge-replaced way of getting item enchantments
- Add a default target for ores
- By default, prefers pickaxes with fortune over those with silk touch, unless the player is crouching, in which case the opposite occurs with silk touch being preferred.
- Ported Fabric API's "Client Tags" module to Neoforge
- Now conventional tags (eg
c:ores) will work when connecting to a vanilla server from a Neoforge client
- Now conventional tags (eg
- Fix Neoforge update url
- Add
Playerdata type, mostly to support things like the mace-
Usable in any
IdSelector(anywhere you can have adataentry) -
Supports the same sort of value comparison as Enchantment Levels
-
Example
target { type=BLOCK id="obsidian" data { player { isCrouching = true distance { GREATER = 2 } } } } -
Currently Available Entries
Type Description Type isFlying If the player is flying Boolean isCrouching If the player is crouching Boolean isPassenger If the player is riding something Boolean isOnGround If the player is on the ground Boolean isSprinting If the player is sprinting Boolean distance The distance between the player and target Number fallDistance The distance the player has fallen Number hasItem If the player has the given item ExpressionTree hasHotbarItem If the player has the given item on their hotbar ExpressionTree
-
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:uSdcnlts:szkb6Aqu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uSdcnlts:szkb6Aqu"
}

