Because it is. Ill break it down for you even more though.
Disclaimer: im all for the QoL the macro brings and i hope they find a way to properly fix it. Now given that:
If people use the macro, they should first be able to play their class / spec / talent / etc etc, on a fundamental level without the use of said macros without killing themselves every 5 minutes and blaming the game.
I.E. use the cvat macro. But in the case it breaks, you should still be able to do what you were doing before it broke without dropping form for whatever reasons…
I know in the heat of battle things happen. Using Shift and Alt as modifiers for my macros, i can only imagine how many times i finger over that capslock button. Same could be said for others and Regrowth depending on where/how its mapped.
But you should be able to play with Regrowth without constantly dropping forms. The macro becomes a QoL when it saves you from.that 1% situation we discussed earlier.
If the macro is needed to keep you from dropping form 33% of the time…then its a skill issue .and a definite crutch and i would advocate for learning to play without said macro first as it will lead to a higher skill floor.
And for the people in the back: i hope they fix this issue as i personally dont have an issue with the macro working or not
Quite a lot actually. Shifting to travel form from bear form. Using my dragon riding mount from bear form. Throwing a group heal from cat form. Etc, Etc. You give all of these features up, making them 2 step operations, if you leave autounshift disabled.
It’s far more convenient to just to encapsulate the autounshifting to just a single actionbutton, as the other 90% of the time auto unshifting IS the desired behavior. The only time I actually want to disable auto unshifting is 1) on Regrowth, 2) only in combat, 3) only in bear form. For everything else, I prefer having autounshift on.
you can fix all of those by having a macro starting with /cancelform. Basically you need to reverse your thinking. You can no longer automate regrowthing with dream of denarius, so reverse autoUnshift and automate everything else.
Sure. Kind of. But it was far easier before to just have a single macro that handled this for the 1 ability that this applied to, instead of now needing many, many macros to try to replicate a similar behavior across many of our abilities.
Also, /cancelform isn’t a direct replacement, i.e. travel form. Right now if you aren’t in travel form it will put you in travel form, and if you’re in travel form it will take you out of it. If I use a /cancelform macro then my travel form button will always break the ladder condition and it will keep me in travel form. So now I’d need a more complex macro to handle the shift into and out of conditions…
Thanks for trying to provide solutions, but some of us are still hoping that Blizzard will provide a workaround as a direct replacement to this broken functionality. I know there are weakauras and macro sets that can help resolve this.
Yeah I just created the macro to test it out, and it does work. My bad, thanks. I’m still salty about needing a bunch of custom macros for basic abilities, but if I need to do it I guess I need to do it.
Yeah, I understand that its more of a pain to set up, but the overall functionality isn’t lost. I just don’t see them undoing this, as again, macros shouldn’t be making these types of decisions for the player.
Fair enough. It’s just a bummer that this worked for as long as I can remember (at least 10 years) just to have it silently removed on a random Friday without notice. I only found out about this change when I started throwing lua errors inside a key, and the error message was entirely unhelpful. I had to spend 15 minutes googling just to figure out what happened, which is was brought me to this PSA thread. So this thread served its purpose perfectly, thanks OP.
Regardless of their being workarounds, annoying or not, this is the type of change that would have been nice to telegraph earlier on so we could adapt to it proactively. It also hasn’t helped that the response from some folks on these forums has been less-than-empathetic. Instead of it being “oh that sucks, I feel you” it’s instead been “needing the macro in the first place means you’re bad. Learn to play better”. And, to be clear, none of us ‘needed’ the macro, it was just a way to protect ourselves from that rogue misclick or mistiming of hitting the ability. This really wouldn’t be an issue at all if the penalty of hitting Regrowth for a tank outside of DoC wasn’t sudden death for you and your party (and bricking your key, etc etc).
It also doesn’t help that it seems like the Blizzard Druid class designers don’t seem care about the DoC/unshifting issue, given that the need for this macro in the first place was just a hack to work around a game issue. An actual, proper, acknowledgment and fix for situations like this would be ideal, rather than a single CVar that had been co-opted into a hacky solution to keep bear tanks from wiping their parties. Other classes have had fixes put in place to address areas that can insta-kill you, such as Monk’s Skyreach/Skytouch choice node. I think Druids just wish they could have something similar here for the case of DoC/Regrowth.
I recommend putting in a report on the bug forum for these kinda things, while the script change overall might have been intentional its possible that breaking the safety net for bear form was an unintentional biproduct, if enough people report it as an issue they might revert the change or create a new work around for it.
It is one of those problems that only affects druids so they might have just overlooked that when tightening permissions. Or they could just make regrowth always castable in bear form since its the only tank that risks dropping all its defensives by accidently hitting a single spell.
I saw someone in the WoWhead article about this change say something like “this would be like if prot paladins casting WoG without a proc would make them naked”
100% sums it up.
If this was intentional to generate “friction” then it just sounds like they want us to stop using DoC altogether.
I thought about this for a bit, and they could just alter guardian’s ursine adept passive to allow regrowth while in bear form, but with a 100% penalty to its cast time or something like that. Would make it so accidentally using it wouldn’t unshift you, but also impractical enough so as not to encourage you to be using it in bear form.
You already loose the ability to dodge while casting like every other tank that can spam a heal so i dont think it really needs a penalty that harsh, 3 seconds no dodge is pretty bad for a tank, especially with how low regrowths healing modifer is for everyone but restoration.
Prot pally doesn’t loose much more for casting flash heal and has a second resource like us that makes up the bulk of their actual tanking kit with holy power, if it really needs a balance can just bump up the mana cost so you can only spam like 5 before without free procs, like pre mana rework.
Paladin loses the ability to dodge, block, and parry, so they lose far more than druids would with this suggested change. The idea around such a penalty is to actually force a decision between staying in bear for the extra armor/stamina, or leaving bear for the faster casts. If you’re actively tanking, you shouldn’t be hard casting either a regrowth or a flash of light. WoG is closer to frenzied regeneration; more in line with active mitigation.
But it isn’t an issue. You’re supposed to drop form to be able to cast Regrowth without a DoC proc. Otherwise with said macro, you cannot use Regrowth outside of procs.
That’s the way it’s designed. Like Predatory Swiftness as well. Casting these spells outside of the niche conditions are meant to pull you out.
Not even close. It would be akin to Paladins not being able to block or dodge or or parry while hard casting. Which if you’re not familiar…they can’t.
I think it would be better if they allowed “aspect” abilities to be cast in form - wouldn’t help Regrowth issue, but then we could at least make use of Rejuv + Swiftmend when we’re required to use Resto tree to get to Remove Corruption.
Well yah it wouldnt be good enough to spam even if we could just because of how much it heals outside of DoC procs,. But if the goal is make it so accidently fat fingering regrowth doesnt instantly mean death via unshapeshift, forcing 3 seconds of no dodge through a cast time isnt a good solution is my point.
They can make it super expensive so you pretty much only use it after pull or some rough kiting moments, but since melee abilites dont auto cancel spell casts if i fat finger a regrowth and dont instantly notice to cancel or am already moving ive stopped dodging and any other action for 3 seconds with your suggestion. I accidently hit regrowth, i dont notice so i hit mangle and ironfur expecting things to happen, but they dont cause im still casting regrowth.
Just make it hella expensive so you only get like 5 casts off and let it be cast in bear form. No other complicated shenanigans.
idk how any bear would fat finger regrowth and not notice it for 3 seconds. Regardless, my suggestion is with the intent of keeping functionality as close as possible to how it is now, only changing druids shifting out of bear and getting domed. I don’t think druids actually need the ability to cast regrowth in bear form except to halt that 1 occurrence.