While I do certainly appreciate your creativity and intent, this is the least useful kind of feedback.

I addressed this in another thread, so I’ll let my previous words do their work;

I’ll add this to the summary we’ll send along tomorrow.

Hiya folks,

So everyone knows, the community team is monitoring and reading your immediate feedback to the new Experimental Card.

For those who have already taken the time to jump in and test the changes for yourself, thank you very much. I understand how these changes could cause a lot of critical conversation.

If I could ask one personal favor; avoiding hyperbole and invectives when sharing your experiences helps us community folks get to the meat of your feedback much quicker. It also makes it far more likely that we can respond to your thoughts with developer insight.

Let’s work together to make sure your experience is clearly communicated to the devs.

Overwatch Experimental Patch Notes – October 21, 2021

A new patch is now live on PC, Xbox, PlayStation, and Nintendo Switch. 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 ...

Sharing your own personal experience with the topic is always the most useful feedback we can receive. Tell us what’s causing friction, how it’s affecting your play experience, how it makes you feel.

We can pull numbers until we’re red in the face. Anecdotal feedback about player experience provides said numbers with context that’s impossible to quantify.

Hiya folks,

This issue is also is listed in the known issues thread found here

We are aware of an issue that is causing players to sometimes not receive credit for completing Junkenstein’s Revenge challenges. The team is actively working on a fix for this issue, which we expect to deploy in our next update. Until that time, we recommend supplementing your games played by playing additional matches in other modes.

We are working on a solution to ensure that all affected players receive their event rewards...

A few thoughts on this

• with rare exception, I don’t believe that any community is wholesale more or less toxic than any other community. People are people, and people have complicated personal experiences. Everyone has bad days.
• Even communities as amazing as the Overwatch community go through difficult times. It’s 100% understandable that extended gaps in communication and engagement would manifest itself in ways that, on the surface, make it look like it’s a “toxic” space.
• As the ...

By doing exactly what I’m doing in this thread

Focused feedback threads are something I can take into consideration. Normal caveats, no promises.

I tend to try to observe and be a participant in community conversation rather than leading it. I am self aware enough to understand that my presence in a thread is a way of guiding or leading community conversation, however I’d rather create space for players to help identify the best moments to jump in.

This is actually the least useful kind of feedback for almost any development process. Jumping straight to the solution without having a thorough understanding of the root cause of friction minimizes the role of designers and can often lead to “fixes” that don’t take in the full width and breadth of a given area of frustration.

We do love to see player inspired designs and ideas. We tend to contextualize the...

I often times find that the things that shouldn’t have to be said need to be said more frequently, if only to effectively manage expectations.

There’s a general rule of thumb that’s known by most community professionals:

• Less than 10% of all players will ever even look at your forums or owned channels

• Of that 10%, less than 10% will ever be an active participant in the conversation on these owned channels

It’s important to understand that this in no way diminishes the usefulness of community discussion hubs (like forums). Forums serve as a microcosm of the larger OW community, representing viewpoints from many different segments of players; casual, what we call “Core Players”, competitive players, representation from marginalized groups such as BIP...

For those that are interested, I recommend watching Stylosa’s breakdown. It’s a great synopsis of the AMA presented in a format you can have on in the background while listening to.

To be transparent with you: it’s challenging to schedule these earlier in the day due to the rigors of day to day development. Later in the afternoon is easier, with folks having more open schedules around then.

That said, it’s a point of feedback that I’m happy to take into consideration.

We’ll eventually get to the point where we can host a Q&A here in the forums. I still need to spend some more time on the boards, working with all of you, to create an environment that would lead to a productive session for all involved.

For future AMA’s it’s likely.

For this one, we specifically targeted the r/Competitiveoverwatch subreddit with minimal lead up in an effort to garner high quality questions, giving Geoff and Josh the chance to provide meaningful answers to hot questions in the community right now.

Thank you for putting all of this together Baja.

We hope everyone found the contents of yesterday’s AMA informative and useful

Hiya Booka.

We’re aware of the bug with Valk and are working on a fix for a future update.

Unfortunately I’m not prepared to comment about your Switch performance issues, however I can certain pass that feedback along to the team.

Thanks for reporting!

Disclaimer: This is not a complete list of all currently tracked issues affecting this build of Overwatch, rather this is a targeted list of some known specific issues with this release.

Patch 1.65

Heroes

Ana

• Subtitles are missing for one of Ana’s “No” voice lines.

Brigitte

• Brigitte’s Rocket Flail can appear translucent with the Vampire Hunter skin equipped.
...

Hey all,

We’re aware of this issue. It will be addressed in an upcoming update.

Sorry for the inconvenience. I feel your pain since I use this Highlight myself.