ROUTE NOTES
Make one weapon better before adding a second.
Stella works when Starlight, the main weapon, and the chosen cards point at the same shots. A Tarot card without a current trigger is only a promise.
ROUTE NOTES
WHEN THIS ROUTE IS WORTH IT
Pick Stella when one main weapon is already working and Tarot offers can improve the same shots. It is a poor opening when every card asks for a different setup.
Take Triple Fate and make Starlight appear regularly with the main weapon. Add Starlit Haste next; take The Lovers only when the Sub Weapon has a job.
When coins are tight, give up the second weapon and decorative Tarot chase first. Keep the main gun, Starlight frequency, and room safety.
Stop forcing the route when Starlight rarely triggers or when the Tarot choices keep pulling you into unrelated elements.
A REAL RUN
What this decision looks like in play
The Lovers appears, but your Sub Weapon does not share a useful effect and the main weapon is still weak.
Skip the cross-weapon setup, take main-weapon or reload support, and revisit The Lovers only if the missing job appears.
Stella gains from a card changing a real event; a card without a trigger only occupies a future slot.
Do not add a second weapon solely to justify a Tarot card you already chose.
CLEAR ALTERNATIVE
If this is not your run
Marcus — Marcus's straightforward gunfire route
Switch when Use it when you want a working main weapon now and the Tarot offers are not lining up.
WEAPON CHOICES
Start here, then change only for a reason
The starter is shown as a transition. The first non-starter pick is the route candidate; the others are for the run you actually rolled.
Why it fits. A deliberate burst weapon for cards that reward timing and room control.
Tradeoff. Its pause rhythm can reduce Starlight consistency if the route is not practiced.
Why it fits. A crowd-control fallback when Freeze already has support in the run.
Tradeoff. Do not add Frost just because a Tarot card looks rare.
Why it fits. A stable main weapon that makes Starlight uptime easy to read.
Tradeoff. The five-round cycle makes reload support important.
REAL-DATA LAYER
Separate the starter, the quality range, and the community signal
Player reports and official facts are labelled separately. Where a Hunter-level sample is missing, this page does not invent a single certain answer.
Steam player report: projectile count is the real ceiling signal
A launch review describes successful runs around extra projectiles, Fire Rate, and Reload Speed, including an Acid setup reported at 6–8 projectiles and 0% condensed spread. The review uses the names “Skorpian” and “Leaf Cutter”; those names are not present in the current official catalog, so the site keeps the mechanic signal and does not hard-map them to a current weapon ID.
Read the Steam player review ↗Steam demo feedback: keep a working gun, dismantle misses
A player report says dismantling guns and parts returns upgrade tokens, and that they usually keep a gun that already works instead of switching just because a new drop is rarer. That is a useful rule for the in-run decision layer, not proof that the starter weapon is the best weapon.
Read the Steam discussion ↗Official 1.0.487: Training Room and Item Encyclopedia
The 1.0.487 Steam update added a Training Room for freely testing builds and an Item Encyclopedia. The site points players to the exact in-game verification step instead of presenting an untested weapon family as a measured tier-list winner.
Read the official Steam update ↗Current conclusion: the public data supports a projectile / fire-rate / reload direction, but not a reliable seven-Hunter weapon ranking yet. A family name also does not mean the drop is Legendary or Mythic; check the quality range and the current affixes on the item page.
COMMUNITY FIELD SIGNALS
Use player discussion as route evidence, not a fake tier list
Routes, decisions, and pain points stay separate. Each card shows its source, version status, and how the site uses it. A single player's result does not directly change Planner rankings.
Steam report: projectile count, Fire Rate, and Reload Speed
A high-rated Steam review describes a successful Acid run around extra projectiles, Fire Rate, and Reload Speed, reporting 6–8 projectiles and 0% condensed spread. The weapon names in that review do not map cleanly to this site's current 45-family catalog, so we retain the event pattern, not the item ranking.
How the site uses it: Use this as a projectile/reload hypothesis. Check the current family, quality, and room coverage in the Training Room before calling any weapon a best pick.
Steam decision signal: keep the gun that already works
A demo discussion describes dismantling guns and parts for upgrade resources, while advising players to keep a working gun instead of switching only because a new drop is rarer. It is a useful decision heuristic, not proof that the starter copy is the best weapon.
How the site uses it: Treat rarity as a tie-breaker. Switch when the new drop fixes reload downtime, room coverage, or a broken element—not when its color is simply brighter.
Official Update 8.20: current pet, co-op, and Lightning interaction fixes
This is the current bug-fix layer. It does not replace the V1.0.499 Frost balance baseline from the previous day.
How the site uses it: Use the current item data, then retest only the three fixed interactions when they appear in co-op, inventory, or Lightning routes.
Official Update 8.19: Pet system and Frost Relic rework
Old Frost descriptions and any recommendation built around the former Ice Pillar, Heart of the Storm, or Flash-Freeze Round behavior are obsolete.
How the site uses it: Prepare Armor before combat, use the refreshed official item text, and keep route ranking claims behind repeatable run tests.
Official Update 8.7: Arrow Rain, resolution, and Steam Deck fixes
The official 1.0.491 announcement is a bug-fix hotfix. It supports carrying forward current Build routes while keeping the three fixes visible on the patch page.
How the site uses it: Keep the current Build recommendations and Planner logic unchanged, then retest Arrow Rain, affected resolutions, and Steam Deck presentation after the update.
Official Update 8.6: three bugs fixed, no Build rebalance listed
The official Steam Update 8.6 announcement lists fixes for Auto Dismantle, controller Item Encyclopedia navigation, and an occasional backwards weapon on the results screen. It does not list Build balance changes.
How the site uses it: Keep the 1.0.487 Build recommendations and Planner logic unchanged. Use the 1.0.488 patch page for the three system, quality-of-life, and presentation fixes.
TapTap player route: Physical / Bleed one-shot claims
A TapTap post presents a Physical/Bleed route as a fast-kill direction and claims that, after an update, most bosses can be one-shot in a lucky or completed run. It is an anecdotal outcome, not a measured sample or a promise for every Hunter.
How the site uses it: Keep the route as a community experiment: build Physical/Bleed when the early triggers arrive, but retain a room-clear fallback and downgrade the claim after a patch changes Bleed or Final Shot.
Chinese guide candidate: Lightning / Disruption package
A Chinese guide ranks Thunder Bow and Railgun as Lightning anchors, then names Battery and several Lightning weapon parts as the package to try. It frames frequent hits and Disruption as the beginner-readable loop, but the tier labels are the author's judgment and the article does not establish a current public test sample.
How the site uses it: Use the named package as a candidate route in the Planner, then verify element coherence, Disruption uptime, and boss damage in the current Training Room. Do not import its tier labels into the site ranking.
RUN PLAN
What to fix first, and what can wait
Early picks make the weapon usable. Later picks raise the ceiling only after the room is safe.
Make Starlight happen often enough to matter.
Look for: Triple Fate, a consistent main weapon, and reload or Battle Skill support.
Checkpoint: If enhanced shots are rare, another rule-changing Tarot is not the fix.
Connect the card to a real trigger.
Look for: Starlit Haste, Endless Star, and The Lovers only when the Sub Weapon contributes.
Checkpoint: Every selected card should explain which event it changes.
Convert the connected system into burst.
Look for: The Emperor after crit sources, current-element support, and safe uptime.
Checkpoint: A full Tarot bar is not a win condition if the main weapon cannot trigger it.
FIVE-LEVEL TALENT PATH
The first five upgrades to look for
One choice is available at each level. The route picks below keep the main job visible; use the fallback when the offer solves a real weakness sooner.
MATCHUP TEST
The next fight may ask for a different answer
Bosses reward a repeatable Starlight window and a card that improves the main weapon rather than a decorative second system. Keep the Sub Weapon for a real effect or coverage gap.
Use Tarot and weapon choices that widen the number of useful events per room. Freeze or volley support can be better than pure boss crit when packs are the wall.
BAD OFFER RECOVERY
If the core item never shows up
The Lovers or a useful Sub Weapon effect never appears.
Drop the cross-weapon plan. Build Starlight uptime around the main weapon, Battle Skill consistency, and the current element.
Do not keep a dead Sub Weapon slot just because the Tarot was the original plan.
NEXT PICK
Use this on the offer in front of you
Check the item you actually see, compare what it triggers, then load the route into Planner if it still fits. A working next pick matters more than a perfect shopping list.
This route is a decision blueprint built from current mechanics and trigger conditions, not a measured DPS ranking. The game currently ships no public damage-testing dummy, so retest it by checking whether the events repeat, rooms clear, and the boss window stays reliable.