Addon Troubleshooting Guide

---

This guide will hopefully solve any problems you are having with the addon.

For instructions on how to download/install our addon see the How to Install section on this page.

Be sure you always completely close WoW and restart it after modifying your addons and before going any further. If all else fails, try a full computer restart, it can actually clear up a lot of issues.

*Note, our site only provides support for live realms. If you are playing on a private server, our addon may not work for you.

BEFORE YOU READ FARTHER: Is your version of our addon up to date? Is your version of TomTom up to date? If you answered no, please go update them as a first troubleshooting measure!

---

Table of Contents

1. I don't have an arrow.

2. My frame says No Guide Loaded.

3. Addon isn't showing up at all, or my guide list is empty.

4. I'm missing only one guide.

5. I lost my guide window!

6. I need to skip just ONE step!

7. I checked off a step and now I can't go back.

8. I checked off all of the steps and now I can't select the guide on the guide list.

---

Problem: I don't have an arrow to guide me.

Solution:

Make sure you have TomTom installed and updated. If TomTom is broken, try Carbonite instead for the time being.

---

Problem: When I log in, My addon says "No guide loaded". What should I do?

Solution:

Right click on the header of the addon, or the panda next to your mini map and choose "Guide List". Select a guide. There you go!

---

Problem: I have no guides in the guide list. Or, the addon isn't showing up at all.

Solution:

Make sure that you have two separate WoWPro files in your addon folder. Here are common locations for the file.

Windows XP location:

C:\Program Files\World of Warcraft\Interface\Addons

Windows Vista/7 location:

C:\Users\Public\Games\World of Warcraft\Interface\Addons

Mac location:

Macintosh Main HD/Applications/World of Warcraft/Interface/Addons

This picture is for a default windows 7 install, but should help you understand what we mean by seeing TWO folders, not one:



Make sure you also close wow 100% before trying to see your changes.

If, after trying all of this, you are STILL unable to see the addon in your in-game checklist, AND if you use the curse auto-updater, please try the following:


1. Open the Curse Client and go to Tools --> Options --> Games and Addons
2. UNcheck "Yes, manage the addons for this game" for World of Warcraft, then click "Done".
3. Try installing our addon again by dragging the extracted (unzipped) folders (BOTH WoWPro and WoWPro_Leveling) to your addons folder.
4. Start WoW back up. You should see our addon in-game.
5. You can now safely go back into the Curse Client and allow it to manage your addons - just remember not to update our addon with it, as you won't get all the guides!

Thanks to Screamindaemon for this workaround!

---

Problem: Wait! I'm only missing XXXXXX guide! What now?

Solution:

• Make sure you have the most recent update from our site. Curse, WoWInterface, etc. are not updated as frequently.

• If an update doesn't fix the problem, try emptying your Saved Variables, located in your WoW WTF Folder. Example for Windows XP: Program Files\World of Warcraft\WTF\Account\YOURACCOUNTNAME\Saved Variables Once there, delete all files that begin with "WoWPro".

• Open your addon folder for WoWPro Leveling. Select your faction folder. Make sure the guide is in the folder. If it is, check the .xml file and be sure it's on the list.

• If the file that you are missing is Horde Vash'jir, try the following:

  Open the WoWPro_Leveling folder, then open the Horde folder. Open "80_82_Arixan_Vashjir.lua" with a text editor (like Notepad). Go all the way to the last line.

  The last thing you should see is...
  

  end)
If it is not there, then add it underneath the ]]

---

Problem: I lost my guide window!!!

Solution:

Reset your profile. Right click on the panda or open your Interface menu, Addons tab. Under WoW-Pro Guides, click WoW-Pro Profiles, then Reset Profile.

---

Problem: I need to skip a step, just one, not 100. How?

Solution:

Right click on the step. If you still have trouble, see the next solution.

---

Problem: I checked off a step, and now I can't go back!

Solution 1:

Right click on the guide window header, click on "Current Guide", uncheck the steps that you want to go back to.

