Flux Forge Dev Pack

Flux Foundry DevPack

Build it. Power it. Pipe it. Automate it.

Flux Foundry DevPack is the official development and testing modpack for Flux Foundry, an industrial technology and factory-automation mod built around physical logistics.

The pack provides a ready-to-play environment for experiencing the latest Flux Foundry systems without having to assemble a testing pack yourself.

Generate power, process resources, build Steam systems, configure machine I/O, create Item and Fluid logistics networks, commission computer-controlled factories, and eventually teach your factory how to manufacture requested Items automatically.

Flux Foundry's philosophy is simple:

Automation should make your factory smarter—not make the factory disappear.

Items still need somewhere to come from. Machines still need power. Pipes still need routes. Factories still need to be engineered.

The Controller just teaches everything how to work together.

---

DevPack 0.4.0

This version features:

Minecraft 26.3
NeoForge 26.3.0.48-beta
Java 25
Flux Foundry 0.10.1-beta.1

The pack also includes JEI to make exploring recipes and materials easier.

Flux Foundry 0.10.1 contains the complete Autocrafting + Industrial Material Foundation introduced in 0.10, now ported to NeoForge .48-beta with no intended gameplay or balance changes.

---

What Can I Do?

Flux Foundry currently provides several layers of factory progression.

Power

Build electrical infrastructure using systems including:

• Coal generation
• Solar generation
• Wind generation
• Geothermal generation
• Steam generation
• Energy storage
• Energy Cables

Flux Foundry uses standard NeoForge FE and is designed to interoperate with compatible power systems.

---

Industrial Machines

Turn raw resources into useful materials using machines such as:

• Crusher
• Powered Furnace
• Alloy Smelter
• Boiler
• Steam Turbine
• Condenser
• Water Pump

Machines support configurable faces, allowing you to decide where Items, Fluids and Energy enter or leave.

---

Industrial Logistics

Move resources around your factory with:

• Item Pipes
• Item Extractors
• Fluid Pipes
• Fluid Extractors
• Steam Pipes
• Energy Cables
• conduit Bundles
• configurable channels

More advanced logistics can use:

• filters
• whitelists and blacklists
• priorities
• Balanced routing
• Round-Robin routing
• Stockkeepers

Flux Foundry currently supports 17 independent channels, allowing nearby networks to remain separated even in dense factories.

---

Industrial Control

When ordinary pipes aren't enough, build an Industrial Control system.

The major components are:

Controller — the brain of the factory.

Data Lines — carry commands and control information.

Item Nodes — powered interfaces that execute Controller-directed Item movement.

Industrial Terminal — lets the player interact with the controlled factory.

One rule is especially important:

Data does not transport resources.

An Item Node needs all three:

Control + Power + Physical Route

If it has Data but no Item Pipe route, nothing moves.

If it has a route but no Controller connection, nothing moves.

If it has both but no FE, nothing moves.

---

Quick Start Guide

Step 1 — Build a Power System

Your machines and active control hardware need FE.

Start with an appropriate generator and connect your equipment using Energy Cables.

As the factory grows, power demand grows with it.

A machine being connected to the network does not necessarily mean your generators can supply enough power to operate everything simultaneously.

---

Step 2 — Start Processing

The Crusher and Powered Furnace are important early processing machines.

One particularly important progression is Silicon.

Flux Foundry does not add Silicon Ore.

Instead:

1 Sand → Crusher → 1 Silica

then:

1 Silica → Powered Furnace → 1 Silicon

Silicon is one of the foundations of Flux Foundry electronics.

---

Step 3 — Make Basic Circuits

The current Basic Circuit uses:

1 Silicon + 2 Copper + 2 Redstone

Basic Circuits are part of the electronics foundation used by Flux Foundry's automation technology. Pasted text

Use JEI when you need to check the exact crafting arrangement or another recipe in the pack.

---

Step 4 — Configure Your Machines

Flux Foundry machines support configurable faces.

Open the machine's Side Configuration interface and configure the appropriate sides for their intended jobs.

Depending on the machine, available roles can include things such as:

Item Input
Item Output
Fluid Input
Fluid Output
Energy Input
Disabled

This allows machines to fit the factory layout instead of forcing the factory layout to fit the machine.

---

Step 5 — Build Basic Item Logistics

An Item network generally consists of:

Inventory → Extractor → Item Pipe → Destination

Use channels and filters when you need more control.

For example:

White Channel → Furnace line

Blue Channel → Crusher line

Different channels prevent unwanted connections between otherwise nearby logistics networks.

