Wain wrote:The Ghastly Charger should show on the Armory. Mine does:
http://us.battle.net/wow/en/character/a ... lter=ghast
Maybe it's specific realms that are slow to update :/
As for all the White Stallions, that's a common and really silly bug. For anyone who doesn't know, there are a bunch of spells allocated for future Draenor mounts which they copied from the White Stallion and never changed to point to a proper new mount. So there's a bunch of mount spells that seems to summon White Stallions. That in itself isn't so strange as they copy object data like that all the time. The silly part is that Armory queries return them as real, owned mounts for your characters. No idea why. The query still fails to return several real mounts you own, but then it does return pretend ones.. This is a problem we would face on Warcraft Mounts as well, except that we have it coded to ignore mounts that aren't in the game.
Actually, I was wrong. I looked at the spell IDs for all the "White Stallions" and they seem to be for mounts you do own, it's just the name the API is using is old. The people (person?) who handles that was working from a very old copy of the mount spreadsheet data. Or rather they haven't updated it as mounts developed during the beta. Possibly they weren't even notified.
I get the impression a very, VERY few people are tasked with dealing with Armory and API issues and they're over-taxed. In the developer forums only one person seems to respond (if ever) and they're not a community manager but someone actually working on this code. I really think they're not getting much help.
This is infuriating for us as it makes maintaining WCM that much more difficult and we never get a response to our bug reports. I know Blizzard uses the excuse that they're hiring and training quality people as fast as they can (to work on WoW at least) but in this case I call bullshit. It doesn't take someone with great experience and immersion in game mechanics to deal with this stuff, none at all in fact. They could hire people tomorrow to help with website/API stuff at minimal risk. I'm now convinced they're not giving the area the amount of resources it needs. As for why, who can guess? I've noted many times that documentation teams are neglected, sometimes even openly resented, by big companies as they're not creating actual products (which galls the bean counters) and they annoy blinkered developers who have to take the time to send them info. Maybe this is similar.
Rant over. Sorry
