I forgot diversity is bad, certain classes should only be able to play 1 spec. There is never a good reason for why having multiple specs viable is a bad thing other then "because x has always been the PvP spec"
That's just how shit works around here mate. Arms or bust. Prot is also acceptable for those moments where you feel like being a faggot though
"Are you jealous of me getting a chance to play something that's incredibly unfinished, buggy and not even close to what it'll look like when released, and even the release version will suck because this game sucks"
there isnt a single person i speak to who doesnt think that ure complete garbage sai :x also, ive known about u for longer than most people (i was on frenzy for a loooong time).
Damn that hurt, who are you again? Your pathetic tries to talk to me remind me of a story that happened to me a while ago. My Grandfather smoked his whole life. I was about 10 years old when my mother said to him, 'If you ever want to see your grandchildren graduate, you have to stop immediately.'. Tears welled up in his eyes when he realized what exactly was at stake. He gave it up immediately. Three years later he died of lung cancer. It was really sad and destroyed me. My mother said to me- 'Don't ever smoke. Please don't put your family through what your Grandfather put us through." I agreed. At 28, I have never touched a cigarette. I must say,
I feel a very slight sense of regret for never having done it, because your post gave me cancer anyway.
If you've ever worked at a big IT/gaming company (circa 2,000 employees), either as a programmer, developer or data analyst, you would know that it's not simply a case of "X needs Y". There are extremely long, complex processes behind everything and every suggestion before it can even be considered being implemented into the game. That's not to mention the approval process.
Blizzard Entertainment do not have single developers for single classes, they have an entire team for all the classes. From which, they have to balance all classes, in all situations, for all specs, whilst keeping it easy to understand for the end user. That's far from an easy task. Changing Frostbolt to do 200% damage in PvP but 100% damage in PvE isn't as simple as changing a bit of code and adding some information to a tooltip - They have to consider:
- How are we going to tell users about this change
- How easy is it for a user to understand the change
- Is the tool-tip going to be bloated
- Does this open the doors for further changes to also be done
- When can we get the translations done by for all supported languages
- Does it require a client build? If so, is it a high enough priority to warrant a client side patch
Even once you've done all that, you need to implement the change on an internal build, do internal QA and tick off every box you've ever known to ensure that no other bugs are introduced with this minor fix. In development, it's not uncommon that changing one minor things, can affect something major elsewhere. There was a post from Blizzard in 2009 about a hot-fix they implemented for class balance, which ended up breaking Onyxia. Completely unrelated, completely separate part of the game, but such is the way of code, especially with a game which now stretches over 50,000,000 lines of code.
Just because it comes out that X has been broken for Y months, doesn't mean anybody knew about it. Even if somewhere, at some point, a user reported the problem, it first of all needs to make it to the ears of the developer through the QA process for it to be delt with. If QA took a look at the issue and decided that there was not a problem, it would never have even made it to the developers. Your bug reports do not go straight to Holinka's inbox, they go to a general repository to then be broken apart, verified and assigned as tasks from team leaders, when/as required.
Put simply, sometimes at work I spend an entire week doing particular tasks, but if you asked me to quantify my results for the week in terms of something visual, I probably wouldn't be able to. It doesn't mean that you've spent 40-60 hours a week doing nothing, it means that you've been working on tasks, investigating, meeting, or even just doing code behind the scenes for future applications. Don't forget that all of these changes that are in the WoD alpha notes, for the most part, are class balance changes. They weren't dreamt up over night, they will have been months of number crunching, decision making and organization to attempt rebalanced across the board.
Take from this what you will, but this is coming from hands on experience in the gaming industry and this field.
holy is strong because they never have to cast a single heal
you feather invis sprint and fear their team
you never die
best comp is prob holy/blood DK
you also never die
Dear Misinformed Monkey,
Holy was previously out of control largely because PoM was not being affected by Battle Fatigue, thus you would see nearly 100k PoM crits that would heal for extremely large amounts during AoE and spread pressure. Now that this has been fixed, Holy Priests, do in-fact, need to cast when there is a large amount of pressure. In addition to Holy Priests needing to cast, their mana regen is relatively garbage compared to other healers, leaving them in a sticky situation after casting just a handful of casted heals.
I do agree that Chastise/Feathers/Guise should be looked into it. It is a pretty large advantage to have for a team. I don't have the exact solution that would appease the masses, however, I feel like Spectral Guise should not be affected by (or maybe limited) movement speed increases, such as feathers. I also feel as if feathers should not be 80%.
In regards to never dying; I suppose if you are a brain dead mongoloid, which unfortunately I can assume from your post, then a holy priest may seem difficult to kill. However, if you took just a moment to look at the arsenal that a holy priest has available, you might see a nice way to counter them. (Hint: Look at their defensive cooldown timers)
P.S; you're a warlock - go spread some unhealable AIDs damage as Affliction.
i hate retards like this that destroy every semblance of balance based discussion with garbage class bias
what part of the nerf on sprint while in spectral guise did you miss ? Class balance XD ? wtf are you even on about... this game was never and will never be anywhere near balance. Deal with it just like how i dealed with being useless in s9 (first 3-4 months) and 12. Probably you need to get out of grandma's basement and get some fresh air son
Elorxo, on 20 September 2013 - 11:56 AM, said:
lol. reason ? cause i think feathers are not ruining the game but the problem is the interaction with spectral guise ? Gz on duellist btw.