PoE 2 Blood Mage Sanguine Tides Flask Build

The Blood Mage build PoE 2 has survived every nerf GGG threw at it. Patch 0.5 nerfed life leech. Nobody cared. One ascendancy passive: Sanguine Tides: turns your life flask into a perpetual motion machine. You press the flask button 30 times per second via script, your HP never drops below survivable, and your damage never stops. That's the whole thing.

140 million damage in 3 seconds to the Uber Arbiter. Solo. By clicking a potion. Let that disgrace wash over you.

Going above 30 flask presses per second triggers an automatic kick. The game politely informs you that you are performing too many actions. It is not wrong.

The Loop Explained

The Sanguine Tides ascendancy node does one thing that breaks the game: it grants 1 life flask charge for every 4% of your maximum life you spend casting spells. You are a Blood Mage. You spend life constantly. Therefore, you generate flask charges constantly.

Flask charges restore life. Restored life gets spent again on casts. Charges regenerate. Life restores. The cycle does not end unless you stop pressing the button: or disconnect from the server.

Sanguine Tides node stats:
• Gain 1 Life Flask Charge per 4% Life Spent
• 50% less Life Recovery from Flasks
• On Flask full charges: consume 40%, gain 1% damage as Physical per charge consumed (3s)

The 50% recovery penalty is irrelevant. You are pressing the flask 30 times per second. Half of a firehose is still a firehose.

Why 30 presses per second specifically

The game has an action spam detection threshold. Exceed it and you get kicked with a "too many actions" message. 30 is empirically the safe ceiling. This is not a limitation: 10,000–15,000 HP regenerated per second makes you effectively unkillable in all currently available content.

Ascendancy Nodes

The dominant version is Cast on Critical Comet. Spark or Arc generates critical hits at high frequency. Each crit procs Comet. Comet hits hard. Blood Magic means every spell costs life, which feeds Sanguine Tides, which refills the flask. The loop is self-sustaining at mapping pace without any script: the script just makes boss killing obscene.

Passive Tree Direction

In 0.4, the build relied on two spell leech nodes to sustain life. In 0.5 those nodes were replaced by two life flask passive nodes. No additional flask passives are required. Two nodes is enough. The change took approximately 30 seconds to implement and completely circumvented the nerf.

Budget note: the build functions at every investment level. Temporalis and other premium pieces accelerate it, but the core loop works on early-league gear. This is not a comforting fact.

Mapping vs Bossing

In maps, you do not need the flask script at all. Life on kill from passive nodes and Life Remnants dropped by Sanguimancy cover all damage taken. Your raw life pool absorbs pack hits without drama. You are, by all practical measures, immortal in white and yellow maps.

For bosses: particularly Uber-tier content like the Uber Arbiter of Ash: you activate the flask script. Charges refill faster than they deplete. You receive 10,000–15,000 HP restoration per second passively. The boss has the same chance of killing you as a garden snail has of stopping a train.

• Maps: No script needed. Auto-pilot. Life on Kill + Remnants cover everything.
• Pinnacle bosses: Activate script. Press flask at 30/sec. Watch numbers.
• Uber content: Same as above. The gap in difficulty is irrelevant to this build.

One player on the Chinese platform Bilibili demonstrated the Uber Arbiter kill solo. Another did it in a 6-player party and dealt 140 million damage in 3 seconds. These are not theoretical numbers. These happened in patch 0.5, after the nerf.

Historical Precedent

If this feels familiar, it should. The Ward Loop exploit in Path of Exile 1 worked on the same principle: trigger a cycle once, ensure no component of the cycle can fail, become unkillable. Ward Loop ran automatically. This loop requires you to press a button. That is the one concession to balance.

The comparison is flattering for Ward Loop. At least that required understanding multiple interacting systems. This requires understanding one node and purchasing a flask.

Will GGG Fix This

The Blood Mage nerf 0.5 targeted life leech. It successfully removed one sustain vector and created a better one. Grinding Gear Games is aware the node exists. Whether Sanguine Tides itself gets reworked or the flask-charge generation rate is capped is unknown as of this writing.

The realistic outcomes:

1. Sanguine Tides gets a cooldown on charge generation: loop breaks.
2. A cap is added on charges-per-second from life spent: loop throttles.
3. Nothing happens for two more patches: Chinese players continue to own the economy.

If you are on the Chinese client (separate server): this may not affect Western economy at all. If you are on global servers: enjoy it or despise it. Both are valid responses.

The ascendancy passive tree changes required to execute this swap are trivial: two node reallocations. Any existing CoC Comet Blood Mage can adopt this in under a minute. There is no barrier to entry. That is the problem.