Overwatch Dev Tracker

Yes, mainly a look into the world of some ability overlap

Hey all, my apologies for this issue. We were testing some changes to Group Respawn in the midseason patch and intended to revert them, but I failed to undo an important element.

The bug we have right now is that if any hero could be Group Respawned, all heroes will be Group Respawned (on a given team - the bug doesn't affect the other team). This is bad, because it means your respawn time can be averaged several more times than intended, leading to the 20+ second respawn times players are talking about in this thread. If you see a longer black screen when respawning, that's caused by the bug. Fortunately Group Respawn is still disabled in Overtime, so at least this won't stack as some players in this thread have hypothesized.

We're working on a fix, but it won't be ready before the weekend.

Replying here too since the most upvoted post changed. Yeah, it's a really nuanced topic and the example I used wasn't great because this was a problem for our whole cast and Mercy was not the biggest problem.

Just to be clear to anyone reading this after only watching this clip, this was a system we removed many years ago in OW1 and the effects of the problems it caused were erased long ago too.

Some of this was for Widow duels - there were spots we saw Widows dueling each other (from statue to spawn on King's Row was one sightline we used) and just not dying even though we felt the distance should have resulted in a kill. Should still be safe from one-shot when playing 250hp heroes further back (behind car on first point, ledge above is fine too for King's Row for example). If it ends up shifting her effective range too much, it could get rolled back.

Oh and I'm a single Winter, not plural Winters as this post title implies.

Couldn't have said it better myself, other than to just clarify this was OW1 only problem and was fixed years ago.

Her melee was only dealing 30 damage instead of 40 (the new increased amount)

Trending in the right direction here design wise for a smaller set of changes. Hopefully won't have y'all waiting too long, this won't be a Roadhog in terms of timeline.

Thank you so much for bringing this forged version of a real customer service ticket to our attention!  Given that there is a real customer service ticket number with the same digits used in this fake ticket, we think it's pretty likely that this post was written with the intent to hurt faith in the reporting system by someone that didn't learn their lesson.  This type of forgery is new for us on OW2, so we'll be watching more carefully for this type of thing going forward!

For any real players reading this that have seen messages similar to these, we're working to improve our process for what chat is included in the chat history section.  We know we can do better here when it comes to showing the most disruptive language that was used that resulted in the account action.

Anti-Heal is a useful mechanic for the overall health of the game as it helps to ensure that healing never gets too far out of control. The complaints around it feeling oppressive are understandable (as debuffs are never something players enjoy being affected by) and we'll be looking for ways to soften its impact while keeping Ana a viable hero.

The simplest solution here is just decreasing the duration of the effect though there is certainly a point where it swings from feeling OP to not useful enough if the time is too low to really capitalize on.

The reaction around it does also suggest that healing is probably too impactful overall so we'll be looking to address that in the near future as well, whether that is handled in the case of individual heroes like Roadhog Take a Breather or more systemically.

Very well at all rank thresholds, one of the reasons we are putting out some initial changes today to lower his damage output (which also affects his sustain).

During the BlizzCon trial Mauga was actually performing much better than community perception, but there were some issues with his survivability and things like his head hitbox size. We pushed him a bit further with the understanding that we would act quick if things weren't in line with our overall balance goals. Today's nerfs should give us a better look at where he will end up once he enters Competitive.

The way Mauga was designed invites players to get up into the thick of the fight all together with his team. Overrun encourages players to land directly on top of their opponents and his dual-fire mode is more effective at close ranges. Cardiac Overdrive and Cage Fight invite his teammates to stay close to him to take advantage of their defensive benefits. This can cause Mauga's to go into a lot of situations that are more precarious and will result in him struggling if his team isn't on the same page. Mauga's abilities are versatile and have uses in situations where they don't get full value. Overrun, for example, lets players run away from a fight with damage resistance, so they can poke from farther away with alternating his single-fire chain guns. As time goes on and players explore Mauga's kit more, more nuanced uses of his abilities should hopefully make playing as him less polarizing. His abilities also have a lot of tuning points in regards to both how he helps himself and ...

Two Maugas enter a Cage Fight, one leaves? both leave? There's a lot of Mauga right now, more than any other hero. He's responsible for many deaths, even his own.

An important aspect of our hero design philosophy is that heroes should have clear strengths and weaknesses to create more varied and interesting gameplay. When we look to buff a hero for example, we want to keep this in mind and typically try to focus on a heroes intended strengths rather than clearing away their weaknesses.

We do want to avoid counters being too easy and effective without adequate counterplay options. There is a broad goal of making sure every hero choice is viable in some capacity and feels good to play, while hopefully not feeling too unfair to play against.

Some direct matchups are not reasonably close, like Winston vs Roadhog, but we don't strictly balance off of 1v1 matchups as Overwatch is a team game (Winston has a good chance to win by going after everyone that is not Roadhog for example).

Generally we've found that when the heroes are balanced closely enough, individual player performance and teamwork has significantly more impa...

Want to clarify here that the first time we do this it will be for a limited time as an experiment. With that said, we're still discussing how exactly it will work in the match flow and where we put this experiment. Should everyone get a ban against one hero in their role? Should this experiment actually run in competitive for a weekend or should it get its own queue? How long is this phase before you select heroes, how much time does a team need to feel like they are strategizing but not so long it significantly increases the match length?

Those are the sorts of questions we talk about in our design meetings around this. I think any sort of ban system in Overwatch has the chance to be fairly polarizing, especially when your main gets banned. The point of the experiment will be to gather some initial feedback and make sure that if we ever move forward with permanently adding bans, we've covered all our bases.

Right now, there's not a strong desire to potentially make such a swap. Heat systems give significantly more damage uptime compared to traditional ammo systems. They're functionally just a constant reload you can cancel at anytime, unless you hit 0 ammo. The reload time gives players a window of opportunity to avoid his fire.

Reaper is also on that list! Had our first brainstorm and have aligned on our overall goals for what we want to see with Reaper's abilities. One of those goals is modernizing Reaper's kit, Shadow Step and Wraith Form standing out there.

We may also explore some new abilities for Reaper (on the right-click), but don't want to take the space just because it's available. If we add something there, we'll want it to give him slightly more decision making in-combat than he has currently.

This is usually trying to be consistent with game mechanics. We do make exceptions when necessary for the sake of game balance, but the less often we need to do that the easier it is for players to learn and understand these many interactions across multiple heroes.

Mauga's ultimate tethers are applying what we internally call "Mobility Lock" which disables movement skills. Other things that use this mobility lock are Junkrat Steel Trap, Cassidy Magnetic Grenade hinder effect, Zarya and Sigma ultimates. For gameplay consistency, you should be able to use Symmetra Teleporter and Lifeweaver's Lifegrip against those abilities.

We are reducing his damage, and those changes went live in this morning's hotfix patch (https://overwatch.blizzard.com/news/patch-notes/). This change will inadvertently affect how much life steal he receives during Cardiac Overdrive, making him a little less tanky.

Game design goes through a lot of iteration to find the most engaging combination of mechanics within the scope of our goals. We naturally try a lot of prototype variations even with a strong starting idea.

We tried a few alternate mobility abilities for Overrun. One of the first ideas was a short range dash that would toss enemies into the air behind him if you impacted them. It was fun to use but the transition from third person to first person and trying to turn around to shoot them wasn't easy, and solutions like automatically doing a 180 with the camera took away control from players.

The weapons had a couple alternates such as a flamethrower or incendiary grenade launchers. There were a few attempts at having two very different firing weapons in each hand, so one being hitscan like it is now and the other being a travel time projectile. It didn't play as well when trying to fire both at the same time unfortunately, especially in versions where they have differ...