Maybe i should start playing my priest!
I thought I had a new button to press but it wasnât. Maul ânow Razeâ hitting three targets is kinda cool though but I wish it hit harder. It feels somehow weaker. Hopefully it is benefiting from the talents that affected MaulâŚ? (this is blizz weâre talking about) 
I donât Boom enough to know a bloody thing except the aoe now scares the literal bejeezus outta me. I NEEDED that boundary line. I am not touching that button in LFR anymore within a mile of untanked mobs; I ainât gonna be that guy.
Need to check out Resto still. I donât Feral but i liked what I saw in the patch notes. 
1 Like
Lynneth, anyone theyâve hired POST Scandals knows this, and shouldnât expect immediate change, that is unrealistic.
Its definitely not a âhandful.â Its been an on going issue for some time and is generally the most complained about aspect of the game. Performing poorly results in a lack of consumers. it is what it is.
âStop paying their paycheckâ â probably the most useless advice yet, and least constructive. Giving people an opportunity to fix their issue is far better, and if firing devs is required then I think it is more productive. Similarly, if you have a bad chef, you fire the chef or go out of business. The advice youâre giving is in support of the latter.
I wouldnât say iâm angry, but iâm disheartened
All i want is infusion of light back
I love the new temporal anomaly rework.
Will check out the trading post when it opens and have no reason to do the event.
1 Like
agreed and signed
Bug fixes for Holy and Arcane are nice, as are bug fixes for any class. Holy talent changes I have yet to test as I opt for a more heal oriented build in keys than the Blaze build. I donât do much world content so no opinion on the storm thing. Excited for the Trading Post, but understanding as to why itâs Feb 1st. Iâd rather have class changes, bug fixes, a new event, and Trading Post files early than put off fixes till the 1st. And I donât get the homies who want the Post open now so they have only a week for the Tender rather than a month for the first go.
1 Like
I think class balance leaves much to be desired. The lack of it has really bummed me out. I hardly log in anymore.
So anyone thatâs hired in the video game industry post Blizzard S.A scandal knows that if a game isnât well received, you fire the dev team and fix the mistakes? I guess youâre also on board with the latest news of intentionally giving bad reviews as a quota to create a bell curve of performance and âinspireâ those to âdo betterâ as well? You responded to someone criticizing the view of firing devs simply because people donât like what they created because they âknew what they were signing up forâ. If you even get hired at a basic fast food and someone complains about their burger, you donât get fired⌠the problem is fixed. If you were the problem, you get retrained. If the problem persists, then termination is an avenue.
If youâre referring to PC performance, thatâs not entirely on Blizzard. Many times itâs due to users not understanding how to operate their PC, update drivers, clean out the crap, do basic system maintenance⌠hell, opening the machine up and using a can of freaking air⌠if youâre referring to how the expansion and patch âperformsâ pc-wise, you want the devs to come to your door to vacuum your keyboard too?
If youâre referring to bugs within the game, ok, I can respect that view, but the game has been around almost 20 years without the code being fully gone over to unify it. You have callback functions calling to systems that donât exist anymore because thereâs a codefragment thatâs still used in this other system⌠and that can create a bug, or multiple sometimes⌠the easy answer to this is to obviously unify the code right? Will you or anyone else sit around and skip an expansion so that the devs have the time to fully unify the code, or are you jockying that they should have 80+hr work weeks so they can unify the code and continue their normal workload too? The unifying of the last 20 years of code into a clean codeblock is, at minimum, a full expansion process (ie dev time)âŚ
If youâre referring to gameplay aspects, systems, rep, story arcs, etc, these arenât solely on the devs, so firing devs over it instead of addressing the entire issue is as ridiculous as thinking that these complaints are new in any fashion. There have been constant dribble of complaints about âI donât like this, change it, waaaâ since 2004, and post Cataclysm it snowballed. This could be due to the larger player volume around the WotLK-Cata changeover, or it likely has to do with specific systems that catered to a specific playstyle and in turn players started to over-reach, constantly expecting more to be shoveled in that direction.
Iâve been around the game a long time, and to go back to the original post, I -am- actually happy with the new patch and the current gameplay direction, for the first time in probably 6 years at least, possibly longer. Am I experiencing bugs? Yes. Are they frustrating? YES! Am I expecting them to be fixed overnight with zero downtime to apply the patches and expect Blizzard to have redundancy server nodes to operate the game? No. Why? They arenât the only gaming company or live service game that does have downtimes to apply patches, contrary to what some would have you believe. They do have bugs, and so do plenty of other games⌠hell, some devs on single player games donât even try to fix the bugs and put out an announcement that they should be considered âgameplayâ instead. This isnât a single player game. This is a live service massively multiplayer online roleplaying (though that has disappeared mostly) game⌠that means that crap is going to occur that wasnât anticipated because, plainly, most times, the people theyâre inviting to alphas and betas arenât the ones that should be. This isnât a streamer issue. This is more of an âinvite the players who most likely will break the systems or have reported major issues in the pastâ issue, look at players who arenât focused on the main story (per se) and just leveling, and find the ones who actively explore, looking for that one cliffside that was accidentally coded to clip through and suddenly youâre under the world⌠Take the breaking of old world dungeons in this expansion⌠why did nobody bother to test these in the alphas and betas⌠because it wasnât encouraged, and a good portion of those who were invited streamlined the speedrunning to 70 instead. Additionally this isnât âpurelyâ an alpha/beta issue either, but the fact that not every event can be accounted for. Event, not as in primal storms and such, but event such as, what happens when a mage uses invisibility while benefiting from the rogue party cloak (which Iâm forgetting the name of at the moment), while in this one quest area that requires using this other ability that stealths the player, but the scripted AI can see through the ability stealth for the quest or event⌠does it break the event? Does the mob just get stuck and evading til a GM goes about to fix it, or does it reset the event⌠If you think this is a crazy example of how the code interacts with abilities, look at any number of people who report major gamebreaking bugs that allow players to, inadvertently or intentionally, stack damage to unfathomable levels to one shot bosses/mobs/players/etc that they shouldnât be able to. On top of that, most players donât even report bugs, they just shrug it off and leave it for someone else to report, and Iâm not even talking about during betas here. If something seems off, put in a ticket, donât just complain on the GD forums about -thing- is broken.
To go full circle to your reply, stop paying their paycheck means -you-. The -you- that have a problem with the current game and the direction that itâs going⌠stop paying. I agree that people should be given the opportunity to fix their mistakes, but Iâm not the one calling for people to be fired over a few bugs and someone complaining about having nothing to do when theyâre just refusing to participate in the game around them. Blizzard, and the game, are in better places now than they were as little as 2 years ago⌠so why not give them the opportunity to continue to fix that which has been broken, internally and in the game⌠but if the complaint is, âWhatâs wrong is that things are different from bfa and shadowlandsâ, then the problem might not lie within the dev team or any other facet of the company.
You can rephrase what I said all day to fit your argument, it doesnât change what I said.
Hey more strawman arguments and ways to try to show you are âRightâ even if youâre completely wrong.
If anything that example is exactly why you wouldnât work for Blizzard and why anyone going into Blizzard would know better. The environment is toxic, the community can be toxic as well. But yes, if you donât perform your job you are liable to being fired. No person is immune because of some notion of human dignity/empathy or whatever. Economics isnât about how someone feels, other than the endless wants of consumers. Meeting those needs will in the end lead to prosperity. If you have enough people upset over service, yes they will get fired. No amount of unionism or otherwise is going to help them. I mean hell, the devs are literally sabotaging other devs just so they can look better. You want to talk about a toxic work place and why they would want to retain a job at such a place, yeah I canât imagine.
Iâm not sure how you got PC Performance out of Game performance generally and issues across the board every release, and many that go unfixed generally. The basic functionality of the game has ongoing issues that are constantly reported, that does include class balancing, quest functionality, hell even the functionality of the AH. Yes People are upset. No one here said anything about keyboards, but again, these are your words not mine.
Yes, and that is a problem as well. The Issue I addressed was one small fragment of the whole. You wouldnât call one Neuron a brain, right? But a collection of Neurons and other cells make what we call a âbrain,â an organ. Similarly, one problem regarding a toxic work place, toxic employees, and poor performance is generally one issue under the same umbrella that stems off into various other issues like software issues, and other issues such as coding issues that have not been resolved, or âupgraded.â
Iâve worked 75+ hours a week, and my âsundaysâ were maintenance days for the company vehicle unpaid. I digress, this isnât about me. This is about their inability to fix the issue. Could they fix these problems? YES. Is it cost effective? Maybe not. But its sort of like buying a run down used vehicle that is about to be sent to the scrapyard. Why repair something when you can just keep buying cheaper ones that serve the same purpose? In a sense, that is what Blizzard is doing. You can repaint it, and keep all the crap inside it, and nothing changes much, just the superficial crap. People eat it up. Whether its appealing to certain demographics in society, or upgrading the graphics every five to eight years or so. Its the same run down vehicle, that gets the job done and does bare minimum. People hate it, but they like it better than walking. So is it good? no.
Yes, the general consensus when you work for an employer is you will do your job, and aim to improve it. No the devs are not solely responsible, but that doesnât change the argument what so ever. It could be a janitor who doesnât keep the building clean and I would say that person should be fired to. But what Iâm referring to is specific to devs. Addressing the entire issue and generalizing is the foolish thing to do, because youâre splitting hairs about who does what, but you canât do that with a game that has different people responsible for different aspects. Yes the game and corporation needs significant change to turn this burning trash heap around.
They really screwed up some of my builds, not too happy with that no.
1 Like
Youâre completely glossing over any aspect of the patch related discussion and simply attacking the points you can pick apart in an attempt to distract the fact that youâre essentially saying fire devs while, when called out on that point, saying they should be allowed to work and fix their mistakes. Choose a lane. Youâre either calling for devs to be fired for reasons up to and including story content that they arenât responsible for, or youâre saying âfix your crap Blizzâ. Nowhere did I argue that problematic individuals shouldnât be fired, nor will I say that someone simply being told what to code should lose their job over a bad review on a forum.
Please see remarks about the curve, intentional bad performance reviews and the recent reports surrounding said behavior.
Where did I say that people should -want- to retain a job in a toxic environment? Was Blizzard a toxic environment? Yes. Are they? Remains to be seen. Nothing, especially in the corporate world, happens overnight, and until thereâs some shuffling on the higher-ups, I wonât say I believe that the environment is âdramatically differentâ, but this returns to your own argument of giving people a chance to fix the problems.
Now, letâs return to the post, and cease the bickering simply because there are fragments that can be picked apart in an attempt to remold the narrative while blaming one portion of the work force for crap they likely have no control in. Alternatively you can start a GD post about how devs need to be fired because the higher ups are toxic
You donât think that managers being ordered to give bad reviews/marks to some devs is a bad thing? So what happened to your entire argument of âno one deserves to lose their job.â Youâre flip flopping here.
Same here. As guardian Druid and mm main, Iâm not happy.
1 Like
Final response to your incessant need to simply pick and choose portions out of context to validate your own personal need to win at something.
Where did I say that managers being ordered to give bad reviews isnât a bad thing? Where did I imply that? I directly stated that the issue lies further up the food chain.
Iâm not flip flopping one bit. The patch is good as a whole, there are problems with the expansion which I feel can and will be resolved if given time. You responded to someone defending the firing of devs, and I responded to that. You began by arguing in favor of firing devs over the situation when, as youâre currently now flipflopping to argue that itâs related to the managers. I brought up the bad reviews, now youâre spinning it in an attempt to sound like itâs your idea. I said that the devs, which you were posturing to fire over a few bugs do not deserve to lose their jobs over a few bugs. I stated that the codemonkeys have little to no say over what goes on. I pointed out that if the issue was related to story content or progression arcs or similar, the devs have no control over this, and yet at every turn youâve decided to pick and choose your way through the post to identify key portions that you can twist out of context in favor of your own narrative.
TLDR for your own clarity: The devs are not directly responsible, the management and those higher up are at fault. The commands came from somewhere, so start at the top and investigate down, not vice versa. Am I saying Kottick controls what happens per patch? No, but from Kottick down the chain there lies the issue where, for example, the bad review system began. It could have started with Kottick⌠it might have started purely with the managers 1 step above the bottom tier devs. Find the problem and remove -it-, just like a bad chef before the kitchen suffers. A bad chef tells the line chef what to do, a dish is bad because the chef is bad, a line chef is generally just doing what theyâre told to do.
Youâve been doing this the whole time while giving me your life story and quoting points I said out of context, or never said at all. so donât feel bad, but this argument ended three posts ago.
They cant fire people bc no one wants to work there already
I went to org to find the new trading post, forgot why I went to org, spent 10 minutes flying around trying to remember, finally remembered, just to find out its not live until the 1st 
Sometimes i am dumb
As long as im.having fun in the game âŚit makes no impact on meâŚ
when you entered the game, you had to close a MASSIVE WINDOW which told you when it was comingâŚ
