The Duskbloods Early Build Ideas

The Closed Network Test will be the first time many players touch The Duskbloods. This page offers early build ideas—playstyle frameworks you can map onto Bloodsworn, blood history, and fate once the hub opens—without inventing DPS tables, TTK values, or tier labels the preview build has not validated. The full game targets 2026 on Nintendo Switch 2; treat every idea here as a hypothesis to confirm or retire after your sessions.

Principles before picking a framework

1. Official systems beat fan math. Build around Victory Points, First Blood, events, and roles we know exist.
2. PvPvE means add control. If you cannot handle environment pressure, duels do not matter.
3. Hub iteration is cheap. Rewards return win or lose—use losses to refine fate in Hub customisation.
4. Two-character CNT plan. Limited test hours favour one ranged and one melee/summon Bloodsworn from the roster.
5. Document, do not dogma. Share notes in Guides; defer Tier List ranks until metrics repeat across players.

Framework A: VP duelist

Goal: Win fights that feed Victory Points and survive last-player-standing phases.

Hub choices: Fate paths that emphasise weapon mastery and duel sustain—exact nodes TBD in CNT. Avoid over-investing in companion tags unless you intend to pivot.

Match habits: Take fair fights when VP per minute beats running to events. Save entity summons for execute ranges or 1vX panic buttons. Learn Controls cancel options early so you are not menu-reading under fire.

Weaknesses: Event steals and third parties punish tunnel vision. Rotate when map telegraphs hint at dynamic events unless your VP lead is insurmountable—something you cannot know without data.

Maps: Open train-yard sightlines favour firearms; gothic alleys may force shotgun or melee variants. Check Maps hub for layout notes as they arrive.

Framework B: Event rotator

Goal: Maximize VP and rewards tied to mid-match environmental swings—stone face sequences and future events alike.

Hub choices: Prioritise mobility characteristics and fate branches that help you reach event channels quickly. Pair with Bloodsworn whose summons clear PvE adds spawned during events.

Match habits: Fight on the edge of events, not in the dead center, until you understand damage zones. Arrive early for channel starts, leave late for cleanup kills on fleeing players.

Weaknesses: Specialist duelists may challenge you in open fields between events. Destined Rival players may spawn hunt you if you become predictable.

Network Test homework: Timestamp event starts per map and publish a table—no fabricated percentages.

Framework C: Role specialist

Goal: Complete Destined Rival hunts or Destined Companion rendezvous for side rewards while staying VP-positive.

Hub choices: Commit in Blood history and fate to role-forward fate. Pick Bloodsworn with tracking tools (duelist) or peel/sustain (companion)—based on trailer kit themes, not stats.

Match habits: Rivals: identify your target early, avoid pointless frags that delay the hunt. Companions: use emotes or proximity to de-escalate until your ally arrives, then cooperate through one event before negotiating the betrayal phase.

Weaknesses: Free agents and boss-focused lobbies disrupt role scripts. Flex one backup framework if pairing fails.

Framework D: Boss participant

Goal: Influence matches where PvPvE rules allow boss defeat or major PvE finishers to decide outcomes.

Hub choices: Summon-heavy Bloodsworn and fate that boosts sustained damage phases—not burst-only—once confirmed in hub. Bring sustain to survive boss AOEs while players third-party.

Match habits: Stage consumables or cooldowns for boss enrage windows. Assume betrayal at execute range; position with escape routes.

Weaknesses: Boss lobbies may be rare in CNT playlists. Do not force this route every queue.

Framework E: CNT surveyor (for wiki contributors)

Goal: Gather facts for the community, not personal rank.

Hub choices: Minimal respec friction; rotate characters to sample kits.

Match habits: Screenshot UI strings, record event timings, log VP sources after each match. Note Nintendo Switch Online stability issues for Network Test errata.

Output: Feed Guides, Review summaries, and eventually evidence-based tier discussions.

What to avoid during early play

• Copying invented tier lists from forums
• Quoting DPS numbers from unrelated games
• Calling the product “released” or “launched”—it remains upcoming
• Ignoring First Blood ritual context while chasing frags only
• Skipping Builds hub philosophy when recommending fate paths to newcomers

Evolving these ideas post-CNT

After August test sessions, revise each framework with confirmed hub nodes, summon timings, and VP weights. Retire ideas that official patches contradict. Only then should Tier List pages assign letter grades—with citations.

Until that data lands, these early build ideas keep you honest, mobile, and ready for the Twilight of Humanity without pretending the meta already exists.