Tags
Creators
Details
2.1.0
Compatibility
Changes
command_exec now says why a command was not dispatched. It used to answer dispatched: false with an empty output for three different outcomes, and a caller could not tell them apart — including from a command that ran and did nothing, which looks identical. The player is told nothing either, not even "unknown command", so there was no way to recover the reason afterwards.
reason says |
What happened |
|---|---|
was refused before it executed, because ... does not have <node> |
The command exists and the sender may not use it. Grant the node, or op the bot |
this server has no command named '...' |
Nothing by that name. Check the spelling, or whether the plugin registered it |
nothing on this server answers to '...' |
Asked by a bot that is not op, where the two cannot be told apart. Run it as the console to settle it |
Nothing breaks — the field is additive. Minor rather than patch because for an MCP server the tool schema and description are the interface.
Full Changelog: https://github.com/Backas03/VitaminMCP/compare/2.0.0...2.1.0
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:6M4ubAZ5:S36dNPZf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6M4ubAZ5:S36dNPZf"
}