Solution 2:

If the first way doesn't work. Reset the guide. Right click on the guide window header. The last option should be Reset Current Guide. Click that baby!

---

Problem: I clicked off all of the steps and now can't select my guide in the guide list.

Solution:

Shift click on the guide in the guide list.

---

If none of the above solutions work for you, feel free to contact us in the Addon Questions Chat.

If possible please copy any lua errors you are receiving or take a screenshot of your issue. Thanks!

Learning git/github with WoWPro Addon - Part 1

This is the Part 1 of the guide on how to use git / github, covering Introduction and Installations.

Table of Contents

1. Introduction
2. What’s git?
3. What’s github?
4. Tutorial: Getting started

---

---

1. Introduction

---

WoWPro addons are developed using a control version system called git and hosted in github, a git public hosting site (I’ll explain what that means later on). Although you are definitely not required to learn git in order to contribute with WoWPro addons, it certainly wouldn’t hurt.

• Who this guide is for exactly?

It is mainly designed to be useful to WoWPro addon developers, allowing them an easier and more resourceful access to the project. For people out there with some programming skills, who want to contribute with the development of the addon, then this guide is definitely for you! Along with the tutorials themselves, I'll also show some "etiquette" suggestions when using git / github.

For guide writers/coders/editors, this guide can certainly be also useful. However, just be aware that we are trying to centralize guide edits, posts and bugs on their respective community pages here on WoWPro.com. So, we ask you to not push your changes directly into the original github's project. But even with this restriction, using git can help tremendously in your task! I'll explain all that in the next part of the guide, as well as some "etiquette" suggestions.

For people who are reading this guide right now and have no idea what this is all about (like general WoWPro addon users), but are curious and willing to learn new things, then I invite you to also read the guide. But I won’t mind if you go somewhere else.

Also, this guide assumes Windows users, but if you have another operating system, you should be able to follow it just fine, as the git user interfaces should be similar across OSs.

• What this guide is not?

There is a plethora of guides, tutorials, articles on how git will save the world, articles on how git sucks, etc on the Internet and it is not my intention to compete with them (in fact, I’ll provide several references at a later time). Partly because it wouldn’t be useful to the community here and partly because I’m not an expert on this subject! So, this guide is really just an overview of git and github, with some tutorials focused on WoWPro addon.

---

---

2. What’s git?

---

Let’s say you have a project composed of text files, that you continuously perform changes. Since the changes can be somewhat sensitive, you then decide to keep track of different versions of the same files, over time. The classical way is opening up the relevant, original file in a text editor, make the changes you want, and then use the “Save as...” option. Then, the name of the new file can be the original’s, plus some other identification, like a version number or the date it was created/modified.

But as the number of versions increases, it gets difficult to know what each of them actually means with just different name files. So, you could also improve this pedantic version control by writing, at the beginning of the text file, a change log, enumerating all the changes you performed in that particular version.

It works, but as you can see (for a number of reasons), this cumbersome system does not scale well with the number of files/lines, number of versions, etc. So people developed other, smart control version systems, of which git is one of them. These can perform easily all the processes described above and more! You’ll see some of the functionalities later on.

Before we get to the tutorials, there’s something else I should mention: what happens if you have more than one person working on the same project? This leads us to github...

---

---

3. What’s github?

---

You can do all the control version processes described above with git, in your local computer. You don’t really need to be like me, who does not remember even what he had for dinner last night, to appreciate easy access to changes / versions / comparisons in a personal project you’ve been working on, say, for months.

But a control version system really shines when more than one person is working on the same project, especially nowadays with all the open source projects and global collaboration. For that, a git project can be hosted in a server, which can then be accessed (and potentially modified), by people around the world through the internet.

Github is git hosting site, which provides interesting functionalities to project management and collaboration. You’ll learn some of them in the next tutorials.

---

