Minecraft Potion Brewing Time Calculator: Optimizing Array Speed and Throughput

Brewing potions is a strict, mathematical process in Minecraft. The game engine locks potion brewing to a merciless 400-tick cycle (20 seconds) per ingredient. You cannot speed this up with enchantments, better fuel, or beacons. The only way to increase your production speed is through clever redstone engineering. The Minecraft Potion Brewing Time Calculator is designed to help you architect the perfect laboratory, comparing the time-savings of Parallel Arrays versus Sequential Pipelines.

The Hardcoded Variables of Brewing

Before designing an auto-brewer, you must respect the immutable rules of the Minecraft engine:

• Brew Time: 1 step (1 ingredient) = 400 Redstone Ticks = 20 seconds at a perfect 20 TPS (Ticks Per Second).
• Batch Limits: 1 stand processes 3 bottles simultaneously. Doing fewer than 3 takes the exact same amount of time.
• Hopper Speed: A standard hopper moves 1 item every 8 ticks (0.4 seconds). Moving 3 completed bottles to a chest takes 1.2 seconds.

Architecture 1: The Parallel Array

A Parallel Array is heavily favored by PvP factions and technical servers that demand massive amounts of potions immediately. In this setup, you place multiple identical brewing stands (e.g., 20 stands) in a row. Each stand performs every step of the potion from start to finish.

The Pros of Parallel

The math heavily favors Parallel setups for bulk speed. If you need 300 potions (100 batches), and you have 20 stands, each stand only has to process 5 batches. If it's a 4-step potion (80 seconds per batch), your total real-world time is only 5 × 80 = 400 seconds (6 minutes 40 seconds).

The Cons of Parallel

Parallel arrays are an absolute nightmare to stock. To brew those 300 potions, you must evenly distribute Nether Wart, Glistering Melons, Glowstone, and Gunpowder across 20 different hoppers perfectly. If one stand gets an uneven amount, it breaks the redstone clock sync. This requires complex water streams, ice paths, and hopper minecart distributors.

Architecture 2: The Sequential Pipeline (Assembly Line)

A Sequential Pipeline operates like a real-world factory. If you are making a 4-step potion, you use exactly 4 brewing stands stacked vertically or diagonally.

• Stand 1: Only has Nether Wart. Adds it, takes 20 seconds, then dumps the Awkward Potions into Stand 2.
• Stand 2: Only has Glistering Melons. Adds it, takes 20 seconds, dumps into Stand 3.
• Stand 3: Only has Glowstone. Adds it, takes 20 seconds, dumps into Stand 4.
• Stand 4: Only has Gunpowder. Adds it, takes 20 seconds, dumps into the final output chest.

The Pros of Sequential

This is incredibly easy to stock. You only need one chest for Nether Wart, one for Melons, etc. You just dump your ingredients in and walk away.

The Cons of Sequential

It is significantly slower for large batches because it has a singular bottleneck: the final stand. It takes 80 seconds of "Prime Time" just for the first batch to reach the end. After that, it outputs 3 potions every 20 seconds. Brewing 300 potions in this setup takes 80 seconds + (99 remaining batches × 20 seconds) = 2060 seconds (34 minutes). That is over 5 times slower than the 20-stand Parallel setup.

Redstone Hopper Clocks and Delays

If you are building a fully automatic brewer, you cannot rely on the brewing stand to empty itself. A brewing stand will happily sit there with finished potions forever. You must use a redstone timer to unlock the hopper underneath the stand exactly when the potion is finished.

The most common timer is an Etho Hopper Clock. Because a brew cycle is 20 seconds, and a hopper moves 2.5 items per second, you need exactly 50 items in your Etho clock to create a 20-second delay. However, you must account for extraction time! It takes 1.2 seconds to pull the 3 bottles out. If your clock cycles exactly at 20.0 seconds, it will cut off the extraction, leaving bottles behind and breaking the system. A smart engineer uses 53 items in their clock to create a ~21-second cycle, ensuring perfect, safe extraction.

The Impact of TPS (Ticks Per Second)

Your real-world timing calculations are entirely at the mercy of the server's CPU. Minecraft is designed to run at 20 ticks per second. If there are massive mob farms running or millions of items on the ground, the TPS might drop to 10.

At 10 TPS, the server is running at half speed. A 400-tick brewing cycle (which should take 20 seconds) will now take 40 seconds. Fortunately, because redstone clocks are also tied to ticks, your automated hopper locks will scale perfectly with the lag. The system won't break; it will just take much longer in real-world time. This calculator assumes an optimal 20 TPS output.

Conclusion: Design to Your Needs

If you are playing casual survival and just need a restock box of Fire Resistance, a simple Sequential Pipeline is the most painless to build and maintain. But if you are arming an entire server for war, mastering the item distribution required for a massive Parallel Array is the only mathematical way to beat the hardcoded 20-second game limitation. Use the Minecraft Potion Brewing Time Calculator to benchmark your designs before you place a single piece of redstone.