Tags
Creators
Details
3.0.3
Compatibility
Changes
🇪🇸 Español
Se agregó el comando /npc equipment.
Uso principal:
/npc equipment <id> hand
/npc equipment <id> offhand
/npc equipment <id> auto [hand|offhand]
/npc equipment <id> boots hand
/npc equipment <id> main_hand hand
/npc equipment <id> boots clear
/npc equipment <id> clear
Ejemplo:
Si tienes unas DIAMOND_BOOTS en la mano y ejecutas:
/npc equipment <nombre del npc> hand
El objeto se colocará automáticamente en la ranura de equipamiento correspondiente del NPC.
🇺🇸 English
The /npc equipment command has been added.
Main usage:
/npc equipment <id> hand
/npc equipment <id> offhand
/npc equipment <id> auto [hand|offhand]
/npc equipment <id> boots hand
/npc equipment <id> main_hand hand
/npc equipment <id> boots clear
/npc equipment <id> clear
Example:
If you are holding DIAMOND_BOOTS in your hand and execute:
/npc equipment <npc name> hand
The item will automatically be placed in the NPC’s corresponding equipment slot.
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:QHFylrAf:VMkKe6g9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QHFylrAf:VMkKe6g9"
}

