1.1
Compatibility
Changes
New Events
playerCommand
-
Fires when a player executes a command.
-
Commands can be blocked, modified, or redirected.
playerDeath
-
Fires when a player dies.
-
Provides death message and killer information.
New Methods
PlayerCommandWrapper
getPlayerName()
returns the name of the player who typed the command
getCommand()
returns the command
setCommand(newCommand)
replaces the command before execution (the new command must include a "/")
cancel()
cancels the command
PlayerDeathWrapper
getPlayerName()
Returns the name of the player who died.
getUUID()
Returns the UUID of the player who died.
getDeathMessage()
Returns the death message.
getKillerName()
Returns the name of the killer if killed by a player.
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:gcqjSE77:YGMI56so"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gcqjSE77:YGMI56so"
}

