Guildrun Dragomir Guide: Devour, Builds & Red Rift

Guildrun Dragomir guide: quick answer

Dragomir is a melee Assassin whose Devour first gains Omnivamp, then deals damage scaled by Magic and Omnivamp, and only awards Shards if the cast gets the kill. The Sanguine has the strongest official current signal in Red Rift, though Update 0.5.1 reduced its immediate stability. The Greedy converts kills and spendable Shards into economy and permanent stats, while The Kingpin converts cumulative Shard generation into Rush-based Assassin/Vanguard Backup support. Every direction depends on starting the kill loop; bosses or high-health targets can stop it. This page uses current data, official patches, and community reports, not independent playtesting.

Dragomir at a glance

How Dragomir's Devour loop works

The current third-party data text gives Devour a strict order: Dragomir first gains 1 + 10% of Crit as Omnivamp, then deals 250 + 200% Magic + 1000% Omnivamp damage. If Devour completes the kill, it generates 2 + 2×Rank Shards. That ordering connects the stats: Crit improves the Omnivamp granted before the hit, and that Omnivamp immediately enters Devour's damage scaling. Omnivamp can also return health when damage is dealt, but it does not prevent control or guarantee survival before the cast.

The successful loop is: gain enough Mana for the first cast, reach a finishable target, gain Omnivamp, secure the Devour kill, receive Shards, then let the selected specialization turn those resources into permanent growth, another cast, or team support. A normal attack kill is not described as awarding Devour's Shards; the current text attaches the reward specifically to a Devour kill.

The negative loop matters just as much. If the first Devour does not kill, Dragomir receives no Devour Shards. Sanguine also misses its 60-Mana refund and Stealth, while Greedy loses the bonus kill income needed to fund later casts and purchases. Starting Mana, Mana regeneration, Magic, Crit, Omnivamp, target health, and safe access to that target all affect startup. No source supports a universal stat threshold or DPS conversion.

Guildrun Dragomir specializations

Dragomir's three current paths answer different resource questions: spend Shards for personal permanent growth, chain executions through on-kill refunds, or preserve cumulative Shard generation as a Backup team payoff. They are not a fixed all-mode ranking.

Community-reported Guildrun Dragomir build directions

There is no independently verified “best Dragomir build.” Current evidence supports three distinct directions with different triggers and opportunity costs. The 681-Shard screenshot, the bottom-right opener, and the Kingpin preference each remain conditional community evidence rather than baseline outcomes.

Guildrun Dragomir Red Rift strategy

Early Devour kills have extra value in Red Rift because the first Shards can fund Greedy growth, rerolls, or purchases before later fights. One player recommends placing Dragomir in the bottom-right for the first PvE fight to secure a Devour kill and two extra Shards. The author explicitly calls the post non-expert advice, so treat that tile as enemy-layout and version sensitive: use it only when the first target, starting debuff, and path to the kill match the example.

Small two- or three-hero cores can reduce exposure to the mode's Hero Death Limit and concentrate upgrades, but that is a Red Rift roster choice rather than a Dragomir-specific official rule. Greedy can improve early Shard economy; Sanguine can use kill refunds and Stealth to keep moving through ordinary waves; Kingpin can become a Backup payoff after enough Shards have been generated.

The recurring warning is boss conversion. Community reports describe Dragomir and similar on-kill economy heroes clearing normal rounds and creating resources while contributing less against a single high-health boss. A Red Rift plan should therefore watch whether the board has a reliable single-target carry, frontline, or control tool. Old Sanguine screenshots and videos are patch-sensitive after the 0.5.1 Omnivamp and Mana changes.

Shard economy: spend, bank, or scale

Shards are not one undifferentiated number. The current balance can be spent by the shop or by Greedy. The cumulative amount generated during the run is the wording used by Kingpin. Permanent Greedy stats are a third state already converted into Crit and Omnivamp. Keeping those values separate prevents a large generation total from being mistaken for a large current balance.

