Skip to content

2.1.0

Choose a tag to compare

@github-actions github-actions released this 22 Aug 19:16
· 42 commits to master since this release

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: 2.0.0...2.1.0