---

Step 6 — Use Conduit Bundles

Large factories quickly become crowded.

Conduit Bundles allow multiple transport layers to occupy shared infrastructure while retaining their independent configuration.

Use Bundles when you need to move several resource types through the same factory area without filling every block with separate conduit runs.

---

Step 7 — Build Industrial Control

Once you are ready for Controller-managed logistics, build:

Controller

Data Lines

Item Nodes

Industrial Terminal

Early Data infrastructure is intentionally point-to-point.

Connect intelligent equipment to the Controller and commission your Nodes.

---

Commissioning Item Nodes

A Node needs to understand what its physical connections represent.

For example:

Right side / White channel → Furnace

Left side / Blue channel → route toward Storage

The Controller uses this information to understand how resources can actually move through your factory.

A Data connection alone is never an Item route.

---

Step 8 — Power Your Nodes

Item Nodes are active industrial devices.

They require FE to execute Controller commands.

The rule is:

CONTROL + POWER + PHYSICAL ROUTE = OPERATION

If a controlled Item isn't moving, check those three things first.

---

AUTocrafting Guide

Once your controlled factory works, you can start building Flux Foundry's autocrafting infrastructure.

You'll generally need:

Controller
Industrial Terminal
Basic Server Hub
Basic Recipe Drive
Crafter Core
Item Nodes
Item Pipes
Power

Processing recipes additionally require the appropriate commissioned machines.

---

Basic Recipe Drive

The Basic Recipe Drive stores recipe knowledge.

Each Basic Recipe Drive stores:

16 recipe definitions

Crafting and Processing definitions use the same capacity.

For example:

12 Crafting + 4 Processing = 16/16

Drives are rewritable.

Recipe data stays on the Drive when it is removed, so programmed Drives can be moved between compatible Server Hubs without losing their recipes.

---

Basic Server Hub

A Basic Server Hub has:

4 Recipe Drive bays

Four full Basic Recipe Drives provide:

64 recipe definitions

Need more than 64 recipes?

You can use additional Server Hubs. The Controller can use available recipe knowledge from multiple Hubs. Pasted text

The Server Hub requires:

FE + Data

It does not require an Item Pipe simply to provide recipe information.

---

Drive AUTO

When programming a recipe, select the Server Hub where you want it stored.

For normal use, leave the Drive selection on:

AUTO

Flux Foundry selects the first compatible Drive in that Hub with available capacity.

If the selected Hub is full, the recipe is not silently written to some other Hub.

---

Programming Crafting Recipes

Open the Industrial Terminal and select:

RECIPES → CRAFTING

Use the ghost 3×3 crafting grid to describe the recipe.

Ghost slots do not consume the actual Items.

Flux Foundry validates the definition against the real registered Minecraft recipe.

Then:

1. Select the Server Hub.
2. Leave the Drive on AUTO.
3. Save.

The recipe is now available to the Controller.

You cannot use this screen to invent arbitrary Crafting Table recipes.

---

Programming Processing Recipes

Select:

RECIPES → PROCESSING

Processing recipes describe work performed by real machines.

Define:

• input Items
• expected output Items
• Ordered or Unordered input behavior
• commissioned destination machine
• Server Hub

Then save the definition.

For example:

Sand → Crusher → Silica

The definition tells the Controller what it should expect.

It does not create the Silica.

The Crusher must actually produce the output.

This means programming something like:

Dirt → 64 Diamonds

doesn't magically produce Diamonds.

The Controller waits for the real machine output.

---

Ordered vs. Unordered Processing

Unordered

The machine needs all listed inputs, but their definition order does not carry positional meaning.

Ordered

The relationship between inputs matters and is preserved for compatible commissioned machines.

Use Ordered mode when different machine inputs have different purposes.

---

Building a Crafter

The Crafter Core performs ordinary registered crafting recipes automatically.

A Crafter Core provides:

1 crafting lane

Each Basic Crafting Module adds:

+1 concurrent lane

So:

Core = 1 lane

Core + 1 Module = 2 lanes

Core + 3 Modules = 4 lanes

The current Beta implementation supports up to 16 lanes.

Each baseline crafting operation takes:

20 active ticks

The Crafter requires FE and physical Item logistics.

---

Making Your First Autocrafting Request

Once the factory knows a recipe, request the Item through the Terminal.

Suppose you request:

16 Chests

and storage already contains:

5 Chests

Flux Foundry uses those five first.

The Controller only manufactures the missing:

11 Chests

