In an effort to reduce the spreading of misinformation I present: A comprehensive breakdown correcting some “common misconceptions” about Overwatch and its devs.

Overwatch2 - In an effort to reduce the spreading of misinformation I present: A comprehensive breakdown correcting some "common misconceptions" about Overwatch and its devs.

I know I'm going to get a lot of hate for this, and I'm not trying to say that anyone has done it intentionally, but I really wanted to talk about some of the misinformation that gets spread around the Overwatch community pretty regularly.

There's a handful of topics that whenever they come up people always love to quote something the devs have supposedly said. The only issue is that the devs have never said them. I wanted to take the next few minutes to address some of these and hopefully correct some of the commonly spread falsehoods.

  • Misconception 1. D.Va was a pro StarCraft player and Michael Chu retconned her to being a pro gamer.

Usually quoted as "it's a common misconception" due to
958493918756155392?lang=en - In an effort to reduce the spreading of misinformation I present: A comprehensive breakdown correcting some "common misconceptions" about Overwatch and its devs.

Michael using the phrase on twitter.

OypMqQIbeGE?t=1200 - In an effort to reduce the spreading of misinformation I present: A comprehensive breakdown correcting some "common misconceptions" about Overwatch and its devs.

From her first announcement at BlizzCon in 2015, D.Va was always referred to as a 'pro gamer' who played StarCraft, not a 'StarCraft pro'. Michael states

"So D.Va…is a, is a pro gamer. She's, you know, multiple time World Champion at StarCraft, all different kind of games. Everything that she plays, she's basically a pro.

Michael specifically stated it was a misconception that D.Va was a StarCraft pro before joining MEKA. Not that she wasn't one. Not that she never was one. That she wasn't one specifically before joining MEKA.

He later clarified that D.Va did play StarCraft, but it wasn't her skills in that game that led her to be recruited.

D.Va is absolutely a world champion professional gamer which was what got her recruited into MEKA in the first place. However her best game wasn't StarCraft (which was what I was attempting to clarify). We imagined that she was most known and specialized in a game with a skillset that was closer mapped to the skills that she (and the other MEKA pilots) utilized while piloting their mechs.

That said, D.Va has definitely played more than her fair share of StarCraft (as she references in some of her lines in Overwatch) and a slew of other games. Bonus fact: StarCraft is one of D.Va's father's favorite games! And he was pretty good at it.

He admits that it wasn't explicitly clear, but it was never a retcon.

  • Misconception 2. Geoff Goodman was the head/lead of balance on Heroes of the Storm and was terrible there, and then got moved (sometimes stated as fired and moved) over to Overwatch.

Geoff Goodman never worked on Heroes of the Storm. I couldn't find a source as to where this spread from, but someone has suggested that because Goodman's name appears in the credits of Heroes of the Storm that people assume that's how it became associated.

Geoff is indeed listed in the Heroes of the Storm credits, under Blizzard Development Family. This serves as literally a dump of any other dev in the Blizzard company. It's basically a "Friends and Family" or a "Pets" listing that some films have. At no point

does his name appear.

Geoff's history with Blizzard is that he worked as an encounter designer for World of Warcraft, then transitioned directly to Titan (which failed), but would eventually become Overwatch. He explicitly states:

While I have great respect for the designers over on the the Heroes of the Storm team, I never worked on that project other than occasionally sending feedback or talking to various designers over lunch etc.

  • Misconception 3. The devs said they didn't like one-hit KO/one-shot abilities, and then added Doomfist"

Jeff didn't say devs don't like one-shot.. It's a bit of a lengthy post from him, but it's the second last paragraph in particular that this misinformation started to spread from:

Players think that every change we make to hero has the intent of buffing or nerfing that hero. Changes to heroes are usually made to make the game better. That’s what we were trying to do with Roadhog. Our goal wasn’t a nerf – our intent wasn’t a nerf. Our intent was to try to remove a behavior that had become “not ok” with our player base – the one-shot combo. Maybe he needs to be adjusted again? Probably. I am just using this as an example that not everything is super black and white. There is a gray area in making the game feel good. Sometimes we need to hold our ground and not make dramatic swings to the game.


Note that he doesn't say that the devs have an issue with it. It was that the community had an issue with Roadhog and his ability to OHKO. Also note that he refers to it as "the one-shot combo ", and specifically talks about Roadhog. He doesn't mention things like Reinhardt's Charge, or Scatter Arrow (which still existed at the time).

