Flower of Life

Editorial read: what this entry is trying to do

Flower of Life is not a universal upgrade. Its recorded identity is growth, acid, ultimate, companion, and that combination tells you what kind of problem the entry is meant to solve. Start with the current effect, then check whether your run is already producing the event that gives the entry value.

This page treats the current planner record as a decision aid, not as a promise of a fixed ranking. The entry is listed as cross-checked; the effect record currently reads: “• All your [Growth] becomes [Bloom]. Each stack increases Bullet Attack by 2%. Effects from Relics with the same name cannot stack. (Unique Passive; Bloom is still considered Growth.) • On Ultimate: Summons a Flower of Life for 10 seconds to fight alongside you. Each second, Flower of Life fires 1 piercing thorn, dealing [Bloom] stacks * 2.5% Acid Damage to enemies. Damage dealt by Flower of Life is also considered Bullet Damage.” That wording matters because a rarity label can stay the same while the route around it changes after a patch. The practical question is whether Flower of Lifeimproves the run you have, at the moment you can actually take it.

What the recorded effect means in a run

A relic is a slot decision. It can be powerful and still be wrong when its trigger is not part of the current route or when another slot fixes a more immediate failure.

growth entries reward a route that reaches its checkpoints and keeps the stored resource alive long enough to compound acid entries want repeated application and enough room for their effect to accumulate before the target disappears ultimate entries should be judged by charge frequency and the quality of the moment when the ultimate lands companion entries add another damage or trigger source, so the key question is whether the rest of the route feeds that source

The current connections point to the trigger it is explicitly connected to. It is also connected to the current Hunter routes do not assign this entry to one named Hunter. Those connections are clues, not automatic instructions: a skill can be listed for a Hunter and still be the wrong answer when that run has a different immediate bottleneck. Compare the entry with the other offers on screen before spending the slot.

Early, middle, and late run decisions

Early run: prove the trigger

Early in a run, take Flower of Life only when you can say what it will do in the next few rooms. Take it when your current route already produces the growth, acid, ultimate signals. The value comes from repeating that event, not from the item name or rarity alone. If the entry needs a second item, a particular element, or a later checkpoint, mark that dependency and keep a simple fallback in mind. An early pick is valuable when it starts a route or removes a failure that is already happening; it is fragile when it asks the run to become something entirely different.

Middle run: check whether the route paid back

In the middle of the run, stop judging Flower of Life by the promise of its text. Look for the event it was supposed to improve: more useful shots, more controlled rooms, a cleaner boss window, or a safer route through the next checkpoint. If that event is not showing up, the correct move can be to keep the item as a placeholder while changing a support slot, or to pivot before the run spends another choice on the same idea.

Late run: protect the win condition

Late in the run, Flower of Life should have a job that can be named in one sentence. Keep it if it contributes to the trigger it is explicitly connected to and the effect is still active in the actual loadout. Replace or ignore it when the route has already solved that problem and a missing survival, reload, or target-coverage answer is now more likely to end the run.

Boss, crowd, and fallback use

For bosses, ask whether the entry improves sustained access to the target or only creates a brief high roll. For crowds, ask whether it reduces the number of dangerous enemies that remain after one action. Flower of Life has no explicit boss-or-crowd label in the current record, so use the trigger and effect text to decide where it belongs.

If Flower of Life does not appear, use a replacement that preserves the same job rather than chasing the exact name. Related entries include Lich's Tear, Entangling Vines, Flower of Peril, Acidolysis Round. A lower-ceiling option that keeps the element, trigger, or survival plan intact is usually a better fallback than an unrelated rare drop. If none of its triggers are happening yet, keep the slot open for a pick that strengthens the engine already on screen.

How to test this pick without inventing DPS

1. Write down the current Hunter, weapon, active tags, and the reason the run is considering Flower of Life. Do not change several slots at once; otherwise the result cannot tell you what helped.
2. Open the Planner with Flower of Life selected and read the synergy explanation. Confirm that the entry is connected to a real trigger, not only to a shared word in the tag list.
3. Test one crowded room and one durable target when the route reaches them. Record uptime, missed triggers, reload gaps, and the moment the run becomes safer or more fragile. A single run is an observation, not a universal damage measurement.
4. Reopen this page after the next patch and compare the current effect with the recorded one. If the tooltip changes, downgrade the advice until the interaction has been checked again.

Limitations and the next decision

The planner does not claim a measured DPS ranking for Flower of Life. It explains route fit from the current effect, tags, element, Hunter links, and evidence label. That is deliberately narrower than saying the item is always best. The useful output is a reasoned next choice that you can verify in the run.

If this entry fits, load it into the Planner and compare the next skill, relic, and Tarot choice. If it does not fit, return to the item library, filter by the missing trigger, and choose a replacement that fixes the failure you can actually see. That loop is more reliable than copying a static tier list without checking the run state.