Craftwire 0.7.0

Craftwire for Minecraft 26.2 and 26.3 (Fabric client, Paper server).

Install

• craftwire-agent-fabric-0.7.0.jar: put it in your Fabric 26.2 or 26.3 profile's mods/ folder, next to Fabric API.
• craftwire-paper-0.7.0.jar: put it in your Paper 26.2 or 26.3 server's plugins/ folder. Development servers only.
• craftwire-api-0.7.0.jar: the API for adding your own tools from a plugin or mod (compileOnly, see docs/extensions.md).
• Claude Code: /plugin marketplace add uxplima/craftwire, then /plugin install craftwire@uxplima.
• Other AI clients: npx craftwire setup <client>.

New

• profile: samples a server's tick or a client's frame and names whose code uses the time: each plugin or mod, the listener and the event it handles or the scheduler task, the hot methods, and the tick times (average, p95, the slowest ticks). Mixins count for the mod that injected them.
• trace: times every call of a named method without changing any code (Java Flight Recorder method tracing): call counts, average and worst times, the slowest calls' stacks and the callers.
• client_eval: JavaScript on a client, like server_eval on a server. GraalJS is downloaded on first use and every jar is checked against a sha256 list; turn it off with allow-eval=false in config/craftwire.properties.
• Bots find their own path: move_to walks around walls, up steps, down drops, through doors and gates, up ladders and through water, never into lava or fire. path:false keeps the straight line. New actions: break_block (real dig time; says which plugin refused), jump, sneak, sprint, drop, swap_hands.
• MCP resources: the connected games, each game's log, a client's chat and a fresh screenshot, the grouped exceptions and the docs, with update subscriptions. Prompts: test_plugin, debug_lag, write_scenario, setup.

Changed

• move_to finds a path by default and waits up to 30 s (was a straight line and 10 s). Scenarios that relied on a bot getting stuck at a wall should pass path:false.