v0.0.4

AE2 Federation 0.0.4 (alpha)

Minecraft 1.21.1 · NeoForge · AE2 19.2.9+ · LDLib2 2.2.34+. Install on both client and server.

Upgrading from 0.0.3: remote autocrafting works differently now (see below). Let running cross-network crafting
jobs finish, or cancel them, before you upgrade: a job started under 0.0.3 is not carried over. A Crafting rule
now always comes with the Storage rule in the same direction; worlds that have a Crafting rule without one gain it
on load. Processing Endpoints that a Provider uses now share that Provider's network's ME power with their subnet;
turn this off with the Endpoint's ME power switch.

Survival

• Every device can be crafted. The new Federation Logic Processor is pressed in AE2's Inscriber from a Logic Processor and Fluix Dust, and goes into the Bridge, Router, Federation Pattern Provider, Processing Endpoint and Federation Cable recipes.
• AE2's in-game guide has AE2 Federation pages in English and Chinese: getting started, how domains, rules and shared energy work, remote crafting and processing, troubleshooting by the screen's own messages, and one page per item.

Remote autocrafting, rebuilt

• With a Crafting rule, the requesting network's own crafting CPU plans and runs the job, using the other network's patterns and materials. The other network needs no crafting CPU.
• Each rule switch has three states: off, on, and on with re-export. Left click steps forward, right click back. With re-export, a network passes on what it gets: if A uses B, and B uses C with re-export, A can also craft with C's patterns and use C's storage.
• Turning Crafting on turns the same direction's Storage on, and Storage stays on while Crafting is.
• Results return only while the two networks are still linked; an output that arrives while the link is broken stays where it was made.

Storage

• When one storage of a network cannot be shared safely, only that storage is left out instead of the whole network, and the rule says how many were left out.
• An enabled rule that does not work says why in its tooltip.

Processing Endpoints

• A Processing Endpoint that a Provider uses powers its subnet from the Provider's network, as a Quartz Fiber does, so the subnet needs no power of its own. A switch in the Endpoint's panel turns this off.
• On the topology, an Endpoint's dot is green when usable, yellow when its Provider cannot use it yet (no power, or nothing connected behind it), and grey when no network uses it.
• Endpoint links leave a network's card side by side and never cross.
• A lane's flow shows items and fluids in their own units.

Federation screen

• Each rule direction is its own label beside the link, pointing at the network that uses it.
• Rule states read just Off, On or On with re-export; the colour says whether the rule works and the tooltip why not.
• The workspace uses AE2's own buttons, switches, text fields and scrollbars, and shows only what a player can act on.
• Switches no longer flash when you press one, and the footer no longer flashes "Saving…".
• Several world highlights can run at once and blink so the blocks stay findable.

Other changes

• Two Routers placed face to face link directly, without Federation Cable between them.
• Art assets are licensed under CC BY-NC-SA 4.0; the code stays AGPL-3.0.

Full Changelog: v0.0.3...v0.0.4