The real decision is opportunity cost: a Greedy cast can strengthen later Devours, but the same 2 Shards may have funded a reroll, item, relic, or upgrade that helps the entire team or fixes boss damage. Current public sources do not establish a fixed Shard-to-gold value or universal spending ratio.

Stats, items, relics, and rank modifiers

Build around the actual missing link in the Devour chain:

• Omnivamp enters Devour's damage formula and can sustain Dragomir after damage lands; it does not solve control, burst, or a lack of killable targets.
• Crit increases the Omnivamp gained at the start of Devour and can connect with random Assassin modifiers.
• Magic directly scales Devour damage but does not create Greedy's permanent growth by itself.
• Starting Mana and Mana regeneration decide how quickly the first Devour arrives and how painful a failed Sanguine execute becomes.
• Defense and Max HP matter when melee positioning makes Dragomir a soft frontliner, but durability cannot replace the damage required to secure the kill.
• Shard generation feeds Greedy economy or Kingpin's payoff, while its source and randomness still matter.

Shard Plunderer, Shard Collector, Critical Defenses, Critical Invigoration, Lurker, and From the Shadows are random class modifiers, not built-in Dragomir skills or guaranteed upgrades. Public examples do not compare enough item and relic alternatives to name a best-in-slot list. Treat on-kill Shard, Crit, Omnivamp, Mana, and survival effects as categories to evaluate against the current board rather than mandatory equipment.

Dragomir team synergies and role transitions

Dragomir most clearly needs help with the parts Devour cannot guarantee: softening the first target, absorbing initial focus, controlling dangerous enemies, and finishing a boss after the on-kill chain disappears. Existing community templates connect him with Assassin and Shard-focused teams, but those public lineups need 0.5.1 verification and do not prove a fixed Zuri/Hoyoung/Dragomir core.

Kingpin creates the most explicit class synergy: during Rush, cumulative Shard generation grants Crit and Omnivamp to Assassins and Vanguards from Backup. One Red Rift clear used Niklas and Dragomir as frontliners with Tilly as the carry, but that is one board, not evidence that Dragomir is a stable tank.

A useful role framework is early kills and economy → mid-run carry or soft frontline → continued Sanguine execution, Kingpin Backup, or replacement by stronger boss damage. It is a pivot framework, not a recommendation to Retrain every run.

Dragomir positioning and targeting

As a melee Assassin, Dragomir needs access to a target that Devour can finish without taking lethal focus before the cast. Sanguine complicates the formation because it teleports him behind the lowest-health enemy; inspect the expected landing area, nearby control, and the next enemy likely to target him instead of treating the starting hex as his final position.

A frontliner can absorb opening pressure, but fixed front-row or back-row rules are unreliable. Critical Defenses and From the Shadows, for example, come from different random modifier conditions and should not both be assumed. The community bottom-right Red Rift opener belongs to one first-fight layout. Re-evaluate it whenever the enemy formation or starting debuff changes.

Failure conditions and when to pivot

• The first Devour does not kill: look for target softening, earlier Mana, more direct scaling, or a different carry rather than waiting for an on-kill engine that never starts.
• Greedy consumes the shop budget: pause personal scaling when the team lacks frontline, control, boss damage, or a critical upgrade.
• Sanguine teleports into danger: change which enemy becomes lowest health, improve control, or abandon the chain-kill plan for that encounter.
• A boss offers no killable adds: convert Dragomir's earlier economy into a single-target answer instead of equating wave success with boss DPS.
• Kingpin lacks Rush or eligible heroes: keep Dragomir on board under a different path or spend the slot on a Backup effect the current team can trigger.
• A Retrain plan assumes permanent stats remain: treat two community observations as version-sensitive and recheck after patches; official notes document related historical bugs, not a current design guarantee.

Dragomir patch history

Frequently asked questions

Sources consulted

No YouTube video was used as evidence. The surfaced OnePunMan / Opem Red Rift video could not be verified for title, version, transcript, or Dragomir timestamps and remains a research lead only.