Flux Forge

Flux Foundry 0.7.0-beta.1 — Logistics Network

Your factory finally knows what it has.

Logistics Network introduces centralized inventory awareness and item requesting to Flux Foundry. Connect physical storage to a Logistics Controller, expose exactly what you want with Inventory Providers, and find and request items from across the network through the new Request Terminal. Pasted text

Added

• Logistics Controller

  • Creates a centralized index of connected, loaded Inventory Providers
  • Tracks available item quantities across the network
  • Rebuilds its index from actual storage rather than owning items itself
  • Detects multiple Controllers on the same network and safely enters Controller Conflict
  • Never force-loads storage chunks

• Inventory Provider

  • Intentionally exposes an adjacent inventory to the Logistics Network
  • Works through standard sided NeoForge Item capabilities
  • Supports all six source directions
  • Includes a 9-entry ghost filter
  • Supports whitelist, blacklist, and empty-permit filtering
  • Only explicitly exposed inventories become requestable

• Request Terminal

  • View items stored across connected Providers from one interface
  • Displays item icons, names, and aggregate available quantities
  • Case-insensitive item-name search
  • Sort by Name or Quantity
  • Ascending and descending sorting
  • Paging and mouse-wheel scrolling
  • Quick request presets for 1, 16, 32, and 64
  • Custom requests from 1 to 1,000,000 items
  • Nine real delivery slots
  • Shift-click requested items into your inventory
  • Clear full, partial, failed, unavailable, and conflict request states Pasted text

Network Requests

Request items stored anywhere in the loaded physical Logistics Network.

For example:

Search for Iron Ingot
Network shows 4,327 available
Request 64
The network finds valid Providers and delivers the items to the Request Terminal.

Requests can pull from multiple Providers to satisfy one request.

If 64 items are requested but only 23 actually remain when the transaction occurs, the Terminal delivers 23. The network never creates the missing 41 from a stale index. Pasted text

Physical Storage, Unified

Ordinary inventories can now become part of a searchable storage network without replacing them with proprietary storage blocks.

Attach an Inventory Provider only to the inventories you want exposed.

Chests, machine buffers, Stockkeeper inventories, and other storage sitting beside Item Pipes are not automatically indexed. Pasted text

Provider filters can further control what a shared inventory exposes to the network.

Built for What's Next

The Logistics Network uses a generalized StorageProvider architecture rather than hard-coding the Controller to chests.

Physical Inventory Providers are the first implementation. The architecture is designed so future storage and crafting systems can participate in the same Controller/index/request layer without replacing the network introduced in 0.7. Pasted text

Performance

The Logistics Controller maintains a bounded, non-authoritative inventory index rather than rescanning every connected inventory every tick.

A mandatory stress fixture tested:

• 128 Inventory Providers
• 4,096 occupied stacks
• 64 item types
• 1,200 measured ticks
• Maximum 1 Provider reconciliation/tick
• Maximum 32 inventory slots inspected/tick
• 0 topology rebuilds
• 0 full discovery passes
• 0 unintended chunk loads
• 0 chunk tickets Pasted text

Terminal search and sorting also caused zero Provider scans, inventory inspections, topology discovery, chunk loads, or tickets across 200 operations. Pasted text

Compatibility

• Existing 0.6.0-beta.1 worlds upgrade directly to 0.7.0-beta.1
• Existing inventories do not automatically become requestable after upgrading
• All previous Item and Fluid logistics behavior remains intact
• Smart Filters, Priorities, Round Robin, and Stockkeepers remain supported
• Existing power generation, processing, Steam, Wind, and FE systems remain compatible
• Standard NeoForge Item capabilities are used for Provider access Pasted text
• Existing Steam balance remains exactly 3,975 FE net per 1,000 mB cycle before Boiler fuel economics. Pasted text

Validation

• 159/159 tests passed
• All 113 previous tests retained
• 46 new FF-007 tests
• 0 failed
• 0 skipped
• Packaged graphical client passed
• Dedicated client/server passed
• Production-only server passed
• Actual 0.6 → 0.7 save migration passed
• Fresh-process persistence passed
• Actual Provider, Controller, and Terminal chunk unload/reload passed
• Partial-network fresh restart passed
• Request concurrency and stale-index safety passed
• Item component preservation passed
• Standard capability interoperability passed
• 0 unresolved S1 issues
• 0 unresolved S2 issues Pasted text Pasted text

Known Beta Limitations

• Item requests only; no Fluid requests
• Only loaded Providers are available
• One Controller per connected Logistics Network
• Inventory indexing is conservatively limited to 4,096 exposed slots per Provider
• No autocrafting yet
• No digital storage yet
• No wireless Request Terminal
• No cross-dimensional requests
• No global Stockkeeper reservation system
• No chunk loading
• Requests are immediate rather than persistent background jobs Pasted text

Requires Minecraft 26.3, NeoForge 26.3.0.33-beta, and Java 25.