It reserves the required real materials, sends them through the physical factory, operates the Crafter and delivers the final result to the Terminal.

---

Recursive Autocrafting

The Controller can follow recipes through multiple production levels.

For example:

Final Product

needs

Component

which needs

Basic Circuit

which needs

Silicon

which needs

Silica

which needs

Sand

The Controller works backward through the known recipes until it reaches physical materials your factory actually has.

Then it executes the required production steps in order.

---

Mixed Machine + Crafting Automation

Autocrafting is not limited to the Crafter.

A production chain can include real processing machines.

For example:

Sand

→ Crusher

→ Silica

→ Powered Furnace

→ Silicon

→ Crafter

→ Basic Circuit

The Controller coordinates the sequence while the actual machines and Crafter physically perform the work.

---

Jobs and Reservations

Autocrafting uses durable jobs.

When a job needs resources, the Controller can reserve physical materials for it.

Reserved does not mean the Item disappeared into the computer.

The Item still exists in an inventory.

It simply means that quantity has been promised to the job.

Once materials enter production, they can become allocated to that job so another request cannot use them simultaneously.

---

What Happens When Something Breaks?

Flux Foundry expects real factories to have problems.

A job may wait for:

Material
Power
Data
Route
Machine
Output
Delivery Space

Fix the underlying problem and the system can continue.

---

Cancelling Jobs

Jobs can be cancelled.

Unused reservations are released.

Physical materials are preserved wherever possible.

Already-completed transformations are not magically reversed.

If your machine has already turned one material into another, cancelling the job does not turn it back.

---

Steam Power Quick Guide

Flux Foundry also supports a physical Steam cycle.

The main equipment includes:

Water Pump
Boiler
Steam Turbine
Condenser

A canonical full cycle for 1,000 mB of circulated Water produces:

4,000 FE gross

The Pump consumes:

25 FE

giving:

3,975 FE net

before separately accounting for Boiler fuel.

The Condenser recovers 950 mB of the original 1,000 mB Water, leaving 50 mB of makeup Water required for another complete cycle.

---

Troubleshooting

My Item Node won't move anything

Check:

Power
Data
Physical Item route

All three are required.

---

My Server Hub isn't available

Check:

FE

and:

Data connection

---

My Recipe Drive is full

A Basic Drive holds 16 definitions.

Install another Drive or remove an unused recipe.

---

My Server Hub is full

A Basic Hub holds four Drives.

Use another Server Hub if you need additional recipe capacity.

---

The Controller says no recipe is known

Program the required Crafting or Processing definition through the Terminal.

Remember that intermediate ingredients may need their own recipes too.

---

Waiting for Material

The Controller cannot currently obtain enough physical resources to continue.

Check storage and upstream production.

---

Waiting for Power

One of the required active devices does not have sufficient FE.

---

Waiting for Route

The Controller understands where the Item needs to go but cannot currently find the commissioned physical Item path.

Check:

• Item Pipes
• channels
• Node mappings
• loaded factory sections

---

Waiting for Machine

The Processing recipe's commissioned machine is unavailable.

Check the machine and its commissioning.

---

Waiting for Output

The machine has not physically produced the expected output yet.

Check:

• machine recipe
• inputs
• FE
• output capacity
• Processing definition

---

Waiting for Delivery Space

The requested Item has been produced, but the Terminal cannot accept all of it.

Free some delivery space.

---

About the DevPack

Flux Foundry DevPack is intentionally a development/testing pack.

Its purpose is to make the latest Flux Foundry Beta available in a convenient environment with useful development/playtesting support such as JEI.

That means:

• systems may continue to evolve;
• balance may change;
• new industrial progression will be added;
• Beta worlds should be backed up before major updates.

The DevPack is also useful for players who simply want a convenient way to experience Flux Foundry without building their own mod list.

---

What's Coming Later?

Flux Foundry's current architecture leaves room for significantly larger factories.

Future development is expected to explore systems such as:

• faster Crafter operation
• expanded recipe-storage technology
• additional resource-domain industrial control
• scalable Controller hardware
• more uses for the industrial material set
• advanced factory communication
• higher-density infrastructure
• deeper storage technology

These are future directions and are not promises that those systems are already available in DevPack 0.4.0.

---

Current DevPack Version

Flux Foundry DevPack 0.4.0

Featuring:

Minecraft 26.3
NeoForge 26.3.0.48-beta
Flux Foundry 0.10.1-beta.1
JEI

Build a machine.

Connect the power.

Route the resources.

Teach the Controller what everything does.

Then ask the factory to build something for you.