Sandustry Flux Emanator Guide: Voidbloom to Fluxite

Understand the machine's job before placing it

The Flux Emanator is a special production building that creates Fluxite from Voidbloom contact. Unlike a simple box with an input slot and output slot, its geometry is exposed: the source touches the top and the product forms in space below. The room around the building is part of the recipe.

Fluxite growth is slow and circular according to the official page. Design collection around the expanding shape rather than a narrow point output. If the area below is blocked, growth can accumulate into a large blob that becomes both a throughput problem and a performance risk.

Follow the documented input and output rules

Voidbloom must touch the top of the Flux Emanator. Keep that contact stable and protect it from unrelated material. The building then spawns Fluxite below, where normal material movement and containment determine how the result leaves the production area.

The official tips specifically warn that blocked space and huge Fluxite blobs can hurt performance. Output removal is therefore part of operating the building, not optional cleanup. Measure the maximum blob size reached during a normal interval and keep the collector faster than continued growth.

Build a serviceable layout

Reserve an open chamber below the Emanator with sloped or conveyed collection at the perimeter. Keep the Voidbloom feed accessible from above and prevent output from reaching it. Add a visual marker for the safe maximum growth region so slow accumulation is noticed before it fills the chamber.

Place a shutoff at the Voidbloom contact or make the source removable without opening the output. Keep the chamber away from critical narrow corridors; a service visit should not require walking through the product. Test collection from several edges of the circular growth area.

Measure sustainable throughput

Treat Flux Emanator as one boundary in a longer chain. Start with empty or recorded buffers, count how much Voidbloom touching the top reaches the input during a fixed interval, and compare that with Fluxite growing below the building leaving the output. Record material still inside the chamber. A growing reserve before the machine identifies an intake or processing limit; a growing reserve after it identifies a collection or destination limit.

Do not infer an exact rate from a short animation. Let startup material clear, repeat the interval, and test again after saving and loading. If supply arrives in bursts, record both average flow and the largest burst. Add parallel capacity only after the same boundary limits two clean observations. Otherwise extra machines can hide a routing fault while consuming space, power, heat, cold, or scarce construction resources.

Diagnose the first failed boundary

If no Fluxite appears, confirm direct Voidbloom contact on the top face and clear the area below. If growth begins and then slows, inspect for an occupied output region before changing the source. A small remaining connection can keep producing into a blocked chamber.

If frame rate declines near the module, pause input and reduce the Fluxite blob in a recoverable copy. Observe performance after the chamber is cleared. If the problem persists, compare a clean v0.5.6 world and active mods before attributing every slowdown to the building.

Apply the v0.5.6 version notes

Update #3 changes an important downstream hazard: Lava now destroys Fluxite. Do not route a Flux Emanator output through or beside an uncontrolled Lava channel, and do not use stored Fluxite as a trusted Lava barrier in v0.5.6.

The patch also includes general performance and diagnostic work. The official Emanator warning about oversized blobs still supports proactive collection. Record product accumulation and frame behavior together when testing a larger module.

Validate the design in a small test cell

Build one isolated Flux Emanator with a limited input sample, visible output pocket, and a way to stop supply. Label the game version and active mods. Observe the expected transformation, any byproduct, where each pixel settles, and what happens when the destination fills. Then clear the cell and reverse the loading order if two materials share space. A repeatable small test gives a stronger design basis than a screenshot of a large factory.

After the test passes, copy the geometry into production while keeping access to the input, output, and removal controls. Leave enough room to inspect or drain the machine without opening a neighboring line. Recheck the route after patches that mention the machine, its materials, density, heat, fluids, energy, or building events. Keep the prior measurement with its version so a future change is visible instead of becoming an unexplained slowdown.

Use the pre-launch checklist

Before opening full supply, confirm that the input really is Voidbloom touching the top, the planned result is Fluxite growing below the building, every required power or temperature connection is active, and no incompatible material can enter. Verify output clearance, overflow capacity, a shutoff point, and a safe path for the player. Take one recovery save before connecting a rare or destructive input.

During the first long run, compare starting and ending inventory at every boundary. Watch for material trapped inside building cells, a mixed network, a full destination, and a reserve that only delays failure. If the line remains balanced through its normal burst and restart conditions, record the observed rate and promote the module as the factory's current versioned standard.

Field facts

Troubleshooting

• No Fluxite forms.

  Restore direct Voidbloom contact on top and clear open cells below the Emanator.

• Growth fills the chamber.

  Stop the Voidbloom contact, remove the blob, and increase collection clearance before restarting.

• The module causes poor performance.

  Reduce blocked Fluxite accumulation and compare the cleared module in a current vanilla test world.