Overwatch

Overwatch Dev Tracker




30 Jan

Comment

workshop creators will really love some of the changes Zach and Dan made to the feature. they listened to their feedback very closely and all of it is in response to what creators wanted. really proud of them for their work!

Comment

you can limit heroes in Custom Game. give it try!

Comment

we talked about a season rotation but taking a hero out of play for 2 months makes us a bit nervous. never say never but it’s not our first instinct…

Comment

regardless of if we do a different scoreboard for OW2, we definitely want to do more with stats and provide more statistics to players

Comment

no [i have to type twenty characters even though i work here]

Comment

The discussion is open for OW2.

Comment

Yes. We’ve definitely considered it. Let’s try a week and see how it feels and if we need to make adjustments we will. But yeah… we’ve talked about rotating every day. We’ve also talked about rotating every match. We don’t like going longer than a week because we want more heroes played… but open to feedback.

Comment

The card won’t be ready until end of Feb.

For now, you can test it by not playing Torb for the week.

Next week, don’t play Symmetra.

=]

only playing with ya…

Comment

For the first 5 weeks, we will be trying a range to see what feel right. We’ve architected this system so that we can update the hero pools without the need to patch. So we’ll be monitoring feedback very closely, experimenting a bit with the pool and adapting our strategy as time goes on.

Comment

Thanks for the feedback!

Oddly, we’re not viewing this change as dramatic, scary or impactful as the decision to pursue Hero Limits or our decision to implement Role Queue. Hero Pools will ...

Read more
Comment

Originally posted by BillWarnecke

Hey there, we're looking into this issue. While we work on fixing the problem you may end up in games in other datacenters outside of SA, sorry for the hassle.

Servers are coming back up in the SAE1 site now, sorry again for the disruption. Cheers

Comment

Hey there, we're looking into this issue. While we work on fixing the problem you may end up in games in other datacenters outside of SA, sorry for the hassle.


28 Jan

Post

Overwatch Retail Patch Notes – Jan 28, 2020

A new patch is now live on Windows PC, Nintendo Switch, PlayStation 4, and Xbox One. Read below to learn more about the latest changes.

To share your feedback, please post in the General Discussion forum
For a list of known issues, visit our Bug Report forum.
For troubleshooting assistance, visit our ...

Read more

27 Jan

An actor, clothed in vibrant, intricately embellished garb, moves synchronously with the beat of percussion-heavy music. A drumbeat and fan-flutter later, they don a crimson face that scowls at the audience; with a wave of their hand, that guise is gone, replaced by a pale, smirking mask, the edges of its lips quirked upwards in an uncanny jester’s grin.

How do they accomplish such feats of suspenseful fun and sleight-of-hand?

That’s a secret the two hundred remaining Bian Lian masters—and, now, Sombra, having joined their ranks with her new legendary Face Changer skin created in celebration of the 2020 Lunar New Year—will never divulge.

Bian Lian, known colloquially in the West as “face changing,” originated in the Qing Dynasty during the seventeeth century as a subgenre of the Sichuan opera. The art used to be simple, with performers only changing a few faces per performance; now, most professionals can swap through more than eighteen masks in a single sh...

Read more

24 Jan

Comment

Originally posted by McManus26

Why not label it 1.44.1 ? Why the extra zero ? Is there more important stuff coming ?

I tend to manage our branches, in this case Overwatch League will be using “1.44.1.0”. It was intentional that they were downstream of all 1.44 live changes.

The final digit in our branches is used when we have a patch that is not protocol/data compatible with what is already released. That was the case for this mid cycle bug fix and balance update, so it became “1.44.0.1”.

In practice, because we do a “major” revision about once a month, we don’t end up having too many cases where we need the last 2 digits for the branch. When we do have cases like this it’s sort of confusing for the team (for people who don’t look at branch details every day).

We could probably be more clever but we have a pretty significant build infrastructure built around this convention, so for now it’s not changing. :)

Cheers