VitaminMCP

Documentation only — no behaviour changed, and nothing breaks. Two places told you to enable server settings nothing needs, which is worse than saying nothing: both widen what the server trusts for no benefit.

Fixed

The verification skill made three claims that no longer held.

• Bots were said to need settings.bungeecord: true in spigot.yml. They do not. That setting is the opt-in for a clientIp spoofing test, and enabling it otherwise only makes the server trust the forwarding handshake.
• agentTools was attributed to server_info. It comes back from session_start.
• The symptom of connecting too soon after a restart was named as an error that does not appear. A bot spawned before the Minecraft port is up fails with a connection timeout that names nothing.

The setup prompt announced three bot settings and listed one. online-mode=false is the one setting bots need.

Added to the skill

Tools it had never mentioned: bot_run_scenario and its steps, that a reused bot name is the player the server already remembers, bot_inspect's message cursor, bot_view, several named sessions at once, session_reset, and the player_state wait condition.

Full Changelog: https://github.com/Backas03/VitaminMCP/compare/3.0.0...3.0.1