On first use, the Garrison Hearthstone was turned into a toy, but it does not work. Trying to use the toy results in a “You can’t do that right now” no matter where I’m standing. The Admiral’s Compass still works, but a 4 hour cooldown is ridiculous. Also, the Dalaran Hearthstone as a toy appears to work fine.
Please fix this; I use my Garrison very often and not being able to hearth to it is a problem.
I have it on my action bar
1st use gave me an achieve and mech mount. Then it grey’d out.
Tried it a 2nd time and it worked as usual for me
Remove it from your action bar.
Then put the Toy on your action bar.
Not a chance!
It had never been i my action bars; I was accessing it through an addon called Tome of Teleportation. However, I put the toy into my action bar, and it still does not work. Same “You can’t do that right now” error.
Bum deal, make sure to post in bug forum plz!
Theres a lot of bugs tonight. Had issues with so mych
Welcome to patch day.
Bug report(s) submitted before I posted here. Hopefully, unlike with the broken pedestals, this Draenor-era bug WILL get repaired.
Ive enjoyed what ive done of the patch but so far ive encountered more bugs than I ever had before. I has my health bar displaying improperly, the gates in the dungeon didnt work for half my party who had to kill thenselves to make it work, getting DC’d in solo shuffle among other things.
I reported that a while back on the ptr why am i surprised it wasnt fixed
Mine is working just fine, I even just retested.
(right now today, yes I realize i posted here 2 days ago as well)
removed from my tool bar and used directly from collections
added to tool bar and used as well.
maybe it’s an addon causing you issues?
You know what’s weird? I got this error a few times since the new patch dropped but not while trying to hearth… it happened randomly while I was dragonflying around a few times. Thought it was pretty strange.
As stated in my bug reports, I have noted the following:
So, it can’t be any of the addons I use; the evoker’s works with all addons enabled, and even with all addons disabled it continues to only produce the “You can’t do that right now” error on every other character.
All my other characters are many years old unlike the evoker… could that have something to do with it?
i just tried the Legio nand Garrison hearthstones i made on a toon only a coupoe months old and he had no issues
Like you, I use the Garrison all the time.
It’s been working fine for me, since the patch, on multiple characters.
Just to check again, I opened up Collections, dragged the “Garrison Hearthstone” Toy over again to my right action bar, and used it just now.
I’ve not had an issue at all with this.
On many characters, I use a different version of the Hearthstone, like Fire Eater’s Hearthstone (now a Toy as well), and it is also working just fine.
The regular Hearthstone (still an object in inventory) also works fine for me.
It sounds like you’re pretty sure, but sometimes, it IS addons which cause strange behavior, and you are using an addon managing hearthstones, etc., which was last updated on Jun 29, 2023, so I’m guessing it is either that or another addon causing this problem for you.
I have tried on multiple characters with all addons disabled, and except for the evoker, the issue persists. (The evoker’s Garrison HS works with all addons enabled as well, so I believe addons have nothing to do with this issue.) Most of my other characters are over a decade old, with a few being a couple years old.
All other hearthstones work, including the newly toy-ized Dalaran one and what variant toys I have for the basic HS. It is only this one since becoming a toy, and the exact same error persists across all characters save the one evoker I made not long ago.
OK, it is within the realm of possibility that you are correct.
However, you are also noticing a problem with a “hearthstone” related item (the Garrison Hearthstone), while disclosing that you have an addon which changes the functionality of the way “hearthstones” work.
I pointed out that your addon was updated BEFORE the most recent patch.
Logically, a person would assume that your issue is related to that, or possibly another, addon.
Here’s how to eliminate completely this or any addon as being the cause:
Install WoW on another PC which has never had WoW before, fresh, update WoW completely, install NO addons.
If you are able to do that, I’m guessing your “Hearthstones” will behave correctly.
Hey OP:
What I’ve found over the years is, you basically never hear a WoW forum poster come back and say ~“I may have been wrong here”.
So, let me say this… “I may have been wrong here”.
I made a Tauren Warlock the other day (because of course!), which brings my total characters up to I think 47 or 48. HIS Garrison Hearthstone (toy) works great.
Just to check and see… I then used my Garrison Hearthstone on every single one of my guys, and I found ONE guy having the same issue as you.
(it is my first and oldest Warlock, who would have been created in late 2005 to early 2006.)
Every OTHER guy, except that Warlock’s Garrison Hearthstone, works perfectly. So, on ONE of my guys it IS happening, and on the other (let’s say) 46 it is NOT happening, and they are all OK.
On THAT Warlock, he gets the same error message as you when trying to use his Garrison Hearthstone (toy)… “You can’t do that right now.”
So… is it your Add-on? I dunno.
Is it another/other Add-on? I dunno. I use a total of 6, and I’ve got 3 which were apparently not updated… Master Plan, Rematch, and Venture Plan.
MasterPlan → UPDATED → issue persists
Rematch → UPDATED → issue persists
VenturePlan → UPDATED → issue persists
I could completely remove Venture Plan, but I actually did do some Shadowlands stuff on a guy last week.
Is it the latest patch? Maybe? Probably? I dunno.
Is it some weird coincidental thing related to a Warlock? I dunno. I’ve got 4 x Warlocks, so I doubt it. It’s not spec, or Talents, or summoned pet status.
Is it some weird coincidental thing related to a specific character? I dunno. The possibilities there are nearly infinite.
If I have to guess it may be something related to Draenor progression in some way. No way (for me) to figure this out, though, as every one of my guys has “done Draenor”, some much more than others, and THIS Warlock would have completed a great deal of Draenor stuff, compared to many of my other guys.
But… it’s happening to ONE of my (47 total) guys too.
So, good luck, and I hope it gets corrected for you soon.
This is not a huge deal for me, but if instead of just ONE guy, it was happening on the other 46, I would be very very irritated, for sure.
UPDATE: the issue is not resolved (nor has it changed), but I did get some… interesting… feedback from a Blizzard GM. And it makes no sense.
According to one going by Uridetz, it appears my garrison starter quests were never started or completed, and that would be why the Garrison HS does not function. So, basically, my fully upgraded and up-until-patch-10.1.5 functioning garrison does not exist according to their end. That’s… troubling.
Some time ago (in years), one of the starter quests called 'What We Got" re-appeared over the NPC Gazlowe’s head inside the main building. In the interest of not breaking anything I opted to ignore doing it again, and up until this last patch, everything seemed fine. After hearing what I did from Uridetz, I re-acquired the quest and attempted to do it, but 2 of the 3 steps can’t be completed: I can talk to Skaggit to “release the peons”, but even tho he wanders away with some dialog, the objective stays undone at “0/1”. The other objective, to speak to Senior Peon II, is impossible because he stands within the main building (next to where Skaggit is) with no dialog options at all - I can select / target him, but nothing else. So I’m stuck on that front, too.
Seems like Blizzard should be able to mark all these quests as “done” since I can prove quite easily that my garrison very much exists. I just hope that both a resolution comes soon, and that I don’t lose anything (like the AH I went thru unlocking), but I have yet to hear back from Uridetz or anyone else after explaining all this.
N.B. - Apologies to anyone noticing this reply being crossposted form the bug report forum, but I didn’t feel like reinventing the wheel.