Self-Sustaining Panacea Factory Guide

Evidence status: Verified from supplied long-form player footage. Checked 2026-09-11. Exact numeric recipes may change with patches.

Design a stable Panacea loop and decide when to keep support production local.

Quick answer

Build the smallest working version first, confirm that inputs stay supplied and outputs keep moving, then scale. Alchemy Factory rewards visible, modular logistics more than clever but fragile spaghetti routing.

Design the loop first

Panacea can act as both fuel and fertilizer in observed player builds, making it a useful shared support resource.

Protect self-consumption

Priority routing can keep the Panacea-producing chain supplied before sending extra potion to other floors.

Local vs central

One large-factory walkthrough often keeps Panacea local to the floor it supports, sharing only when spare capacity has been measured.

Scale conservatively

Two Panacea machines were observed supporting a specific late-game set of consumers with measured surplus; do not copy that ratio blindly across patches or upgrades.

Troubleshooting checklist

1. Confirm the current patch and unlock state.
2. Inspect the upstream input before rebuilding the output side.
3. Check for full storage, blocked belts, or an empty support resource.
4. Test one module in isolation.
5. Scale only after the isolated module stays stable.

Source used

• We Built a Self-Sustaining Panacea Factory! | Alchemy Factory — supplied transcript with timestamps.