I learned epic mount riding skill for 900g at Brill, and chose the purple mount from the quest reward after inspecting them at the stable. However instead of getting the purple epic mount version I got the 60% skin, but the mount speed is still 100%.
The other mounts from the same quest seem to be the Epic version. I understand it’s not high priority issue but it’s silly/annoying to still have to 60% skin while running 100%
Images below
https://i.imgur.com/vvyfVbQ.png
https://i.imgur.com/ZjVttVh.png
5 Likes
Same thing just happened to me wtf. I hope it gets patched and that I get a warhorse instead, this one is real fugly.
Same problem here. Opened a ticket / reported the bug
The quest specifically states:
Inspect the armored undead riding warhorses to choose your epic mountt
Quest objectives:
-
Ochre Skeletal Warhorse
-
Purple Skeletal Warhorse
-
Green Skeletal Warhorse
Actual quest rewards:
-
Ochre Skeletal Warhorse
-
Purple Skeletal Horse
-
Green Skeletal Warhorse
Quest: https://www.wowhead.com/forever/quest=99211/an-epic-ride
The quest specifically tells you to inspect the mount you want before choosing your reward. However, the Purple Skeletal Warhorse you inspect isn’t actually available as a reward. Instead, the quest offers a regular Purple Skeletal Horse, which has the unarmored appearance of a level 40 mount.
I chose the purple option expecting to receive the armored warhorse shown during the quest, only to be extremely disappointed when I received the regular skeletal horse instead.
This seems like an incorrect quest reward rather than an intentional choice, especially since the other two options correctly reward armored warhorses and the quest clearly indicates “inspect the mounts to choose which one you want”.
Could this please be fixed, including for players who have already completed the quest and selected the purple mount?
Same thing happened to me. Picked up the Purple Skeletal Horse which looks like a regular 60% mount. I can’t ride this thing blizz fix plox
1 Like
Got the same issue with the UD mount
Hit the same issue, this bug needs more attention.