Why Build This Potion Line?

A Vitality Potion blueprint matters because it is often the point where a simple potion setup becomes a real factory system. It combines farming, solid-material processing, liquid pipes, conveyors, and retail delivery in one compact production chain.

The practical goal is not merely crafting one potion. A good build keeps Redcurrants growing, turns them into Fruit Wine, produces Quicklime Powder steadily, and prevents the Blender from waiting on either ingredient. Once the output is stable, route the finished potions to a Potion Shelf or a storage buffer for later use.

Community layouts range from straightforward starter modules to dense, stackable one-tile machines. Start with a visible, easy-to-debug layout before copying or compressing it into a large alchemy factory vitality potion blueprint.

Production stageInputOutputMain logistics type
Crop productionRedcurrant SeedsRedcurrantsConveyor
Liquid extractionRedcurrantsFruit WinePipe output
Mineral processingLimestone or Stone chainQuicklime PowderConveyor
Potion craftingFruit Wine + Quicklime PowderVitality PotionPipe and conveyor
Sales deliveryVitality PotionsShelf stockConveyor or Catapult

Keep your first build near existing fertilizer, fuel, and coin routes if possible. This reduces the number of long belt runs and makes it easier to see where a shortage begins.

Recipe and Production Ratios

The Blender recipe uses 4 Quicklime Powder and 80 Fruit Wine to make 1 Vitality Potion in 8 seconds. That rate equals 7.5 potions per minute for one continuously supplied Blender.

Fruit Wine is the limiting ingredient in many early designs. An Extractor processes 1 Redcurrant into 10 Fruit Wine in 6 seconds, so a single Blender needs a reliable supply of Redcurrants and enough Extractors to keep its liquid pipe filled.

Blender targetPotions per minuteFruit Wine needed per minuteQuicklime Powder needed per minute
1 Blender7.560030
2 Blenders151,20060
4 Blenders302,400120

For a single Blender, 600 Fruit Wine per minute requires 60 Redcurrants per minute. Since one Extractor makes 10 Fruit Wine every 6 seconds, it produces 100 Fruit Wine per minute. In other words, six fully supplied Extractors match one Blender’s Fruit Wine demand.

Device or processWorking ratePlanning use
Blender1 potion per 8 secondsFinal crafting stage
Extractor10 Fruit Wine per 6 secondsSix support one Blender
Redcurrant planting recipe150 Redcurrants per seed in 720 secondsCrop planning baseline
Vitality Potion sale value330Useful for comparing sales routes

Treat these values as a planning reference, especially after version changes. Confirm live recipe settings, device rates, and unlock requirements in your current game interface before building a large permanent module.

Build the Blueprint in Layers

Build from the Blender outward. Place the Blender first, choose Vitality Potion as its recipe, then reserve one side for the liquid connection and another for solid-item belts. This avoids the common mistake of building a tidy-looking production block that cannot accept a pipe where it needs one.

A clean starter layout has three layers:

  • A crop and nursery area that produces Redcurrants.
  • An extraction row feeding Fruit Wine through pipes.
  • A mineral and Blender row that moves Quicklime Powder and potions by conveyor.

The Blender uses two distinct input systems. Fruit Wine is a liquid, so it must enter through the pipeline input. Quicklime Powder is a solid item, so it must enter through a conveyor input. The completed Vitality Potion also exits as a conveyor item.

ConnectionMaterialDirectionCommon mistake
PipeFruit WineInto BlenderTrying to deliver liquid on a belt
ConveyorQuicklime PowderInto BlenderSending powder to the pipe port
ConveyorVitality PotionOut of BlenderForgetting to leave output access
Conveyor or CatapultFinished potionToward Potion ShelfPlacing the shelf outside launcher range

Give each Blender a short output belt leading to a storage box, shelf line, or merged factory belt. A small buffer is useful while testing because it reveals whether the machine is producing consistently without forcing you to watch a shelf constantly.

For the Redcurrant side, keep nursery outputs organized before they reach Extractors. A shared belt can work for a small setup, but it becomes harder to diagnose once several nurseries compete for fertilizer and transport capacity. If crops arrive unevenly, place a buffer before the Extractors.

Quicklime Powder should also arrive on its own belt. Do not merge it with other solids until after it has passed the Blender inputs. Mixing unrelated materials into the same line is compact, but a misplaced splitter can starve every potion machine in the row.

Operate, Expand, and Deliver Potions

Run a simple startup check before treating the module as finished:

  1. Confirm every nursery has the intended crop and receives its required support materials.
  2. Watch Redcurrants enter Extractors and verify Fruit Wine moves through pipes toward the Blender.
  3. Check that Quicklime Powder reaches the Blender on a conveyor.
  4. Let the system run for several production cycles.
  5. Inspect the Blender output belt, then connect it to storage or a Potion Shelf.

If the Blender pauses, identify which input is empty rather than immediately adding more machines. An empty liquid input means the crop or extractor side is underbuilt. An empty powder input points to the limestone, stone, quicklime, or grinding chain. A blocked output means your potion belt, storage, shelf, or Catapult route needs more capacity.

For retail, place Vitality Potions onto a Potion Shelf. A Catapult can automate shelf stocking when positioned within reach of the shelf. This is useful when the factory line is elevated or when you want the shelf separate from the main conveyor path.

Expansion is a choice between local modules and centralized infrastructure. Local fertilizer or fuel production keeps each blueprint self-contained and easy to copy. Centralized lines can reduce duplication, but early shared networks may become bottlenecks before they save much space.

ApproachBest forAdvantageTradeoff
Local support modulesEarly or repeatable buildsEasy to copy and troubleshootRepeats infrastructure
Centralized fertilizer busMature factory floorsFewer separate production plantsCan run short at high demand
Stacked potion blueprintLimited floor areaSaves footprint and supports replicationHarder to inspect and modify
One-tile community layoutAdvanced compact buildsHigh density and clean external inputsRequires careful routing

A known community example targets 15 Vitality Potions per minute without upgrades. That corresponds to two constantly supplied Blenders. It demonstrates why scaling should begin with a clear production target: every increase in potion output multiplies crop, extraction, powder, fertilizer, fuel, coin, and transport demands.

When space becomes tight, build vertically only after the ground-level flow works. Raised shelves, stands, beams, elevators, and supported floors can make the layout compact, but they also hide jams. Leave access around pipes, belts, and machine ports so future upgrades do not require tearing down the whole line.

FAQ

What does an alchemy factory vitality potion blueprint need?

An alchemy factory vitality potion blueprint needs Redcurrant production, Extractors for Fruit Wine, a Quicklime Powder line, at least one Blender set to Vitality Potion, and a conveyor route for the finished potions.

How many Extractors supply one Blender?

One Blender needs 600 Fruit Wine per minute at the listed recipe rate. Since an Extractor produces 100 Fruit Wine per minute, six active Extractors supply one continuously running Blender.

Why will my Blender not accept Fruit Wine?

Fruit Wine is a liquid. Connect it to the Blender’s pipeline input, not its conveyor input. Quicklime Powder uses the conveyor input instead.

How should I sell the finished potions?

Send finished Vitality Potions by conveyor to a Potion Shelf. If the shelf is nearby but difficult to belt directly, use a Catapult positioned so it can reach the shelf.

Should I use a downloaded blueprint immediately?

Use community blueprints as layout references, but verify their footprint, required materials, unlocks, ratios, and logistics against your current version. A compact imported design may rely on assumptions that no longer match your game.