1.0.0
Compatibility
Changes
/build – Enable or disable building for players.
/pvp – Turn player combat on or off.
/chat – Restrict chat access for players without permission.
/limparchat – Clear the in-game chat instantly.
/hardcore – Send players to spectator mode upon death.
/hardcorekick – Kick players from the server after death if needed.
/alternartell – Block or unblock private messages to command executors.
/stickkb – Give a knockback stick with customizable power.
/sticksharp – Give a sharpness stick with customizable power.
/reviver – Revive dead players in spectator mode.
/interact – Enable or disable player interactions like opening chests or using furnaces.
/manutencao – Activate server maintenance, kicking non-admin players automatically.
/rec comando [block | unblock] – Control which commands players can execute.
/rec chattag – Toggle team tags in chat.
/rec congelar – Freeze player movement (admins unaffected) and prevent midair abuse.
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:Pti4Q0Ey:nUysvZcw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Pti4Q0Ey:nUysvZcw"
}

