Direct answer
Flux Emanator is a current Special building, but the checked official material does not yet establish a complete input, output, feed, or clearance specification. Treat any setup as a versioned test: isolate one input, leave visible space around the building, and record what the current UI and output actually confirm.
Field note
Start from the confirmed entity
Use the current Flux Emanator name and verify the building in the present build. Do not import detailed preview layouts simply because the entity name matches.
Create a small test area away from a valuable production chain so an incorrect input or overflow does not contaminate other systems.
Field note
Test one condition at a time
Begin with one candidate input and an empty output area. Observe whether the building accepts material, changes state, emits an output, or reports a requirement in the UI.
Then test clearance, filters, and overflow separately. Record the game version and visible result for each change rather than combining several assumptions into one layout.
Field note
Diagnose transport and Drone interactions
If material never reaches the building, inspect routing and filters before changing the machine. If output appears but does not leave, inspect destination capacity and Drone assignment as separate layers.
This page should be upgraded only when an official detail page or reproducible current-build capture supplies the missing mechanism.
Limits and update triggers
What this page does not claim
- Current official evidence confirms the entity but not a complete input, output, or clearance specification.
- Competitor layout details may describe a preview build and are not published as facts.
Source ledger
Sources checked for this guide
- Sandustry official wiki indexofficial fact
- Steam Sandustry store pageofficial fact
- Community Flux Emanator coveragethird party guidance
Research checked 2026-08-16. Time-sensitive claims require another check before public release.