When they first data mined the legendary ring proc I read it and immediately wanted to make a post about it but I held my tongue. I knew it had to be some horrible joke, or at least I hoped so. As it turns out I was both right and wrong. It was not a joke which made me wrong, but they did not intend to released what was data mined, which I was right about. I knew, hoped really, that it would never get released like that.
Just for the fun of it, I want to complain about that removed proc before I complain about the proc it was changed into. I enjoy picking on blizzards horrible ideas sometimes.
For those that do not know what the legendary proc was supposed to be based on the original data mined information I will gladly regale you and we can laugh how bad of an idea it was together.
The proc would no longer be "your" proc. It would become a raid wide proc that added up all people in the raid with the same type of ring and then randomly gave one of those people the proc, but a much bigger version of it. For example, if you had 6 agility users in your raid with the agility ring that would mean someone would get a 60% increase to all damage they, and they alone, do for 12 seconds. 6 users of the agility ring at 10% each is how it worked out.
Every 12 seconds it would switch to another person wearing that same type of ring randomly. So someone in the raid would always have a 60% boost to their damage done at all times for a length of 12 seconds.
In theory that is pretty awesome really. Instead of a proc every minute or two it would be constantly there, so to speak, but who had it would be completely random. For a guild group with all solid players in it, this would actually be pretty damn awesome if you ask me.
Now, I will ask you the question, what exact about that did I dislike? Dislike enough to call it a horrible idea.
Main part that made this idea dreadful was the random element to it. I hate anything random and would hate this even more. I am sick and tired and fed up with random. I do not want more random in the game.
Lets say with my luck, and we all know it is poor at best most of the time, I would never end up with the buff as it bounced around the other 5 agility users in my raid and left me with nothing. No, hell no, no thank you, go screw yourself with a hot poker blizzard. Stop adding more random crap into the game.
The add to that the fact that the ring would be mandatory, not like that is a big deal, it is not hard to get, but for someone that comes back to the game in 6 months maybe catching up will not be instant, and it will not be instant I am sure of that. So lets say you come back to the game 6 months from now and you want to get into a pug. Sorry, you do not have the ring so we can not invite you.
At least with the legendary cape the only person that was hurt by you not having it if you were late to the game getting it was you yourself. Now, with a ring proc that benefits the entire raid, you not having the legendary ring hurts the entire raid, not just yourself. No blizzard, bad blizzard, do I have to hit you on the nose with a rolled up newspaper. You can not add stuff like that into the game.
Then there is the whole idea that it is "my" ring. I want something from it. I want a benefit of having it. Sure I could very well get it randomly while in a group, but outside of that it is just another ring, nothing special about it. If I get a legendary ring I want the "legendary" feeling all the time for myself. I do not mind that if I have it it helps others, that is cool, but I should still always have some sort of proc for myself and not have to wait for luck to get it. It is my ring after all, shouldn't I be guaranteed to benefit from it.
So, needless to say, when they announced that was not going to be the proc on the legendary ring I was very happy. But I was still a little concerned. Concerned because how the hell did someone actually come up with an insane idea that like and worse yet, how the hell did a horrible idea like that get so far that it actually made it into the game before they decided that was not the way they wanted to go.
It is really concerning because it shows that no one at blizzard has any clue what they are doing. I am sure during the idea phase, the development phase, the coding phase, the implementation phase, there has to be more than a hand full of people it passed through and none of them even considered some of the issues a proc like that would raise? That is why it worry's me. No one at blizzard is looking out for the players. No one at blizzard is taking into account the full picture and what some people, like myself, might view as an issue with a proc like this. I am sure others had different issues than the few I mentioned too.
I am guessing wiser heads prevailed in the end, thank elune for that, but how did a horrible idea like that get so far into development before someone noticed it was a horrible idea?
So after they said they would not be using that dreadful idea for a legendary proc, I waited to see what the new announced proc would be. Now we know what that one is.
It counts all the rings in the raid and make them work in unison as an on use ability. It works on a blanket number for everyone that does not go up with the more of that type of the same rings you have in a raid, better than random who gets it in my opinion.
I do like the idea for my raid team, I do not like the idea for pugging and feel bad for people that are late to getting it, just coming back to the game, or switched characters and are now playing catch up. I also feel bad for classes that the on use cooldown does not line up well with because they have absolutely zero control over when it is used, and that is the problem I see.
See, this ring, unlike the other that adds all rings together, is a blanket 25% damage increase for all ring users, thank elune no random on this one. But this one has one huge drawback which is as soon as someone in the raid uses the on use function of it, it puts everyone's ring on cooldown because they will all share a cooldown. All players get the benefit, don't get me wrong, but once one person uses it, everyone is using it. Like it or not. I am going to side with not here.
The problem I see with this is that I want to use my on use trinkets when I need the on use. My on use might not be the same as the other people in my raid. Maybe I am waiting a few seconds for all my procs, maybe I am saving it because I know I will only get 3 on uses in the fight and I can time the three uses better for when I am on an important target. Maybe I know I can only get one more use in and I am holding it to use it when stampede is off cooldown for maximum potential out of it.
Bottom line here is that it is "my" ring blizzard, I do not want someone else using it whenever the hell they feel like it. I want to use my cooldowns, including my on use abilities, when I want to use them.
Lets not even talk about the trolls in LFR and pugs that hit time warp as they drop group, or on trash, or whenever they know people will lose the benefit of it just to be jerks. Now they can use the ring and screw up the entire raids 25% bonus.
Once again, no blizzard, bad blizzard, stop letting other people control my character.
My On Use.
I do not want to let someone else dictate when I use it.
What is up with blizzard and these horrible legendary procs? Have they completely run out of ideas?
Just turn the ring into a 2 minute cooldown that is per person and you have a winner of an idea blizzard. Everyone can use it when they want to. No one can troll with it. We all win. That would make a legendary legendary.
Letting Billy Joe hit it on cooldown to pad his numbers like he normally does blowing all cooldowns on useless trash mobs because he thinks it makes him look cool should never have access to my on use abilities and I don't like that you are giving it to him blizzard.
Now get off your butt and fix this once again. It is better than it was with the first data minded information, but it is still not a legendary ring. Not as long as you let Billy Joe decide when it is used.
Bad blizzard, go sit in the corner, you need a time out. Next time maybe you will think before you implement. You stay in time out until you understand that.
Same Same But Different
12 hours ago