D.Mon got two hotfixes in four days: the cast-time cuts are the ones you feel

If you tried D.Mon on launch day and put her down, the two August hotfixes changed her launch kit. Blizzard hotfixed Overwatch's new tank twice in the first four days of Season 4 — on 12 August and again on 14 August — and the two passes did completely different jobs.

The 12 August pass raised damage and eased fuel use. The 14 August pass cut ability delays and fixed more bugs. This analysis describes those August changes; check later notes before using the values as current advice.

What the two hotfixes actually changed#

12 August. Plasma Saber damage went from 60 to 65. Fusion Repeater damage went from 15 to 16, and its cooldown from 6 seconds to 4. Propulsors got the biggest single adjustment: fuel drain rate dropped from 40 to 25, and fuel regeneration rose from 15 to 22.5.

14 August. Surging Strike cast time went from 0.15 seconds to 0.05, and its recovery from 0.25 to 0.15. Fusion Repeater cast time went from 0.3 to 0.2, and its recovery from 0.5 to 0.2. In the same pass Blizzard fixed an issue where D.Mon could be damaged from the front while Power Barrier was deployed, and adjusted the height of the mech's head hitbox to sit more flush with the model.

The 14 August notes also list fixes for Fusion Repeater hits that could fail to register, Limit Break not correctly granting overhealth for targets hit, and Toggle Propulsors not working on console. The 12 August notes separately fixed a Power Barrier protection issue while Fusion Repeater was active.

The cast-time change#

This part is analysis rather than patch notes, so treat it as a reading of the numbers rather than a measurement.

Cast time and recovery are the windows where you have committed to an ability and cannot do anything else. Add them up. Surging Strike went from 0.4 seconds of committed time to 0.2. Fusion Repeater went from 0.8 to 0.4. Both were halved.

That can matter as much as five points of saber damage because of what D.Mon's kit asks you to do. Power Barrier is a held frontal shield; Surging Strike is the strike you get while it is deployed, pushing enemies back. The whole design points at going forward behind the barrier and hitting something at the end of it. A 0.4-second commitment on the strike gives an opponent more time to react than a 0.2-second one. The notes establish the timing change, not a guaranteed outcome against a player.

The same logic applies to Fusion Repeater. Halving the time it takes to bring up and put away can make switching to it mid-engagement less costly.

The fuel change is what altered your positioning#

Propulsors burning 25 fuel per second instead of 40 is a 37.5% cut in the listed drain rate, and regeneration rising from 15 to 22.5 refills the meter faster. A lower resource cost can create more room to reposition; the notes do not show how often that changed match decisions.

Read that alongside the barrier fixes. The 12 August issue involved deploying Power Barrier while Fusion Repeater was active; the 14 August issue involved frontal damage while it was deployed. Both fixes matter to a forward push, but the notes do not measure how often either bug affected a fight.

What Blizzard has not published#

The cited notes give ability values and fixes, without pick rate, win rate or an internal balance target. They cannot establish where D.Mon ranked among tanks after the hotfixes, much less where she ranks now.

D.Mon is listed as a Tank with the Stalwart sub-role, and arrived with Season 4: Heroes of Busan on 11 August, alongside reworked Busan, Paraíso and Eichenwalde, a rebuilt Battle Pass, and a new Emerald rank between Platinum and Diamond. The season's Team Drives competitive event was scheduled for 4–7 September; that window has passed.

What to do with this#

For the August version of D.Mon, a useful sequence to reconsider was moving with Propulsors and Power Barrier, then using Surging Strike while the barrier was deployed. Her official ability page describes that interaction, and the hotfixes lowered fuel drain and shortened the strike's cast and recovery. Check current notes and test the sequence in the current client before using this historical analysis as a build recommendation.

The saber's five-point damage increase was one part of a broader launch-week adjustment.