VitaminMCP

Bots chat as players: the chat scenario step sends player chat instead of running /say, so plugins that read chat input receive it.

Existing scenarios run with the same arguments and get answers of the same shape, and the server plugin is the same as 3.2.0's apart from its version number. What the server sees from a chat step does change: player chat, where it used to see a /say command. A scenario that asserted on /say's broadcast, or on a command event for its chat, needs updating. A chat message that starts with / now fails the step instead of being said; send it with command.

Fixed

chat sends player chat. It used to run /say <message>. That never reached a plugin waiting for chat input, such as a shop asking for a quantity or a prompt asking for a name, and it failed for a bot without permission to use /say. The message now goes out as a player typing it, and the step waits until the server receives it, for up to timeoutMillis. A message a plugin consumes and cancels still counts as received, so check what the plugin did with assert_message or a state assertion.

When the server refuses the message, the step fails and shows what the bot was told. Offline bots have no chat signing key, so a server that requires secure chat can refuse them; use a Microsoft-account bot there.

Commands are signed when the bot can sign them. A Microsoft-account bot running a command that carries a message, such as /msg or /say, now signs it the way a player's client does.

Upgrading

Install as before; the server plugin can stay on 3.2.0 or 3.2.1.

The fix is @qsef1256's, in #5.

Full Changelog: https://github.com/Backas03/VitaminMCP/compare/3.2.1...3.2.2