Doctrine and the Two Infuse Charges: Overwatch 2 Bets on a Vampiric Support in a Data Void

On the BlizzCon 2026 stage, when the Doctrine reveal trailer ended, what stayed with me was not the image of a support in a red cloak, but a detail in the bottom-right corner of the interface: two dots beside the Infuse ability bar. Two. Not three, not one. Exactly two.

In more than fourteen years of watching hero shooters evolve, I have learned one thing: character design usually tells its story through very small numbers. A cooldown, an energy threshold, a one-second difference - that is where a developer bets on how players will make decisions. Doctrine's two Infuse charges, in my experience, are not an incidental detail. They are a statement about how Blizzard wants to shape the tempo of the support role in the coming season.

I have to say something uncomfortable before going deeper: this article is built on a near-empty data foundation. World Cup 2026 taught me that the box score does not know how to play football; that is true for football, and even truer for a game where every number depends on the patch. With Overwatch 2, the only number I trust is the number I have counted myself from match footage. Everything else is a hypothesis waiting to be confirmed.

Context: a new hero inside a programmed cycle

What context does Doctrine appear in? To answer, I have to step back a few paces. Overwatch 2 launched officially in October 2026, inheriting a title that had defined an entire generation of hero shooters. Since then, Blizzard has run what I call the "new hero cycle": every few months, a hero is released to refresh the pool of choices. Each time, the community rushes to debate whether the new hero will overturn the meta or is just a faint addition. And each time, I remind myself: do not let the applause of the reveal drown out the cracking of the balance system.

Before Doctrine, the support role in Overwatch 2 had gone through a period of relative stability. The mainstay supports in tournaments generally fall into two groups: pure healers and "hybrid" supports with self-defense or pressure tools. Doctrine, described as a vampiric support, clearly targets the second group - heroes that can sustain life while not being entirely dependent on teammates.

The timing is notable. BlizzCon 2026, according to what was presented, is where Doctrine was introduced for the fifth season. This is not a random moment. In the history of hero shooters, introducing a new support usually coincides with the developer wanting to adjust the speed of the match: if the meta is too fast, they add a support with sustain; if the meta is too slow, they add a hero with pressure.

With Doctrine, I believe the intention leans toward the first group: prolong matches, create prolonged teamfights. But this is speculation. And speculation is not enough to write a script.

Look at what we actually have. Doctrine is a support. Doctrine has an ability called Infuse, with two charges. Doctrine has a Perk system, with two Perks named Cost of Life and Transfusion. Doctrine has a "vampiric" theme. Beyond these points, there is no other data. No healing-per-second figure, no Infuse cooldown, no damage, no health, no movement speed. No PTR testing. No win rate. No pick rate.

This is where I have to say my second line: the missing footage always contains something someone does not want us to know. In this case, the "missing footage" is not a cut segment, but the entire quantitative data section. A new-hero reveal that comes with no numbers, to me, is a reveal telling players to trust feeling instead of evidence.

The Infuse mechanic: two charges and a psychological threshold

Now let us go into the part I can analyze seriously: the mechanic design.

Infuse is the heart of Doctrine. According to what was presented, Infuse has two charges and allows Doctrine to amplify other abilities. Amplify what? According to the description, at least movement and healing output. In other words, Infuse is not a standalone ability, but a decision layer sitting on top of other abilities.

This is a familiar design pattern, but also a dangerous one. When you place a limited resource - two charges - on top of abilities, you force players to choose between "saving" and "spending". This is what I call tactical tension. For a support, this tension has a very concrete consequence: players may become overly cautious, holding both Infuse charges for emergencies, and thus reducing total healing output for most of the match.

I have seen this in many other games. In football, it is the story of a midfielder who holds the ball too long for fear of losing it. In a high-tempo match, excessive caution becomes a form of error. And in Overwatch, where a one-second delay can kill a teammate, support over-caution can decide win or loss.

The core point is this: two Infuse charges are not just a resource number, but a psychological threshold. It shapes how players perceive scarcity. If Blizzard sets the cooldown of each charge reasonably, Doctrine will be a hero that requires players to read the match continuously. If not, Doctrine will either be too strong - because it regenerates too fast - or too weak - because it regenerates too slowly.

I have spent years cross-checking design decisions against competitive results. What I have drawn is this: in games with scarce resources, professional players usually optimize in one of two directions. The first is to maximize the number of uses, accepting the risk of waste. The second is to optimize timing, accepting fewer total uses. Doctrine, with two Infuse charges, will push players into a struggle between these two directions.

The vampiric theme and the question of independence

Next is the vampiric theme. In hero shooter history, vampiric heroes usually share one trait: they convert damage into life. For a support, this means Doctrine can sustain itself without teammates, something historically considered imbalanced. A support with strong self-healing is often called an "independent support", and in tournaments it can change how a team arranges its composition.

Imagine a team with Doctrine. If Doctrine can sustain itself, that team can devote fewer resources to protecting the support, and use those resources to attack. This is a change that can ripple: it affects not only the support slot, but also how tanks and DPS make decisions. A new hero in the support role can reshape the entire team composition, if it is strong enough to become mandatory.

But of course, that is an "if". And this "if" is exactly where the empty data causes the biggest problem.

I remind myself of my professional principle: I write documentaries to answer questions, not to confirm answers. With Doctrine, I do not yet have an answer. I only have questions. And my job is to present the questions honestly, rather than fill the gaps with belief.

