The Console Discussion Blizz Tracker and Console Bug Report Blizz Tracker show that’s just not true. Heck, the most recent blue post in a Console forum was just 22 hours ago…
And the one immediately prior to that was 4 days ago…
1 Like
Sometimes I hope that they will at least post something like "Good thread. I am here to tell you I have seen and read your thread. No promise on anything, but I do read your thread. 
"
1 Like
Posting in a Console Bug Report that a patch is live is not “community interaction” that I’m talking about.
You well know what I mean…where is the post about the borked S22 starting at the wrong time and introducing modded gear into Seasons for the first time?
It’s in the same section as the response to 2/3 Crusader clones disappear by leaping into the heavens and never coming back down, clones killing hardcore heroes, and so on.
Well, one fail was due to strange issue… I cleared the dungeon and at the end there were 4 or 5 mobs left on the counter so I couldn’t get Mastery. I tell you, the dungeon was dead empty but mob counter was not zero. I had enough time to spare so I checked everything, and no… I did not miss hidden rockworms and trust me, I won’t overlook four hidden rockworms 
The other three fails were all due to bites because the _#!°-&% rockworms wouldn’t come out and Twisters ignored them. It’s a non issue with Channel Meteor Shower, you can just leave and let the Meteors carpet bomb the worm, but as Twisters won’t pull rockworms, you may have to cast manually on top of them, if they miss. Argh, but enough of this, I don’t want to remember and it definitely doesn’t belong here
Overall, they have tried to listen. The 3 times I felt they banged the cat were:
-Letting WW/Rend release as on the PTR.
-Adding HFury to Aegis last minute and never fixing it.
-Releasing Etched Sigil in its broken and useless state.
Reflect has been in the game and has worked the same way for years. For example, clan member dropped wave of light bell on act2 key warden, resulting in 2 dead clan members.
1 Like
Yes, which means a player chose to make the attack. The player can’t stop the clone attacking and, last season, the lightning breath could actually hit dervishes which were off-screen, i.e. you couldn’t even see them to turn the breath away from them. The first indicator that dervishes were there was when the breath hit them and the hero died.
I’m fine with players causing their own deaths due to making attacks at a reflecting mob. I’m not okay with them dying due to a seasonal theme making it unavoidable.
2 Likes
well, we can express our dissatisfaction with that arrangement and hope whoever is in charge of what they can and can’t share gets the hint to do better. but i agree that blaming the CMs isn’t the way to go there since it’s not up to them what they’re allowed to share. they can, however, tell us that they’re not allowed to share something. like… when someone asks you something and the answer is someone else’s secret, just tell them that. because if you don’t, you’ll piss them off because you’re obviously hiding something or because they’ll feel like you’re lying to them. if you tell them why you can’t answer their question, they understand enough not to be mad at you over it (and then if they still are they’re the a-hole).
Something tells me that you’ll still have plenty of people who’ll be mad at the cms even if they respond with a “I’m not allowed to say”. There’s no winning for them. Again more communication is definitely needed, but it’s needed from Blizzard as a whole, not just their cms.
2 Likes
yeah, but as i said, then they’re the a-hole and not the CMs. if the CMs don’t at least say “i’m not allowed to say” then there’s a legitimate argument that they might be the a-hole in the situation.
1 Like
Gotta disagree there, there’s no legitimate reason for folks to be mad at the cms, for a change that the cm had nothing to do with and/or can do nothing about (and said folks are even aware that the cms had nothing to do with it), even if the cm don’t say anything on the matter. If folks want to think that the cms are jerks for not saying that their not allowed to answer, and such use that as a reason to get mad at the cms, then I’d say that those folks are pretty small minded imo. All getting mad at the cms is going to achieve is have them reluctant to inform the community of anything in the future. We’ve already seen that happen before.
2 Likes
and i gotta disagree with you. the CMs are 100% in control of what they tell us (since this is the internet i’ll point out that that’s hyperbole, but they have enough control over what they say) and if they don’t tell us that they aren’t allowed to tell us something, that’s on them. CMs are supposed to communicate with the community. i’m not sure how you manage to think people are jerks for being upset that they don’t do so better. if you get upset that people are mad at you for not doing a better job and you stop doing your job at all, how is that not being small minded? if the CMs do that, i’d say they need to grow up, get thicker skin, and learn to take criticism.
1 Like
Truth be told, I don’t consider such people (or anyone on these forums really) to be jerks. I do however consider them short minded, but only if they know that the CM had little to nothing to do with the decisions made by Blizzard and/or their developers, and yet still decide to blame the CM. It’s a tad worse imo, if the blame is solely on the fact that the CM doesn’t outrightly say that they’re not allowed to say…, since I imagine their silence would’ve said the same thing.
I mean just using this patch as an example with the etched sigil change. If in one of the many threads where wizards talked about how bad the etched sigil change was, we had a CM enter the discussion telling everyone that they (the CM) aren’t allow to say why the change was made; then I strongly believe that nothing would’ve changed. Wizards would still (rightfully imo) be upset as the etched sigil change wouldn’t suddenly become good, we’d still be in the dark about why the change took place or even the developer’s intent. The only thing we would’ve learned from that exchange is that the CM isn’t allowed to discuss the change, and such the community shouldn’t blame the CM… even though that should’ve been the case from the start.
Again, the lack of communication from Blizzard lies with Blizzard as a whole not solely their CMs.
2 Likes
but the problem is that that’s not what their silence says. that’s a generous interpretation of their silence, but generally people take silence as being ignored. hence all the bad will that could be avoided by saying “we can’t answer that.”
more accurately, we would learn that we aren’t being ignored which, if we are, would be something to blame the CMs for… so it seems like saying something is better than saying nothing.
so who is to blame for their silence if they could say something but instead say nothing?
yes, of course, but that doesn’t mean you ignore what the CMs can do.
it’s their job not to ignore the community, so if the community feels ignored there’s a problem. maybe that problem is a bunch of people are a-holes. maybe that problem is that the communication we’ve had hasn’t been effective. maybe there hasn’t been enough communication. i’m not claiming to know what exactly the problem is; i’m only claiming that at least two of those things are on the CMs regardless of what they’re allowed to tell us because their job is to manage the community.
hey, at least you PC players get Blue responses…problem with s22 and you have a blue response…consoles had a screwed up early season start and NADA from the CMs…nothing. And this is par for the course for us, over the past near 5 years. I think I’ve seen 2 Blues responses in total over that 5 years…yeah, a total of 2. And we’ve had so many issues it isn’t funny…constant end of season stuff ups, constant issues with bugs affecting game play, constant issues with game design that’s unique to consoles. none of it addressed by Blizzard…
I feel sorry for the lack of communication for my PC brethren, but spare a thought for us poor console players who have it far worse.
If folks know that the cms have nothing to do with Blizzard’s actions, and yet still get mad at them for being silent, then that again means those folks are being small minded.
Actually people would still feel ignored, especially those who offer feedback, suggestions, and/or alternatives, and Blizzard makes choices or changes that completely disregard said feedback. In that situation, it wouldn’t matter how many times the CM say “I can’t say”, players will still feel ignored since their feedback will feel like it amounted to nothing.
I would say that the folks who get mad at the CMs over decisions that the CM’s had nothing to do with, and because they’re silent on the matter (when the folks themselves know that the CM’s are limited on saying things), have nothing to blame but themselves.
Well their job includes more than that. However, if they’re not doing their job, then that once again falls onto Blizzard to correct, as having the community hounding at the CM’s isn’t going to achieve anything.
Yet this has been in D3 code for 5years or so. Nothing new. Yes though, I agree such seems unfair.
One of the most frustrating parts of being a CM (at least for Blizzard), is that you are not allowed to say “I can’t tell you that”.
Take for example the whole Diablo Immortal “we hear you thread”. It was a formatted statement approved by Legal and upper management. Nev was not allowed to comment further and certainly could not say “My bosses won’t let me say anything more”.
Sharing what they are not allowed to talk about, is pretty telling at times and can make management look pretty bad. Rightfully so sometimes! However there are often reasons for why they don’t want CMs to share something - that are valid.
Personally? I think the restrictions put on CMs are not in the best interest of Blizzard, transparency, or customer communications.
I will probably get in trouble if I give specific examples of things CMs should be able to answer, but that they had restrictions placed on them for. Really dumb stuff that makes no sense.
6 Likes
I’m not sure if I necessarily want to put blame on any one individual. As said, it’s an issue of being ordered to stay silent. Defy that order and you’re unemployed. My frustration regarding this policy of maintaining silence is on the company as a whole. They have to be able to see that it’s having a negative impact.
Others have said: “Don’t shoot the messenger.” We can’t, because they never sent one.
1 Like