The problem with GupPet
STOP RIGHT THERE! As of early December 2011, the author has begun updating the addon again. The new version (2.020-ish) works properly. See here for more details.
If you have been using the addon GupPet, you’ve no doubt noticed that (a) it has problems with swimming mounts in Vash’jir, and (b) it has problems with any of the new mounts from 4.0.6 onward. This is a shame since GupPet is otherwise one of the most sophisticated and well-featured random mount addons you are likely to encounter. Fortunately, all is not lost. I have some tips on how to fix both issues.
Easy one first – the swimming mount issue
In the most recent version, 2.018, the following appears in the release note.
Fixed the bug where a flying mount was selected while swimming if you only had a mount that can be used as ground and fly
This got me thinking: what if that broke something else? So, I downgraded to 2.017. That fixed the problem!
This is a little harder to sort out, but isn’t that difficult if you’re familiar with using text editors to edit configuration files.
GupPet puts all of its mount data in a single file called
Gup_MountData.lua. The trick is to find a mount similar to the one you want to add, copy it, paste it where needed, and then edit the new data to add your mount.
- Find your Addons. On an XP box, it’s
C:Program FilesWorld of WarcraftInterfaceAddons, in Win7 and Vista it’s
C:UsersPublicGamesWorld of WarcraftAddons. Inside that folder you will find a folder called
- Find the file to edit, and open it with a text editor. The file is called
Gup_MountData.lua. You can use NotePad, but I recommend one of the free replacements such as NotePad++ (which will be used for this example).
- Find a mount similar to the one you want to copy. In this case, I want to add my new Subdued Seahorse mount, so I’m going to copy the seahorse mount that everyone gets in Vash’jir, as you can see.
- Copy that mount’s info, and paste it where it needs to go. In this case, it goes right at the end of the aquatic mounts section.
- Edit the name of the mount. This is not required – the mod will work either way – but if you don’t edit the text on the far right (a programming comment), you may forget what’s what in your updated file. DO NOT REMOVE THE DOUBLE-MINUS AT THE START OF THE DESCRIPTION. The addon will break if you do.
- Find the mount on WoWHead. You need the ItemID of the mount. There are many ways to get that information, but this is the surest.
- Find the ItemID. The ItemID is the unique identifier of the mount (not it’s reigns or similar "item" that teaches you the mount). The ItemID will be the number at the end of the URL for that mount’s WoWHead page. Note the ID and write it down.
- In the LUA file, change the ItemID of the copied line to that of the mount itself.
- Save the file and you’re done! If you are logged in to the game, you will need to exit the game and re-start it ((There are other ways, yes, but this is the most reliable way to get the right results. Hush. Do eet.)).
And that is it! You should now have the Subdued Seahorse as a usable mount in GupPet if you should ever catch Poseidus out on a stroll.
Finally, at the top of the file is a guide to the flag logic that you can use when adding mounts of various types.
When upgrading, don’t forget to copy this file off as a safeguard against being overwritten by one with incomplete information. You will need to manually inspect the upgrade file to ensure that all your mount data is preserved in the new one. Now, I suspect that any upgrade that comes down the pike will be up to date with the latest mount data. But I also find it unlikely that we will see an upgrade since this one is close to eight months out of date (nine, if you don’t count the broken 2.018). Otherwise I’d not be writing this guide.
Hey, if you know of a maintained addon that has all the bells and whistles that this one has, please do drop a line in the comments. And, if not, then at least we can extend the life of this lovely piece of software a bit more. Who knows, we might keep it running into 5.0!