Nomenclature:
Repository (repo, for short): a git project, its files and information stored by git, 
such as the different project versions. A repository can also refer to a 
full copy of a git project (more on that later).  If it’s located in your local computer, 
then it’s called “local repository”. If it’s shared, in a server, it’s called remote 
repository. Usually, you need a local repo in order to work with a remote one.

---

Now let's get on the hands-on...

---

---

4. Tutorial: Getting started

---

Let’s start by downloading and installing git. There are several tools and interfaces that you can use to do git control version, from the blander, but more robust command lines to graphical interfaces. For this guide, we’ll use a git interface for Windows, called Git Extensions. For a complete list of interfaces, including the original one for unix/linux, check the following reference link: Git Interfaces list.

You can download the latest version of Git Extensions from here:

http://code.google.com/p/gitextensions/

Or more directly, for the version as of this writing, here:

Direct Download Link

Run the downloaded file to begin the installation:

Unless you have absolutely sure you have the required softwares, check to install both of them and continue in Next:

For the next step, leave the installed features as they are, just click Next. But here, let's use Putty:

Then, just continue with the installation. At some point, it will ask you to install Git (which is actually the core’s program) and kdiff3, which you shouldn’t worry about it. For both, just use the default options as they are and keep clicking “Next” or “Continue”.

If the installation is successful, you should see a new icon on your Windows desktop (and/or somewhere in the Windows Programs menus), that looks like... hmm... a Tauren?. Open the program Git Extensions, click “Ok” if a checklist settings window is shown, and you should finally see something like this:

For this guide, as you can see, we’ll use the graphical interface, but don’t be afraid to use the git command line if you want to. Git commands are few and easy to remember (yes, even to me), since they are all English words. If you want to try that later, you should see a program called git bash, which opens the git command line.

Ok, now let Git Extensions rest for now and let’s deal with github...

Go on github.com and click on the big, blue button. Don’t be scared about the plans, prices... for public projects such as the WoWPro addon, github is completely free, easy and quick to sign up and use.

Now, choose the Create a Free Account option. Unless you already have a github account, just choose an username, e-mail, password and you’re good to go. Your github home looks a little empty right now... but we'll fix that in the Part 2 of the guide!

Using the WoW-Pro Recorder

In this guide, I'll go over how to use the WoW-Pro Recorder to help you write leveling guides. The Recorder is awesome both for writing addon guides, AND for writing paper guides - the pseudo-code is very simple and works GREAT for an outline for your paper guide, and has all the information you'll need including coordinates, quest IDs, and NPC names!

Coming Soon: The Recorder will soon have the ability to add notes to quests, add custom steps, and delete steps on the fly, but right now all it can do is record automated steps. I'll post comments on this guide, as well as update the guide, when the new features are added to the recorder.

---

Table of Contents

---

1. Downloading the Recorder
2. Creating a New Guide
3. Editing an Existing Guide
4. Recording
5. Saving Your Work
6. Working With the File
7. Submitting Your Work
8. Frequently Asked Questions
9. Comments

---

Downloading the Recorder

---

To get started, you'll need to download the guide recorder. There are versions available on Curse and WoW Interface, but I've got a handy link here that includes:

• The In-Dev (most up to date) version of the WoW-Pro Addon
• Cataclysm-specific leveling guide files completed so far
• WoW-Pro Recorder

Download here.

Unzip the file into your beta addons folder. You should have three separate folders:

• WoWPro
• WoWPro_Leveling
• WoWPro_Recorder

Everything should be ready to go - fire up the beta and log in!

[Back to top]

---

Creating a New Guide

---

If you'd like to append a guide that's already been created, skip to the Editing an Existing Guide section below.

To create a new guide, simply click on the "new" button. It's toward the right side of the Recorder's bar, and it looks like a piece of blank paper.

This will bring up a dialog box asking what type of guide you'd like to create. For now, we only have one type, and that's Leveling! Select it.

This will being up a new window. Now, some of these fields will be automatically filled out. I need to make this very very clear:

