War Horn

What this item is trying to do

War Horn is a good case for reading patch history before ranking a relic. Its version note makes the pickup meaningful for an Embarkation route, but the value still depends on how much of the run remains after the trigger fires.

This page treats the effect and route connections as a decision aid, not as a promise of a fixed ranking. The current effect reads: “·Bullet Attack Cap +120% ·Embarkation: Bullet Attack permanently +12%.” 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 War Hornimproves the run you have, at the moment you can actually take it.

What the 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.

frequency entries matter when the route can repeat its trigger often enough to turn a small event into a steady engine physical entries are the baseline for routes that want direct weapon or skill output without splitting their investment embarkation entries pay at the start of a run or stage, so earlier access generally matters more than late access reliable entries have value because they work without a perfect sequence of offers, which makes them useful during a pivot

The route connections point to the trigger it is explicitly connected to. It is also connected to no named Hunter route uses this entry as a core choice yet. 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 War Horn only when you can say what it will do in the next few rooms. Take it when your current route already produces the frequency, physical, embarkation 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 War Horn 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, War Horn 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. War Horn has no explicit boss-or-crowd label here, so use the trigger and effect text to decide where it belongs.

If War Horn does not appear, use a replacement that preserves the same job rather than chasing the exact name. Related entries include Blood Moon Necklace, Book of Pilgrimage, Executioner's Axe, Fool's Boots. 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.

The trap is selecting it solely because the game text is official. The text proves what it does; it does not prove that the current run has room for its opportunity cost.

How to test this pick without inventing DPS

1. Write down the current Hunter, weapon, active tags, and the reason the run is considering War Horn. Do not change several slots at once; otherwise the result cannot tell you what helped.
2. Open the Planner with War Horn 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 previous one. If the tooltip changes, downgrade the advice until the interaction has been checked again.

Test War Horn by recording the starting stat, the first room after the trigger, and the later breakpoint where the extra value changes a kill or a reload. This keeps a patch-aware observation separate from a permanent tier claim.

Limitations and the next decision

The planner does not claim a measured DPS ranking for War Horn. 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.