Comments that he's saying here would actually somewhat echo why something like Scatter Arrow was ultimately removed: Players didn't like it. In the patch notes for why it was removed

Developers Comments: The goal of these Hanzo changes is to allow him to have new options and maintain his high damage output, *while removing the frustration of fighting against the old Scatter Arrow *. Hanzo is now much more mobile with his new Lunge ability, and with the combination of the bow projectile speed increase and the new Storm Arrows ability he can now deal his high damage more consistently than ever before.

People don't typically have an issue with Reinhardt being able to OHKO on a Charge. People don't typically have an issue with Doomfist being able to OHKO on Rocket Punch. But people did have issue with it on Roadhog, and they had it Hanzo. Hence why 2 have stay with little to no change, while others were balanced or removed accordingly.

  • Misconception 4. Tracers butt pose was removed because it was sexual and Blizzard responded to peer pressure

Partial credit here. Tracers butt posed was removed because it was a sexualised pose on Tracer, but not specifically because it was sexual by nature (I’ll explain the difference in a bit). Unfortunately I can't find the original post as it was made in the Beta forums which no longer exist, but Polygon basically posted most of the comment in a news article when this made the rounds. There’s also a thread on r/copypasta that looks to have the comment in its entirety, and given that it matches up up with what was reported by Polygon, it’s likely that this was the exact post. The part in particular is:

WHAT? What about this pose has anything to do with the character you're building in tracer? It's not fun, its not silly, it has nothing to do with being a fast elite killer. It just reduces tracer to another bland female sex symbol. We aren't looking at a widowmaker pose here, this isn't a character who is in part defined by flaunting her sexuality. This pose says to the player base, oh we've got all these cool diverse characters, but at any moment we are willing to reduce them to sex symbols to help boost our investment game.

To clarify: The posters issue wasn’t that Tracer had a suggestive pose. The issue was that it was out of character for Tracer to have such a suggestive pose. That regardless of the kind of personality the female character had they would/could still be given suggestive poses even if they were wildly out of character.

Since people have sometimes had difficulty understanding the difference between why it’s acceptable on some heroes and not on others, I like to give them this example: Imagine that Tracer had a Victory Pose that was her aggressively fronting on the player. Picture her doing Doomfist’s
Charging Victory pose: She’s wearing a scowl, baring her teeth, and looks like she’s ready to throw down. It would be weird. Nothing else about the character shows that level of aggressiveness. Nothing else about Tracer, no matter how dire the situation, has shown her in such a way. It’s the same thing with the Butt pose.

What works for one character doesn’t work for another. That’s why the poster even states that such a pose is acceptable on Widowmaker, as Widowmaker is presented as a “femme fatale” character. Doomfist is presented as an aggressive/powerful character. And Tracer is presented as

She's Fast. She's Silly. She's Kind. She's a good Friend. Her body seems to be comprised of about 95% spunk.

It's not that Tracer can't be aggressive or can't be suggestive. It's that literally nothing else about the character suggests those things because we've seen nothing else resembling that. Blizzard changed the pose to something that was more in character for Tracer.

And ye that about sums up the 4 big ones I've seen. Thank you for slogging your way through all of this. I appreciate the time you took to read (or skimmed, or didn't read cause "TL:DR" amiright?). EDIT: Also to anyone downvoting, would you please tell me why. This is nothing but aggregated information. I'm not sure exactly what there is to disagree with on this. I mean, do you disagree with facts?

Source: Original link

© Post "In an effort to reduce the spreading of misinformation I present: A comprehensive breakdown correcting some “common misconceptions” about Overwatch and its devs." for game Overwatch.

Top 10 Most Anticipated Video Games of 2020

2020 will have something to satisfy classic and modern gamers alike. To be eligible for the list, the game must be confirmed for 2020, or there should be good reason to expect its release in that year. Therefore, upcoming games with a mere announcement and no discernible release date will not be included.

Top 15 NEW Games of 2020 [FIRST HALF]

2020 has a ton to look forward to...in the video gaming world. Here are fifteen games we're looking forward to in the first half of 2020.

You Might Also Like

Leave a Reply

Your email address will not be published. Required fields are marked *