The Duskbloods PvPvE Rules
Fight seven other Bloodsworn and the map itself while Victory Points decide who leaves ahead.
The Duskbloods advertises itself as PvPvE: every Dusk Battle asks you to manage player threats, environmental dangers, and objective swings at the same time. Nintendo and FromSoftware marketing for the upcoming Switch 2 title consistently highlights Victory Points as a scoring spine, last-player-standing as a familiar finish condition, and alternative win paths such as defeating a boss when the mode demands it. This guide organises those pillars without inventing numeric tables the public build has not shown.
The three pressures in every match
First, PvP: up to eight Bloodsworn with unique weapons—including firearms—and personal summons contest the same space. Second, PvE: map-native enemies, hazards, or set-piece threats drain healing, ammo equivalents, and attention. Third, objectives: dynamic events, role payouts, and First Blood ritual progress pull you off pure fragging. Successful players triage constantly: is that duel worth more VP than securing an event chest before the stone face rotates the arena?
Victory Points: the default scoring language
Victory Points appear in official gameplay explanations as the measure that decides outcomes alongside eliminations. VP likely accrues from kills, assists, event participation, role fulfillment, survival time, or bonus actions tied to the Twilight fiction—exact weights remain unconfirmed pre-Network Test.
Treat VP as the reason matches can end with ambiguous kill counts. A Bloodsworn who avoids early brawls, farms PvE during a double-score window, and completes a Destined Companion rendezvous might leapfrog a high-frags duelist. Document observed sources during CNT and share them through Guides rather than guessing coefficients.
Because VP matters, Builds should include a scoring route, not only a damage route. Mobility tools, entity summons that clear adds quickly, and fate paths that boost event interaction may outperform raw duel stats on certain Maps.
Last-player-standing structure
Official descriptions call last-player-standing a common match format—not the only one. In LMS modes, the closing circle of survivors often coincides with escalated PvE or a forced relocation event. Expect healing scarcity and third-party etiquette to dominate the final minute.
LMS rewards patient Bloodsworn who preserve summon cooldowns for the endgame. It punishes players who burn resources winning mid-map duels that grant fewer VP than surviving the collapse. Pair LMS prep with Controls drills so movement tech is muscle memory before you queue.
Boss defeat and alternate win conditions
Some matches reportedly allow boss defeat—or comparable PvE finishers—as an alternative to outright elimination wins. That option reinforces the PvPvE identity: a squad can theoretically cooperate long enough to drop a boss, then turn on each other for First Blood relevance.
When boss routes exist, watch telegraphs shared across all players—inviting betrayal the moment the boss enters execute range. First Blood lore may flavour why stealing the final hit matters even if VP already ranks you highly.
Eliminations, assists, and third parties
Eliminations remain visually satisfying and likely feed VP, but they also attract third-party cleanup. Firearms shown in reveal media enable cross-map sniping; melee Bloodsworn with entity assists can punish reload windows. The social layer adds Destined Rivals who may ignore free kills to chase their designated opponent—creating windows for low-HP players to reset.
Do not cite unverified TTK or headshot multipliers. Instead, note weapon roles: rifle space control, shotgun breach, hybrid melee/gun kits, and summon finishers.
Alliances, betrayal, and voiceless negotiation
Without assuming a ping system, expect emotes, proximity, and shared PvE danger to signal temporary truces. Companion roles formalise some alliances; rival roles hard-counter them. Even free agents should read Blood history and fate markers if the UI exposes them—walking past a companion prompt may forfeit a reward you cannot earn later.
Match flow from queue to hub return
After hub customisation documented in Hub customisation, you queue, load into a map blending gothic and early-modern motifs, play through VP swings, then extract to the hub with rewards win or lose. Losses should still teach which PvPvE axes you neglected—event timing, add control, or endgame positioning.
Schedule around Network Test windows if you are selected; preload when Nintendo allows so you spend session time learning VP sources, not downloading.
Post-CNT analysis without fake tiers
Once data exists, compare Bloodsworn by VP efficiency per role, not invented DPS ranks. Tier List pages should wait for reproducible metrics. Review pieces can capture feel—gun heft, summon reliability—while this wiki tracks verifiable scoring behaviour.
Related reading
- Gameplay hub — overview of all systems
- First Blood — ritual prize context
- Dynamic events — mid-match rule changes
- Early build ideas — honest prep frameworks
Frequently Asked Questions
Quick answers drawn from official Network Test and Creator’s Voice details.
What does PvPvE mean in The Duskbloods?
You simultaneously fight **other Bloodsworn (PvP)** and **map threats (PvE)** while chasing objectives like Victory Points and First Blood.
How do Victory Points work?
VP **decides match outcomes** per official copy. Exact earning rates are not public—record them during the Closed Network Test instead of trusting fabricated values.
Is every match last-player-standing?
LMS is described as **common**, not universal. Some modes may end via **boss defeat** or event-driven conditions.
Can I win without the most kills?
If VP comes from events, roles, or survival, a lower-kill player can still **win or place highly**—confirm sources when you play.
Does PvPvE affect build choice?
Yes. Builds must account for add clear, event rotation, and duel strength. Start with [Builds hub](/builds/) and [early ideas](/builds/early-ideas/).