I purchased the 12 month subscription bundle last month and received both the Ginormous Grrloc and Gleaming Moonbeast. After today’s maintenance, the Gleaming Moonbeast is no longer anywhere to be seen. How did this happen?
Same for me!
I’ve been using for a week or so, had it on my bars, and now its just gone.
1 Like
Same! Had it on the bars and I looked through my mount journal…just poof gone.
1 Like
At least it wasn’t just me. I have submitted a ticket about this problem. Hopefully the issue is addressed before they respond to my ticket though.
1 Like
Mine is also missing, and no longer visible in collections at all. Seems it’s completely gone. 
1 Like
Mine and my Fiances are both gone,hoping for a hotfix to resupply everyone with them, or atleast a dev to reply with any update
1 Like
It now shows in my collections, but says I haven’t collected it.
I was using it most recently on my Dracthyr, so the icon was on my bars. It wasn’t there when I logged into her a few minutes ago, but it sort of just…reappeared just now out of the blue. Still says I don’t have it though.
I just put in a ticket for it before I crossed into the Emerald Dream. Once I was inside, mount came back on my bars and in the journal. I haven’t stepped back out to try to see if it disappears once I go back.
Mine just re-appeared both in collections, and on my bars. Quick fix it seems. 
Huh. I’ll give that shot after this Sha of Anger mount attempt.
Maybe I just need to relog. That is good news if it is indeed fixed for everyone.
I’m in Badlands just doing low level questing and it disappeared and re-appeared for me. I’m not sure if location matters too much. I hope yours comes back.
I got mine as a gift and logged in once Maintenance was done and did a full manual check then a Name check once I rememebered its name and nothing. I still have the Gurlock Mount not this one. Bug or something I assume
It might also need some time to roll out across all the affected accounts, so I will see what happens.
Edit: Yeah, I logged out of one character and onto another. It appears to be fixed now.
We’ve just applied a hotfix that should resolve this.
Thank you.
1 Like