SHORT ANSWER
Start with the weapon that feeds the route
Drop qualityCommon / Rare / Epic / Legendary / Mythic
A physical fallback when the Musket does not appear and Hemorrhage still fits the route.
The starter weapon is shown separately when it is part of the route, but it is not counted as a community power recommendation.
Load Marcus's route in PlannerREAL-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 ↗Official X: weapon handbook is onboarding material, not a tier list
The official X feed points players to a Demon Hunter Handbook about elements, weapon parts, Smite, Final Shot, and weapon combos. It is useful for explaining the system, but it does not provide a public hunter-by-hunter win-rate sample, so the site does not turn it into a ranking.
Open the official X feed ↗Third-party tier list: useful lead, conflicting catalog
A community-wiki tier page uses chassis names such as Skorpian and Leaf Cutter and describes a five-chassis model. The current official Steam catalog used by this site contains 45 weapon families with different names. Until the two datasets are reconciled in the Training Room, this source is kept as a lead and not converted into a recommendation.
Compare the third-party tier list ↗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.
Steam review: players cannot see enough to compare a drop
One high-rated review calls out missing comparison information such as current health, unique stats, proc chances, and how elemental damage changes a weapon. That is one player's report, but it matches the site's need for explicit quality, role, and trigger explanations.
How the site uses it: Show the decision reason and the known quality range. Do not invent a DPS number when the game UI and public reports do not provide a reproducible measurement.
Current Steam topics: comparison, stutter, balance, and bugs
The current General Discussions page contains recent topics about weapon/stat comparison, explosion-effect stutter, difficulty balance, unlocks, achievements, and freezes. Topic titles show where players are getting stuck; they are not enough to rank a build.
How the site uses it: Keep patch-sensitive warnings and a clear fallback on route pages. Treat a discussion title as a problem lead until the full thread supplies a reproducible case.
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.
TapTap reviews: branches, stats, and high-quality drops are hard to read
Several early reviews discuss weak branch differentiation, stats that are hard to feel or compare, and difficulty finding high-quality weapons. These reviews are historical and mixed with demo feedback, so they are UX signals rather than current balance evidence.
How the site uses it: Explain what a route is trying to trigger, what a rarity label does not tell you, and when to keep the current weapon. Leave old review evidence dated instead of silently rewriting it as current fact.
Official verification path: Training Room and Item Encyclopedia
The current official update adds a Training Room for freely testing a build and an Item Encyclopedia. This gives the site a safe place to send players when a community route names an item or interaction that is not yet mapped with confidence.
How the site uses it: Verify the weapon family, quality, trigger frequency, room coverage, and boss phase before upgrading a player report into a route recommendation.
Official guardrail: infinite trigger loops caused instability
In a developer letter, the team said extreme infinite-stacking and Ultimate-trigger combinations had caused stutter, freezes, crashes, and lost saves, then introduced caps and cooldowns. A high-ceiling interaction therefore needs a stability check as well as a damage check.
How the site uses it: Do not promote a route solely because it can multiply triggers. Keep the current room playable, and mark old infinite-loop claims as patch-sensitive.
This layer only uses publicly viewable pages. In this pass, the game-specific material we could recheck came mainly from Steam, TapTap, and one Chinese guide. No Xiaoheihe or Discord thread with a stable, publicly reviewable message URL was found, so neither channel is used to fill a ranking. Research date: 2026-08-06; current site baseline: 1.0.503.
Weapon choices that match the run you have
A physical fallback when the Musket does not appear and Hemorrhage still fits the route.
Tradeoff: Do not swap just for rarity if the current gun is firing more reliably.
A crowd-control pivot when the run has already lost its Physical support.
Tradeoff: Changing element abandons Hemorrhage progress; treat it as a real pivot.
Best starting anchor for the extra-shot and first-shot rhythm.
Tradeoff: Five rounds means reload downtime is the first problem to solve.
How to choose the weapon during a run
- Keep the active element. Switching away from the element your relics and Tarot reference costs more than a higher rarity label usually gives back.
- Check the event rhythm. Reload, first shot, final shot, skill use, and companion triggers only matter when the weapon produces them often enough.
- Match the room. Use the crowd guidance for packs and the boss guidance for a long single-target phase; one weapon does not have to win both jobs equally.
- Switch for a reason. Move when the new weapon fixes a real failure, such as reload downtime, missing room coverage, or an element the rest of the build has already abandoned.
Use reload support and crit payoff once the target stays alive long enough for repeated first-shot windows. Keep firing discipline; a burst that spends half the fight reloading is not a boss plan.
Extra shots, fire rate, and a weapon that spreads pressure are the priority. If packs are the failure point, Bullet Attack and volley effects beat a greedy single-target card.
If the recommended weapon never appears
Geminate Shot+ or the Musket never appears by the middle of the run.
Keep the physical element, choose Fire Rate and Reload Speed, and use Demonhunter Crossbow or any reliable physical family.
Do not: Do not hold empty slots for one exact skill while the current weapon has no uptime support.
How to read this list
A Common starter can be the right first-room choice because it is guaranteed and familiar. After the run reveals its element and trigger direction, compare later drops by quality range, firing rhythm, and build evidence—not by putting the starter at the top of every list.