Flux Foundry 0.10.0-beta.1 — Changelog

Added

• Autocrafting Foundation.
• Recursive Crafting and Processing jobs.
• Recipe Drives with 16 recipe definitions each.
• Basic Server Hubs with 4 Recipe Drive bays / 64 total recipe capacity.
• Automatic Recipe Drive allocation.
• Crafting and Processing recipe programming.
• Ordered and unordered Processing inputs.
• Multiple Processing outputs.
• Modular Crafter Core and Basic Crafting Modules.
• Durable jobs, reservations, allocations, cancellation, and restart recovery.
• Powered Item Node operation.
• Platinum, Selenium, Nickel, Tin, Silver, Lead, and Chromium resource families.
• Silica and Silicon production.
• Basic Circuits.

Changed

• Item Nodes now require FE for Controller-commanded transfers.
• Industrial Terminal expanded with recipe programming, job management, and system diagnostics.
• Controller now supports recursive production planning and physical autocrafting execution.
• Existing-resource-first behavior uses stored materials before manufacturing shortages.
• Processing outputs must be physically produced by the selected machine.
• Crafter Core provides 1 lane; each Basic Crafting Module adds +1 lane.
• Baseline Crafter operation time is 20 ticks.
• Existing 0.9 Industrial Control factories migrate forward while retaining Node identities, commissioning, channels, and Data configuration.

Fixed

• Fixed stale Controller route caching during Data readiness transitions.
• Fixed incorrect partial-delivery accounting.
• Fixed cancellation handling for outputs between production stages.
• Fixed pending job ledger state being lost during certain save/restart boundaries.
• Fixed stale Processing routes after machine state changes.
• Fixed ordinary requests being able to take materials allocated to active Crafter jobs.
• Fixed empty connected Terminals incorrectly displaying Disconnected.
• Fixed several Recipe Terminal/Core GUI layout and status issues. 

Validation

• 336/336 tests passed.
• 285/285 previous tests retained.
• 51 new tests.
• 70/70 executable release gates passed.
• 15 fresh-process recovery boundaries validated.
• 0.9 migration validated across 195 block entities.
• No unresolved S1 or S2 issues.

Status: Release Candidate