YOU HAVE TO HIT "ENTER" FOR EVERY SINGLE FIELD EVEN IF IT'S ALREADY FILLED OUT!

I plan to fix this in the future but for now please just hit enter in each field. Sorries!

Note that the stuff you put in these fields isn't really that important, and can always be edited later.

Once all of the fields are filled out, just hit "Register Guide". If you did it correctly, your guide window will change to a mostly blank guide with one step, called "First Step". If it doesn't change, it means you didn't hit enter for every field - try going through them all again.

Now that you have a new guide, you can start recording! Skip to the Recording section below.

[Back to top]

---

Editing an Existing Guide

---

If you want to add to one of the guides that's already included in the addon, OR if you have saved a guide using the recorder and would like to edit it, this section will explain how to do that.

All you need to do is open up the guide you want from the guide list, just as you would if you wanted to play it! Don't worry if it's already completed - if the recorder is enabled, the addon doesn't automatically ask if you want to go to the next guide.

Note: Guides saved with the recorder currently aren't displayed on the guide list. Instead, you can access them by clicking the "Open Guide" button (it looks like a folder). This will open a dialog where you can select the guide you want to edit. This list will contain ALL guides, both those in the WoWPro_Leveling folder, and those you've saved using the Recorder.

[Back to top]

---

Recording

---

First of all - the recorder is set to "REC" or record, by default. You can use the record (circle) and stop (square) buttons to toggle between recording and not recording. This can be useful in several situations. Say for example you take a break to do an instance - you can stop recording during the instance so instance quests aren't tracked. Similarly, if you for example need to abandon and re-accept a quest, you can stop the recorder so the second accept step isn't tracked.

Once you have the guide you want loaded and the recorder is set to "REC", you really don't have to do anything - just play the game! It can be useful, however, to keep in mind the things that the guide recorder records.

