Never in the history of wow have paladins had to run around with a /stopattack macro and use it after every swing just to have the ability to switch targets and not lose all stacks obtained.
We should be able to switch targets as we please REGARDLESS of if auto attack is turned on or not. This implementation is somehow binding the stacks to the target if auto attack is on and that is wrong.
The only way to lose stacks should be actually using them on a target. You cannot spout off #nochanges then allow people to level paladins expecting that to be the case then completely ruin/break them while fixing a trinket that isn’t even paladin specific that was abused by many classes.
People spent months testing beta and leveling their characters expecting reckoning to function as it did in beta since #nochanges was supposedly the plan. Yet this blatant bait and switch occured and royally screwed paladin players over.
You guys effectively ruined the launch of BGs for any paladin spec’d reckoning and enough is enough. Put it back to how it was, the only way to lose charges is to actually use them and while you’re at it fix the glitched orc racial that is still working on grenades.
You have always had to stop auto attacking with reckoning while switching targets.
It was this way in vanilla, Please stop complaining about things that work how it was back in the day.
I played Reck till 2.0 when it got nerfed out of the game, I play it now. Yes it is frustrating when stacks drop when you don’t believe they should, but it did the same back in vanilla.
You are wrong but lets say even if you were right. It is still a bait and switch. You can’t have it one way during months of beta and then months of lvling/playing WHILE paying a monthly fee then turn around and screw with it while adjusting a trinket.
People put tons of time into their character lvling/gearing and hell some people even made a sulfurious which was a tremendous effort and what did they get as a reward? A bait and switch that effectively ruined the first few weeks of BGs and now still provides a garbage experience compared to how it was all beta and launch.
How is making it work like it was in 1.12 a bait and switch? It was working incorrectly for the beta and far too many people just were happy being OP and exploiting it. The idea of classic was always provide the 1.12 experience, its close but its not perfect. Sure they are changing things now (av queues) but the gameplay is “in theory” the same(gotta use air quotes cause theres still issues.
Get passed it, Reckoning is working closer to it was in 1.12 then it was before minus a few issues with batching. It was always buggy, you always had the rare chance to just drop charges and have no idea why, But controlling your auto attack and your range was always the biggest part of vanilla reck.
This /sit macro, pre-charging meta that is the private servers is not the 1.12 that was vanilla and im glad its not in game now.
It doesn’t work correctly still. It did before the …FIX… I know in AV or any area where I am getting crit by multiple horde and in range of my target and I do not receive reckoning charges to this day. Sometimes you get some but most the time you don’t and I’m not sure why. I can get crit by 2 fury warriors in rapid succession but not get any extra attacks.
So it’s definitely not working as intended and definitely not working as described in the tooltip.
“Gives the paladin a 100% chance to gain an extra attack after being the victim of a critical strike”
Should be updated to:
“Gives a 100% chance to sometimes gain an extra after being the victim of a critical strike unless you change/move targets and stop auto attacks.”
So I should see a number of white hits equal to number of times I was crit. It doesn’t matter from what source.
Honestly, my opinion and I know it matters to no one and will make no difference but it should be reverted to what it was and with Hand Of Justice bug fixed you shouldn’t get those extra stored swings in.
While it’s a little clunkier than I remembered, I have been very successful at using it at its current state. Assuming that we can’t expect it to be reverted back any time soon, or at all, I’ve written up details on what I’ve found, and it’s still been fun to play.
No, what you mean to say is it worked like you wanted it to prior to the fix to its 1.12 version. We have tons of sources from 2006 including Bacon’s guide saying this is how it was and the reference client even proves it. You guys seriously need to stop spamming these threads.
No where in the tooltip does it say you cannot switch targets. No other talents function like this where its effect is wasted by simply playing the game.
You can spout off it was X way in 2006 or w/e but it does not change the fact that they implemented reckoning the way it was and baited people into thinking it wasn’t going to be trash.
What makes it a bait and switch is the fact it was not listed as a bug in the known bugs list. No where did it mention “Reckoning is not correctly losing stacks while switching targets and blah blah” There was no indication it would change and quite frankly its nonsense to change it multiple months into the game when people already chose paladin as their main character and geared it based around what the beta/bug list reflected.
The bottom line is, the changes to reckoning were accidental when they screwed with HoJ free procs by abusing /start /stop macros. They did not go into it with the intent of changing it. After they broke it they started lying citing how it supposedly worked in vanilla even though people proved otherwise. Instead of doing the right thing and restoring it they made a few little changes to shut most people up and said good enough.
Except there are numerous threads even documenting this being how it was in vanilla, months in advance of classic. Also you know all the guides from patch 1.9-1.12 also agree with the sentiment. Just because you don’t like the changes because it isn’t private server reckoning sounds like you just refuse to acknowledge the truth.
Was it listed as a bug or was there any indication it would change from beta? Of course not. If it’s not listed as a bug and its stayed that way for months why should we expect changes? #nochanges was blasted all over constantly. Many things on here aren’t accurate to vanilla. Why is this rule only applied when its to screw over something and never applied for a buff?
They screwed it up by accident when messing with HoJ and don’t feel like fixing it since clowns give them a pass saying ohh its ok. I would bet money the people saying this don’t even have a paladin main and if they do its in green gear. Anyone that actually put effort into leveling their paladin and gearing it properly is/should be quite pissed over this nonsense.
What i am saying is peoples time should be respected. This is a 15 year old game, they implemented reckoning in a fashion that does exactly what the tooltip says. No where in the tooltip does it say it has to be used on your current target or that the stacks are bound to a target. The tooltip is:
Gives you a 100% chance to gain an extra attack after being the victim of a critical strike.
Where does it magically say its supposed to disapear if you switch targets or have auto attack on?
Implementing bugs from the past by accident that they probably didnt have the technical ability to even fix back then(while fixing a trinket) then saying hey its fine you just wasted months of time lvling/gearing the character we just broke is not ok.
No, it isn’t. I can get crit like 5 times in a row by two fury warriors and not get any extra swings. When in fact I should be getting 5 extra swings on whatever target I have ( in which case they were in range )
Not just dropping but also not any extra attacks if you have auto attack on which should happen. It sometimes works in 1 vs 1 but not reliable and def not working in 2 vs 1 or more situations
fun fact I’m not even Reck spec atm - but many of the players in the Paladin TC discord are and are continuing to lose stacks or not properly gaining stacks while auto attack is OFF
this is being reproduced against 2v1 or multiple v 1 scenarios as Crimsan stated earlier - batching seems to mess up the reck counter and causes it to get stuck if multiple crits land all at the same time within the same batch window
