WotLK Classic: GetCompanionInfo does not return mountType

fullmoon_sulfuras · 09-05-22, 05:57 PM

I was looking at this thread about GetCompanionInfo, but when running on client 30400 (BCC pre-patch)

Code:

/run print(GetCompanionInfo("mount",1))

I get

Code:

24379 Amani War Bear 43688 132117 false

Which corresponds to

Code:

creatureID, creatureName, creatureSpellID, icon, issummoned = GetCompanionInfo("mount",i)

How do I get the mount type for a given mount?

https://wowpedia.fandom.com/wiki/API_GetCompanionInfo

Of course, API_C_MountJournal.GetMountInfoExtraByID isn't available.

Thanks!

SDPhantom · 09-06-22, 06:21 PM

I forget which expansion it's added in, but the classic API doesn't support that feature. You'll have to get creative either with tooltip scanning or keep a database of mounts.

Xrystal · 09-06-22, 07:00 PM

Wowpedia shows the function being added 3.0.2 in Wrath but I was wondering the same thing as you but couldn't find anywhere that specified it. And a quick browse in https://github.com/Gethe/wow-ui-source/tree/classic I can't see any Companion related files.

Looking at the live equivalent https://www.townlong-yak.com/framexml/live we have Blizzard_Collections which handles the C_MountJournal functions which is noted as the latest replacement for the Companion system.

So it might be something they just chose not to add, or they have it working via another route. Perhaps look for the in game Blizzard equivalent frames and see if you can find something in the 3.4.0 classic link I posted.

Otherwise .. what SDPhantom said may be your only other option.

fullmoon_sulfuras · 09-07-22, 05:23 PM

Thanks for the answers. I could not find GetCompanionInfo in https://www.townlong-yak.com/framexml/3.3.5

SDPhantom · 09-11-22, 10:12 AM

The older version of the WotLK UI code isn't the same as the classic version just because the game client is built off a more recent version of the retail client. A lot of the APIs have changed over the years.

For example, in the original vanilla, event arguments were written into the global environment. They weren't passed to handlers like they are now. They started migrating it in the original TBC, but they didn't fully depreciate the old method until later.