ColonyLink v1.6.2 — Delivery modes, stability & translations

New — Delivery target (server / modpack setting)

Choose how ColonyLink delivers builder resources, set server-side in colonylink-server.toml under [delivery] send_target:

• BUILDER (default) — inserted straight into the Builder's Hut, bypassing the courier. The classic ColonyLink experience: fast and hands-off.
• WAREHOUSE — placed into the colony Warehouse instead; a MineColonies courier delivers to the builder. Slower, but keeps couriers relevant — great for balanced modpacks.

Set it once as a server owner or modpack author and it applies to everyone on the server — the delivery policy is authoritative and syncs to every client on join. In WAREHOUSE mode, sent resources show a greyed-out "Sent" line until the courier delivers, and tool substitution is disabled so couriers carry exactly what was requested.

Server admins: the config moved from COMMON to SERVER type — a fresh colonylink-server.toml is generated, so re-apply any custom values. Modpacks can ship defaults via defaultconfigs/colonylink-server.toml.

Improvements & fixes

• Shared Domum queue — queuing a Domum block now shows it on every Warehouse Link Terminal on the same network (shared cable, Quantum Ring…), survives relogs, and clears itself once the pattern is encoded.
• Priority Request no longer loops — fulfilling a builder's priority request (tool, armor, food…) now marks it "Sent" and waits for delivery instead of staying clickable.
• RF bar behaves correctly when the energy capacity is lowered below a wand's charge (no more over-100% / overflowing bar).
• No lost materials on a failed Domum craft — they return to the ME network.
• Broad stability and validation pass across all Clipboard and Terminal actions, and the Citizens tab is lighter on large colonies.

Translations

Now fully translated in English, French, Spanish, Russian and Chinese. Spotted a wording issue? Corrections welcome on GitHub or Discord.

Multiplayer: updating is recommended; run v1.6.2 on both client and server. The default builder flow is unchanged — existing setups keep working as before.