v0.0.2

AE2 Federation 0.0.2 (alpha)

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

Upgrading from 0.0.1: the Processing rule no longer exists; a saved one is dropped on load. Check that each
Processing Endpoint's front and each Federation Pattern Provider's front (their Federation faces) point at the
domain side.

New: Federation Pattern Provider screen

• Right-click a Federation Pattern Provider to open its own screen. It has nine pattern slots, and each slot shows what its pattern makes, as in AE2.
• To map a pattern, drag its port onto an Endpoint, or click the pattern and then the Endpoint.
• Blocking mode, Lock Crafting, Pattern Access Terminal visibility and priority are set on the same screen.
• Endpoints owned by other Providers are shown read-only, with their owner and its patterns.
• Each Endpoint has its own return buffer. An Endpoint cannot be released while its buffer still holds results.

Processing Endpoint redesign

• The Endpoint's front is now its Federation face. Connect it to Federation Cable, a Router, or a Federation Pattern Provider's front.
  • Its other five faces connect a normal ME subnet with ordinary ME cable; no ME Interface is needed.
  • Machine results pushed into those faces, by the machine itself, a pipe or an Export Bus, return to the owning Provider.
• No rule is needed for processing. Any Federation Pattern Provider whose Federation face joins the same domain can map the Endpoint, and one Provider owns an Endpoint at a time.
• A native AE2 Pattern Provider on the Endpoint's Federation face uses it in Local mode.

Domain workspace (Router / Bridge)

• The policy page is now a topology view.
  • It has named networks, identity states and AE2 figures.
  • Each rule has its own switch, and rules with recent real deliveries are flagged.
  • It can show related domains read-only.
• Endpoints appear on the topology beside the network whose Provider maps them, along with the lane flow.
• The processing page maps patterns to Endpoints by dragging wires, many-to-many, for every Provider in the domain.
• Device locations are shown on a map tile or in 3D, and can be highlighted in the world.
• Federation screens use a fixed GUI scale and fill the window up to 1024×640.

Fixes and other changes

• A destroyed Federation Cable port no longer crashes the server tick after a chunk unload.
• Router faces are re-resolved when a native neighbour connects late.
• A Provider screen closes if its Provider is broken and replaced, so its patterns cannot be taken twice.
• Cable flow rendering is on by default.

Full Changelog: v0.0.1...v0.0.2