T3 Craft 0.4.0 — guided connections

Pair and recover T3 machines inside Minecraft without putting a pairing link into chat.

• New Connections screen opens automatically when unpaired, and is available from the panel or /t3 connections.
• Private paste-and-pair form hides the link from rendering, narration and copy/cut actions. Invalid or expired links show recovery guidance without echoing credentials.
• Per-machine health, retry, re-pair and confirmed local removal preserve the other machines' live sockets, focused conversation, drafts and pins. Wrong-owner replacement links are refused.
• Empty machines are recognized as connected. Late pairing and stale socket callbacks cannot restore a removed connection.
• Config replacements are created with owner-only POSIX permissions. Failed pairing/removal saves preserve active pairings.

Minecraft Java 26.3 · Fabric Loader 0.19.5 or newer · Fabric API 0.161.0+26.3 · Java 25 or newer. Add the jar to your Fabric profile's mods folder alongside Fabric API.

Source: a0b56079970b431eaf7a1b1d2f1f8de6dbc9f2e5. Exact-source CI passed on Java 25, including both T3 protocols, office persistence, MCP boundaries and launcher ownership.

The CI jar is byte-for-byte identical to the local jar that passed actual Minecraft setup, restart/late-pairing and shared-office workflows, plus read-only machine health and checkpoint review against T3 Code nightly 0.0.46-nightly.20261004.2644. A clean setup walkthrough also passed using the downloaded CI copy. These game runs used an isolated Fabric/Loom harness, not a conventional consumer launcher. Fresh real-T3 bootstrap pairing, other platforms and broader provider coverage remain unverified.

SHA-256 (t3craft-0.4.0.jar):

09362313a32d2a9704c26a12d8bff9337294e72766a674f05b680ad9a2a032a4

After publication, the anonymous jar download matched the CI artifact and checksum above. That public copy also passed actual checkpoint review and draft preservation through the unchanged Mac launcher, plus live MCP boundary checks. The launcher saved/stopped its own disposable world while preserving an independent server; all test processes were then stopped. The installed T3 nightly remained healthy.