The Perk system: two playstyles in one hero

The Perk system is another notable part. Overwatch 2 introduced the Perk system as a customization layer for heroes, allowing players to adjust abilities to their style. The two Perks named for Doctrine are Cost of Life and Transfusion. The names hint at it: Cost of Life and Transfusion. Both sit within the theme of vampirism and life sustain.

This makes me think of one possibility: Doctrine may have two different playstyles, one leaning toward sacrifice and one toward conversion. If so, Doctrine will be a hero with high depth, suited to players who enjoy research. But again, this is inference from names, not from data.

In the history of games with ability customization systems, I notice a pattern: the more complex the system, the wider the gap between good players and average players. For a competitive game, this can be good - it creates differentiation - or bad - it reduces accessibility. Doctrine, if it has two highly strategic Perks, will sit on the "good for the skilled" side. But that also means at lower levels, Doctrine may be ignored.

Three tests for a new hero

Competitively, a new hero in the support role can be evaluated through three questions. First, can it replace an existing choice? Second, can it create a new tactic? Third, can it change how teams prepare for opponents?

With Doctrine, the answers to all three questions depend on numbers we do not have. A strong vampiric support can replace traditional healers, but only if it heals enough. A weak vampiric support will replace no one. This is a simple truth often overlooked in discussions of new heroes.

Looking at history, I recall many cases of new heroes announced with grand promises, then adjusted repeatedly. In football, the same happens with big-money signings: a striker introduced as "will change the club", then benched a few months later. The difference is that in football, we have data to evaluate; in a hero reveal, we only have promises.

This is where I have to mention Schalke again. When Schalke was empty, I finally heard the cracking of an entire system. That story taught me that collapse usually does not begin where the public looks. It begins deeper: finance, personnel, strategy. For a new hero, that deeper layer is mechanic design and balance. If that layer has a problem, no grand reveal can save it.

The contrarian angle: being unique is not automatically good

Now comes the part I want to call the contrarian angle. There is an implicit assumption in most discussions of Doctrine: that the more unique a hero is, the better. I disagree.

In sports, uniqueness only has value when it is converted into results. A player with a strange style but no effectiveness is quickly discarded. For a hero, uniqueness can become a burden if players need too much time to master it. In a competitive game, time is a scarce resource. Every hour spent practicing Doctrine is an hour not spent on other heroes.

The contrarian point is: a complex hero like Doctrine can fail not because it is too weak, but because it is too hard to become worthwhile. If the cost of mastering Infuse exceeds the reward received, professional teams will ignore it - no matter how entertaining it is to watch.

And this is where the lack of data becomes a strategic problem, not just an informational one. No PTR win rate, no professional feedback, nothing to evaluate Doctrine's cost-benefit. We are discussing a hero we have never seen played in a real match.

Be careful of another trap: the trap of collective excitement. When a new hero is announced, the community tends to produce evaluations that are too high or too low. Both are noise. And noise helps no one make a better decision.

I saw this at World Cup 2026. Before the tournament, people praised Germany. After the first two matches, people buried them. Both were evaluations built on emotion, not data. And the final result - elimination in the group stage - proved neither. It only proved that those who made extreme evaluations had ignored the signals in the middle.

Signals to watch

If I had to make a list of what to watch in the coming months, it would have four items.

First, the cooldown of each Infuse charge. This is the most important number, because it decides Doctrine's tempo.

Second, the healing-per-charge ratio. If this number is low, Doctrine will not be able to compete with existing supports.

Third, Doctrine's presence in professional scrims. If top teams start testing it, that is a positive sign.

Fourth, community feedback on the feel of playing it. A hero can be strong on paper but unpleasant to play, and that affects pick rate.

None of these items has data at present. All are blank boxes waiting to be filled.

Based on my experience watching matches, I have learned that such blank boxes are usually filled faster than people think. Once Doctrine appears on the PTR, the community will have data within days. But until then, every conclusion is only speculation.

In Germany, where I live and work, the esports community has an interesting trait: it is very sensitive to unsupported claims. Perhaps that is the legacy of a technical culture. When I exchange with German colleagues about Doctrine, the common response is: "Sounds good, but where are the numbers?" That is also my question.

History as a mirror

Looking back at the history of hero shooters, I see a recurring pattern. A new hero is announced with grand promises. The community splits into two camps: believers and skeptics. After a few weeks on the PTR, data starts to appear. If the hero is strong, it gets adjusted down. If weak, buffed up. Finally, after a few months, the new hero finds a stable position - or disappears from the pick list.

With Doctrine, we are at the first stage of this cycle: the stage of promises. And as I said, promises are not enough to write a script.

In football, I have seen the same with signings. A player is signed for a high fee, introduced grandly, and then the season begins. Afterward, only data can answer the question: was it a good signing or not. For a hero, the "season" is the subsequent patches.

What I want to emphasize is: I am not against innovation. I am against evaluating innovation by belief. Blizzard has the right to experiment with unique ideas - that is how the industry moves forward. But observers have the right to demand evidence - that is how understanding moves forward. The two do not conflict; they complement each other.

Conclusion: questions instead of answers

The question I leave for myself, and for those watching, is not "is Doctrine strong". The question is: does a vampiric support actually make Overwatch 2 more interesting, or just make matches longer? When the first test build appears, I will count every number. And I will rewrite from there.