• Accept steps:
  • Quest Name
  • Quest ID
  • Location (including zone if it's different from the title zone)
  • Quest giver name (if you have them targeted)
• Complete steps:
  • Quest Name
  • Quest ID
  • Location of the LAST place you completed a quest objective
  • Use items for the quest
• Turn-In steps:
  • Quest Name
  • Quest ID
  • Location (including zone if it's different from the title zone)
  • Quest giver name (if you have them targeted)
• Get Flight Path Steps:
  • Location as the title
  • Quest ID of the last quest you accepted
  • Location (including zone if it's different from the title zone)
  • Flight master name (if you have them targeted)
• Set Hearth Steps:
  • Location as the title
  • Quest ID of the last quest you accepted
  • Location (including zone if it's different from the title zone)
  • Innkeeper name (if you have them targeted)
• Level Up Steps:
  • Your level as the title
  • Quest ID of the last quest you accepted

If you make a mistake while recording, you can delete the last step recorded by using the minus (-) button.

I recommend recording while in scroll mode. This will allow you to see what you are recording. You'll note that the bottom step will be highlighted - this is the active recorder step. New steps will be placed AFTER this step. This is also the step that will be edited when using the edit or delete buttons.

To change steps, simply left-click on a different step! You can also right-click a step to open a small menu. With this menu, you can move the step up, down, or clone it.

You can add new steps by clicking the "Add Step" button - it looks like a plus (+) sign. You can choose to have the recorder automatically fill in information from one of your quests, or you can fill everything in for a step from scratch.

You can also edit the selected step by clicking the "Edit Step" button - it looks like a pencil.

Now that you know how to record, you need to know what to do with the data you are gathering.

---

Saving Your Work

---

Though the recorder does save your work automatically when a new step is added, it's still wise to save it manually, and often! That's because when WoW closes unexpectedly, it doesn't always save it's saved variables, and your data may be lost!

You can save your work at any time by clicking on the save button. It's on the far right of the Recorder's bar, and it looks like a little disk.

Clicking this button does two things.

FIRST: It will save your data in the WTF file. When you quit and log back in, your guide will be loaded and you can select it at the bottom of the guide list. Note that the guide is also automatically saved every time a new step is added.

SECOND: It will open a dialog box which contains the code for your guide. This is how you will submit your guide, and also the best way to manually save to make sure you don't lose your work - just copy/paste the stuff in the box into a text file and save it. You can also use this to work with your guide to fill it out, change the order, and more - we'll cover that later in the Working With the File section. For now, just know that you can safely close this box without doing anything to it if you want to.

Just hit that save button often and you'll be okay, I'll try to get an auto-save feature enabled soon!

[Back to top]

---

Working With the File

---

Note that with the advanced features recently added to the recorder, it's no longer necessary to work directly with the file. Reading this section still may give you some insight into how the files work, though, which can be useful.

If you would like to do a bit more advanced work with the guide file, please read this section. No coding knowledge of any sort is needed - the guide files are written in pseudo-code and they are very easy to understand once you have a key.

First of all, open up your favorite simple text editor. I prefer Notepad++, it's a WONDERFUL editor with lots of very nice features.

Open up a new text file. Now, hit the save button on the recorder to bring up the code for your guide. Select all (Ctrl+A for PC users) and copy (Ctrl+C for PC users). Paste your code into your new file.

You should see something that looks similar to this:

A Clear the High Road|QID|24504|M|31.42,13.32|N|From Nura Pathfinder.|
f Hunter's Hill|QID|24504|M|39.75,20.18|N|At Unega.|
h Hunter's Hill|QID|24504|M|39.30,20.05|N|At Innkeeper Hurnahet.|
C Clear the High Road|QID|24504|M|35.93,15.58|
L Level 30|QID|24504|N|You should be around level 30 by this point|
T Clear the High Road|QID|24504|M|37.36,16.70|N|To Tunawa Stillwind.|

First, I'll explain how to read this stuff and what it means. Then, I'll tell you how you can improve your guide file's code to make it even better!

Anatomy of a guide step:
Each step is only ONE LINE of code. A new line means a new step to the addon.

Step Type:

The first letter that you see all by it self at the beginning of the line is the step type. Every step has a step type. These are the types of steps that the addon can process:

A = "Accept"
C = "Complete"
T = "Turn in"
K = "Kill"
R = "Run to"
H = "Hearth to"
h = "Set hearth to"
F = "Fly to"
f = "Get flight path for"
N = "Note:"
B = "Buy"
b = "Boat or Zeppelin"
U = "Use"
L = "Level"
r = "Repair/Restock"

The Recorder only automatically creates A, C, T, h, f, and L type steps. If you want the guide to have other types of steps, you'll need to add them in yourself.

Step Name:

The step name is the word or set of words that follows the step type. This is often a quest name, but is sometimes a location or other short descriptor for the step. The addon knows when the step name ends based on the | symbol.

Tags:

The rest of the step is defined by tags. Tags basically either flag the step for a special function, or feed a piece of information to the addon. The most common tags are map tags, note tags, and quest ID tags. There are a LOT more tags, too, but I won't cover them all here.
|QID|24504| = Tags the step as being tied to quest #24504. EVERY step must have a quest ID!

|M|37.36,16.70| = Tells TomTom where to map it's arrow to.

|N|To Tunawa Stillwind.| = Displays "To Tunawa Stillwind" as a note for this step. These should be limited to one or two sentences - we want to minimize reading as much as possible!

This covers the basics of the pseudo-code. It would be really awesome if people wanted to improve their guide file code before submitting it, since it's pretty bare-bones otherwise. However, some guide code is MUCH better than no guide code, so if you don't feel comfortable doing this, don't worry about it!

If you'd like to learn more about the pseudo-code and how to use it, check out the addon's documentation page!

[Back to top]

---

Submitting your work

---

So now you've got some stuff recorded - maybe you even edited the code to make it a bit nicer. What do you do with it?

Well, lucky you, it's really easy to submit your code to the addon! All you have to do is make a comment on this page containing your copy/pasted code! Be sure to disable rich text and set the input format to bbcode so the line break don't get wrapped. I'll look it over, and if it seems sound, I'll put it into the addon!

Remember that not only are we trying to get a lot of addon guides done, we also want to make more "paper" guides - guides here on our website. If you'd like to make a paper guide based on your (or someone else's) recorded guide, go ahead! You already have most of the information you need for your guide at your fingertips - all you need are maps and screenshots. The recorder file makes a very nice outline, as well, with steps that can be easily moved around to make the best questing route.

[Back to top]

---

Frequently Asked Questions

---

Register Guide doesn't seem to do anything - I don't see my guide being recorded! Is the addon broken?

No - you probably didn't hit enter for every single field. Go through them and try hitting enter for each.

My guide won't save, what's going on? I'm getting lua errors when I try to save!

In all liklihood, you didn't actually make a new guide and instead tried to record on the "Nil Guide" - the "No guide is currently loaded" guide. This will indeed produce errors. Make sure you click that "New Guide" button before starting!

I was testing a guide, and when I got to the end, it started repeating! What happened?

You probably accidentally had REC on while you were testing! Don't worry - the Recorder can't actually modify any of the files included with the leveling addon, so the double steps won't be saved over the real guide. However you WILL need to delete your WTF file for the Recorder before you can access the original guide. Make sure to back up your work first!

Please let me know if you have any questions about this process, either by PM or by comment!

[Back to top]

WoW-Pro Dungeons Addon

Introduction

Hello all!

I am working on a new module for the WoW-Pro addon called WoW-Pro Dungeons, that should provide the framework for guides and information related to dungeons in World of Warcraft. Right now, the WoW-Pro Dungeons is still in its early alpha stage, but I decided to create this page to explain my own design ideas and to hear feedback from the community (especially those that are in the beta, since I'm not).

That way, if we decide to change something, I won't waste too much programming time.

Basic Idea

WoW-Pro Dungeons will make use of the WoW-Pro Guide frame, showing steps and information in a similar way, that happens now, with the WoW-Pro Leveling module. Because of this, only one module will be active at a given time, but there should be plenty of options for the player to switch between them, manually or automatically (more on that later).

But there are important differences between leveling and dungeon guides:

• dungeon guides do not have a fixed format and some players may only be interested in specific information, like a list of quests for a given dungeon or its bosses fights, and not in full walkthrough guides;
• leveling guides are much more popular, so I would not expect good quality walkthrough guides for all dungeons, at least not initially. Given that, it would be better if we provide ways to accept smaller contributions from the community.

Therefore, unlike WoW-Pro Leveling, WoW-Pro Dungeons should allow access to different types of guides, for each dungeon, from the more basic to the more lenghty. For another hand, the dungeon guides should follow, as much as possible, the format of the WoW-Pro Leveling guides, to not confuse guide writers and players.

Types of Dungeon Guides

The types of guides, for each dungeon, I'm thinking of are the following:

• Location: At least for some dungeons in Cataclysm, the player has to discover them before using the Dungeon Finder directly. The location "guide" can contain a single coordinate step to map (something that I could include as default) or be more complex, for dungeons that require a lot of running around (or flying) to get to the actual dungeon portal. The location "guide" could also be used by dead players unfamiliar with the dungeon, unsure on how to get back to the dungeon portal.

• Quest list: Showing the list of all quests that should be completed in the dungeon, marking which ones the player already has; has completed and turned in; have completed but not turned in; whether the quest is too high level; etc. All these will make use of the format defined by the WoW-Pro Leveling steps, like Accept/Turn-in, and also the mapping by TomTom, showing where to get and where to turn in each quest. It will also allow the use of class/level/etc flags.

  EDIT: It seems quests are more easily picked up in cataclysm dungeons, so this guide type may be obsolete.

• Boss guides: Guides that explain boss/encounter fights. They are meant to be used in dungeons, so some restrictions on mapping will apply. It will also allow the use of class/role/etc flags. The idea is that the guide should be short enough to be read by a player just before fighting the boss, but this can be changed.

• Walkthrough guides: The pinnacle of dungeon guides, steps that form a complete walkthrough in the dungeon. The idea is that this type of guide should be used mainly (or completely) inside the dungeon, so some restrictions on mapping will apply. WoWPro already has several good of such guides:

  http://www.wow-pro.com/dungeon_and_raid_guides/5player_dungeons

  Though probably some (the lower levels?) will need to be updated or re-written for Cataclysm.

• Achievements guides: Guides for completing achievements related to specific dungeons.
  

Once I get the addon in a more stable way, I'll provide at least one guide of each type, as an example, and also some instruction on writing dungeon guide for the addon. Again, the format should be quite similar to the Leveling guides, but not completely.

Planned features

• Option to allow smart auto-load of dungeon guides, based on being in a dungeon, boss fight, etc.
• A frame to allow guides to show images.
• Allow sharing guide steps with party members (especially good for boss fights).

• Dungeon names, levels and progress come from LFG tool.
• The progress comes from the dungeon achievement, when possible it will show the number of missing/defeated bosses, to mark the dungeon as completed.
• Level ranges can be by allowed or recommended levels.
• Dungeon names will likely have colored text, like the LFG tool, but a different highlight than shown in the above image.

Feedback Questions

If you have any suggestion/info on the following topics, please post in this thread.

• How much the Dungeons module should interact with Leveling Guides? For example, if you skip a quest in a Leveling guide, that is a pre-requisite to a Dungeon quest, would you want the Dungeon guide skip steps related to that skipped leveling quest?
• Should this addon support guides for raids? If so, what would need to be changed (if any) in the layout discusses above?
• How to deal with heroics? I think most, if not all, guides that works in the normal mode will work for the heroic versions of the dungeons. So, my idea is to just have a 'heroic'/'normal' tag, that guide writers can use, in specific guide steps. Then, those steps would only be shown if the player is in the heroic/normal version or if the player set an option for that. Or, I could include all the heroic versions in the dungeon list pictured above, with their own guide types icons.

More info and images to come later!

WoWPro Addon - Keybindings

Just a quick blog entry to revisit a WoWPro addon feature...

WoWPro addon has two keybindings implemented, that you can make use of while playing:

• Use Quest Item: Default key: CTRL-SHIFT-I
  Attempts to use the first quest item shown (as a small clickable button) on the addon's guide panel, if there's one.

• Target Quest Mob: Default key: CTRL-SHIFT-T
  Attempts to target the first quest mob shown (as a small clickable button) on the addon's guide panel, if there's one.
  

By "first" above, I mean from top to bottom on the addon's guide panel, following the guide progression.

Example

Instead of clicking the quest item button associated with the quest "Speaking their language" (shown in the image below), you can use the keybinding to use that item (default: CTRL-SHIFT-I). In this case, the pressed keybinding blows the horn to summon the quilboar's chieftain... *snort*

How to change WoWPro keybindings

Open up the game options frame (ESC), and click on Keybindings.

Scroll all the way down (or almost all the way, depending on other addon's keybindings you might also have) to find the WoWPro keybindings. If you haven't changed the default keybindings yet, you should see something like this:

Then you can change WoWPro's keybindings like any other in the game, including also adding a second key for each.

Known issues

• If both the top "sticky" step and the imediate follwing step have clickable item/target buttons, then the keybinding will favor the non-sticky step. That's because I figured that would actually the "current" guide step. In any other case, though, the keybindings should work as expected.

If you notice any other issue, please feel free to post a reply here or on the addon's general bug report page.

Also, I don't plan (myself) on adding any more keybindings to the addon, but I wrote that part of the code to be easy to expand. So, if any other developer wants to add more keybindings, I'll gladly point you the way.

Good questing! *snort*