Skip to main content

Create Stock Bridge

Mod version shipped with FlammiCraft: 0.9.0

Create Stock Bridge by tom5454 connects Create logistics to Applied Energistics 2. This fork fixes transport, access and request persistence. Deutsche Anleitung.

Requirements and upgrade (0.5.0)

Requires the Create fork 6.0.21 or newer and AE2 Reforged 19.52.0 or newer. An adjacent Packager must face the bridge. Insertion, simulation, execution, crafting tracking and packaging are handled directly in the fork. Failed handoffs retain queued requests. Through 0.7.0 a returned stock summary was its own copy.

Since 0.5.0 the bridge reports only the stock actually stored in AE2. Items with an AE2 pattern no longer appear as infinite in the Stock Keeper, and Factory Gauges order again. Items that are not in stock can therefore no longer be ordered from Create to start an AE2 craft.

Requirements

Minecraft 1.21.1, Java 21, NeoForge, Create and AE2 are required. The build uses NeoForge 21.1.211 and tested local Maven publications of the Create fork 6.0.21 and AE2 Reforged 19.52.0. Mod metadata requires these versions or newer for the targeted crafting-planner integration; these declared ranges do not verify every combination. Other forks and newer dependencies need separate in-game acceptance.

Connect a bridge

  1. Craft an AE Stock Bridge. The supplied recipe uses a Create Stock Link, a Stock Ticker, an AE2 Interface, two Engineering Processors, two brass plates and two iron plates.
  2. Before placing it, hold the bridge and right-click a Stock Ticker on the desired Create network to bind it.
  3. Place the bridge and connect it to AE2. It requires a channel and an online, powered grid; the source sets idle consumption to 4 AE per tick.
  4. Place a Create Packager directly beside the bridge and arrange package transport. Create can request stored AE2 items through this connection.
  5. Right-click the bridge to edit its destination address. For delivery from Create into AE2, match the receiving Frogport address. The bridge's Ponder scene demonstrates the arrangement.

Create stock appears in AE2 as requestable or craftable items. These requests still require working package delivery; a displayed item is not proof that a delivery has completed. Small AE2 requests are accumulated until a stack is ready or no new request arrives for 20 ticks. A continuous small stream is sent after at most 200 ticks, checked once per second. AE2 co-processors still determine how quickly AE2 submits individual requests. Configured pattern priority is retained. When remote stock runs out in a missing-item calculation, AE2 can try a real production recipe next. This also covers AE2 Reforged's exact BigInteger planner. AELIS hands virtual bridge transport patterns to the protected native planner, keeping remote stock finite and reporting missing real ingredients. Unrelated recipe calculations retain their existing planner path. A virtual-only recipe keeps its missing-stock report.

Stock and deliveries from AE2

Since 0.8.0 the bridge keeps the stock summary while the amounts stored in AE2 stay the same. Factory gauges and orders read that summary. When an amount changes, the new summary is built in that same read, without waiting extra ticks. A caller that needs to edit a returned summary copies it first. The bridge's own delivery buffer stays a separate list.

Create only sees the stock actually stored in AE2. A pattern alone does not make an item visible or orderable in Create, so an item must be in stock to be delivered from AE2, for example through an order in the AE2 terminal. If an already accepted order runs short, for example because the items were taken in the meantime, the bridge tries to make the rest with a real pattern. This requires ingredients, an available AE2 crafting CPU and the normal processing machines; otherwise the delivery waits. Virtual transport patterns from other bridges do not count as production recipes.

The bridge menu displays pending delivery lines and an offline state. Cancel deliveries cancels outgoing bridge orders and their AE2 jobs. Dispatched packages remain in transit. Buffered items return to AE2 when storage space and power are available; until then, they remain in the bridge inventory. Create gauges can order again while demand persists. Cancelling at a gauge does not automatically remove the independent bridge order; use the bridge menu too.

Chunk unloading cancels calculations that have not yet been submitted to AE2. After loading, the bridge recalculates the remaining demand. Submitted AE2 jobs retain their saved link IDs; finished or canceled links do not block remaining deliveries. Failed calculations release their planning slots and retry after a short delay. Newly arriving stock is accounted for before more manufacturing is started. Cancellation remains available for a running AE2 job even if no delivery lines remain.

Sneak-right-click with a Create wrench to dismantle the bridge. This cancels its jobs and drops buffered items into the world. Stop package traffic first and collect the drops; after replacing the bridge, bind its network/address as needed.

Compatibility and access

The optional item adapter compiles against Create Factory Logistics 1.6.1. That mod is neither required nor bundled. Older versions are excluded by the declared minimum. Fluid transport and Refined Storage / RS2 are not implemented.

Multiple bridges on the same AE2 grid and Create frequency publish the inventory only once. Menu access, address changes and cancellation respect Create's network lock. The placer is saved and assigned to the AE2 node; existing network owners and locks are not reset. Old ownerless networks do not contain enough information to reconstruct a reliable owner.

Request Pattern is an internal virtual transport recipe. Players do not craft or use it. Its registry entry is retained for saved pattern data, while the c:hidden_from_recipe_viewers tag hides it in supporting recipe viewers. Hiding it is safe; do not remove its registration or saved pattern data.

Troubleshooting and saved data

Check the Create network binding, AE2 channel and power, adjacent Packager, package route and destination addresses when stock is missing. Redstone strength 15 disables the bridge's Packager connection. Edit the address in the bridge menu.

Order diagnostics are off by default. To troubleshoot, set debugOrderLogging = true in the server's config/createstockbridge-common.toml. Messages appear in the server log under Stock bridge at, at most once every 100 ticks per bridge. accepted confirms acceptance and rejected gives the reason for refusal. With extractable=0 and listed above 0, AE2 lists the item but does not release it. skipped means another bridge on the same grid and frequency handles the order. waits means an accepted order is currently getting no items from AE2.

Network, address, inventory and request data are stored in the world. Back up a world copy before version changes and watch outstanding deliveries. Existing inventory, network, address and AE2 request fields remain readable. Outgoing orders add new saved fields that an older version cannot understand. A downgrade is not a verified rollback: finish or cancel deliveries first and keep a world copy. Removing the mod from an existing world is not a verified rollback either.

Acceptance status

Source inspection and local artifact builds are recorded separately. Client and dedicated-server startup, both transfer directions, multiplayer menus, redstone, repackaging, Ponder and save/reload require manual testing on a copied world. A successful build does not establish those results.