0.0.1
Latest
2026-08-05 · Keeping up with the new MCAgents
A compatibility release. MCAgents 6.0.0 changed how it decides whose key pays for a request, and instructions given by the server itself stopped working until now. Nothing you configure or command has changed.
Fixed Server-side instructions work again
- MCAgents 6.0.0 replaced the console account with a server one and now decides which API key a request spends from who the request is for. An instruction given by anything other than a player was still being billed to the old account, which no longer exists — so it came back as "no API token found" instead of being carried out.
- That affected
/npc tasktyped at the console, and anything a command block or a scheduled job set off. A player giving an NPC an instruction was never affected, and neither was any behaviour that needs no AI. - Those instructions are now billed to the server, which is exactly what the server's own key in MCAgents is for.
Changed The names are read, not remembered
- MCAgentsNPC no longer keeps its own copy of what MCAgents calls a player or the server. It asks MCAgents for those names when it binds, so a rename there can no longer quietly bill the wrong account here.
- An older MCAgents that does not offer them still binds, on the names this plugin assumed before — the integration degrades rather than refusing to start, exactly as it does for anything else it cannot find.
Note Upgrading
- Drop the new build in place of 0.0.0. There is no configuration change and nothing to migrate.
- If you run MCAgents 6.0.0 and want console or command block instructions to work, make sure MCAgents has a server key set. A server whose NPCs are only ever commanded by players needs nothing.
- Commands, permissions, behaviours, memory, and the two tools handed to MCAgents all behave exactly as they did in 0.0.0.
- The downloads are unchanged: the universal
MCAgentsNPCjar still detects your server at startup, and the three per-server builds are still published alongside it.