WoW-Pro Addon Syntax

Jiyambi's picture

With the WoW-Pro Recorder, you don't really need to know the syntax (the language the guide files are written in) unless you really want to. However, taking a look at this syntax can help you understand how the addon works and can help you do a better job of writing and designing guides for the addon.

Remember, if you have any specific questions about the addon's syntax, feel free to ask in chat!

Table of Contents

  1. Overview
  2. Step Types
  3. Tags


To start with, I suggest working with a guide that has already been coded, rather than trying to start from scratch.

Opening a File to Edit

    The leveling guides can be found in Addons\WoWPro_Leveling\Alliance (or Horde). Go ahead and open one up in your favorite simple text editor. Do NOT use Microsoft Word or a similar rich text editor - the formatting used by these programs will break your guide file.

    I highly recommend the free program Notepad++, as do most addon authors - it's very powerful yet simple for beginners, with a very user-friendly interface.

[Back to top]

Anatomy of a Guide File

    Once you open up the file, you should see something like the following:

    local guide = WoWPro:RegisterGuide("LudoExpDaS","Achievements","Darkshore","Ludovicus", "Neutral")
    WoWPro:GuideSteps(guide, function()
    return [[

    In the example, where I say "INSERT GUIDE CODE HERE", you'll see many lines of code. We'll talk about those in a minute. For now, we're going to talk about the guide registration functions.

[Back to top]

Guide Registration Function

    The guide registration functions are what tells the addon the overall information about the guide. It contains several important parts, as follows:

    1. The function
        The actual name of the function we are calling: WoWPro:RegisterGuide
    2. The Guide ID
        The next section, “LudoExpDaS” in the example, is the Guide ID (or GID). This was implemented as a means to give guides a unique ID since zones and authors and level ranges separately might overlap. The GID consists of:
        • The first few letters of the author’s name (Ludo for Ludovicus in this case)
        • The first few letters of the guide zone or type (Exp for Explore in this case and DaS for Darkshore)
        • For leveling guides, the level range in double digits (0112 for 01-12 for example) is appended.
    3. Guide Type
        Which module the guide is for (practically, which tab it shows on). Achievements in the above example.
        • achievements
        • leveling
        • professions
        • dailies
        • worldevents
    4. The zone
        Pretty self explanatory. “Darkshore” in the example. This does not have to be a valid zone, but if it is not, a|Z| (zone) tag must be used on every line of the guide. It controls which map will be used for mapping (which can be overwritten with a |Z| tag), and also what name the guide have in the menu (ESC>Addons>WoW-Pro>Guide List) as well as the name showing at the top of the active guide pane. A better way of changing the guide name is to use the code WoWPro:GuideName(guide, 'name here') discussed below.

        NOTE1: You can provide more information about the guide after a "-" or a "(". For example, a valid zone entry would be Scarlet Enclave (Death Knight) or Durotar - Valley of Trials.

    5. The author
        Again pretty simple. “Ludovicus” in the example.
    6. Faction
        The faction the guide is intended for. Can be Horde, Alliance, or Neutral.

  • The return value
      The guide object is returned, which you can now feed into some additional functions to more fully describe the guide.

Guide Description Functions

  • WoWPro:GuideLevels(guide, start_level, end_level, mean_level)
      The starting, ending and average level for the quests in the guide. It is not what level you will end up at by doing the guide, it is the required level to get the quests even if you have XP locked down.
      The start_level controls when a guide will be offered to the user. The mean level sets the "color" of the guide to indicate difficulty. The end_level controls a warning to XP locked users that not all quests in the guide can be completed.
  • WoWPro:NewGuideLevels(guide, start_level, end_level, sort_level)
      With Blizzard's implementation of level scaling, guides now have a much larger range. This function is much like the GuideLevels function with one important difference. Instead of mean level, there is sort level, it controls the order several similar leveled guides will sort in the list of guides. [i.e. to keep Suramar, Broken Shore and Argus as the last Legion guides, rather than sorting in Alphabetically with BFA guides, all of which are available at 110]
  • WoWPro:GuideIcon(guide, icon_type, icon_reference)
      The icon to associate with the guide. With an icon_type of "ACH", the icon_reference is the achievment number (like the "Did ## quests in Tanaris").
      With an icon_type of "PRO", the icon_reference is a profession number.
      With an icon_type of "ICON", the icon_reference is an icon path.
      For Achievement guides, setting the correct icon_reference is doubly important, as it also sets the guide name, class and subclass from the game functions
  • WoWPro:GuideClassSpecific(guide, class)
      Tells the system that this guide is restricted to a particular class. Used for the "DeathKnight" only starting zone.
  • WoWPro:GuideRaceSpecific(guide, race)
      Tells the system that this guide is restricted to a particular race. Used for the "Goblin" or "Worgen" starting zones.
  • WoWPro:GuideProximitySort(guide)
      Tells the system to sort the steps in order of proximity every time you complete a step.
  • WoWPro:GuideNextGuide(guide,nextGID)
      Tells the system which guide to offer as the next guide. For a neutral guide you can use two GIDs separated by a "|" for each faction (Alliance first).
  • WoWPro:GuideSteps(guide, ...
      Register the function which returns the big "[[ ... ]]" quoted string of all the guide steps.
  • Fancy things: But this is really LUA code we are running, so we can do fancy things here. Look at this!

    This picks an icon for the Dwarf starting zone depending on the gender!

  • WoWPro:GuideQuestTriggers(guide, 33333,33334,33335) If you want a guide to autoload when a quest is accepted. Particulaly useful for holiday and other special occasion guides. The numbers are the QID's of the quests that you want to trigger the guide loading. The user will receive a dialog box giving them the options of Switch, Not Switch Now, or Not Switch Ever (for this quest).

  • WoWPro:GuideAutoSwitch(guide) Use Auto Switch if you want a guide to autoload when any quest from the guide is accepted. You can put the |NA| tag in to make a particular quest not cause a guide to switch. (such as for a dungeon or raid quest that the user is not likely to be completing immediately). The user will receive a dialog box giving them the options of Switch, Not Switch Now, or Not Switch Ever (for this quest).

  • WoWPro:GuideName(guide, 'Whatever name you want') If you want the guide name to be something other than the zone as defined in the guide registration parameters. This is the name that will be at the top of the guide pane and show in the list of guides.

[Back to top]

The Guide Code

    Finally, to the meat of the guide. Each line of code represents one step in the guide. You can have blank lines if you like to help break up the big block of code, but make sure they are COMPLETELY blank. A single space on an otherwise blank line can cause the guide to not load!

    For each line, You have several fields of import. The first is the step type, represented by a single case-sensitive character at the front of the line followed by a space. Step types tell the addon what icon to display, and can also tell the addon how to auto-complete the step.

    Right after the step type, you'll see the step text. For quests, this will be the quest name. For location-based steps (run to, fly to, hearth to, etc) this will be the zone or sub-zone name. For other steps, it can vary.

    After the step text come the tags, and this is where most of the "coding" comes into play. Some tags are required, some are not. These tags help the addon know how to handle the step, whether to display a note, where to map the coordinates, and more.

[Back to top]

Step Types

A – Quest Accept

    Use this every time you direct the player to accept a step.


      A Wanted: Dreadtalon |QID|12091|N|From the Wanted Poster just outside the door.|


      When a quest of the specified QID newly appears in the user's quest log.

[Back to top]

C – Quest Complete

    Use this when the player is completing a quest (or part of a quest)


      C Blood Oath of the Horde |QID|11983|N|Talk to the Taunka'le Refugees.|


      When the quest of the specified QID is marked (complete) in the user's quest log.


    • Use a |NC| tag to mark the step as non-combat, giving it a cog icon instead of crossed swords.
    • Use a |QO| tag to make the step complete based on one quest objective rather than all of them.

[Back to top]

T – Quest Turn-in

t – Quest Turn-in (suppressible)

    Use this every time you direct the player to turn in a step. FYI Be aware, abandoning the quest will also cause T steps to autocomplete, if that happens you need to manually un-check.


      T The Flesh-Bound Tome |QID|12057|N|Back at Agmar's Hammer.|
      t Test Your Strength|QID|29433|M|48.06,67.05|N|To Kerri Hicks.|


      When the quest of the specified QID disappears from the user's quest log or after viewing the completion page for the quest.


      For a "T" step, if the completion criteria for the quest have not been met, the step will not be skipped. So use a C step if you need it done.
      For a "t" step, if the completion criteria for the quest have not been met, the step will be skipped. When it is completed, the "t" will step magically reappear.

[Back to top]

R – Run F – Fly b – Boat/Zeppelin H – Hearth P - Portal

    These steps are all really variations on the same type – a location change.

    Hearth steps will automatically provide a use button with the hearth stone on it.


      H Warsong Hold |QID|11686|U|6948|


      When the subzone or zone name matches the specified one.


    • Use a |CC| tag to make the step complete when the user reaches a coordinate, rather than a zone name.
    • Use a |CS| tag to make the step complete when the user passes through a series of coordinates, rather than based on the zone name.

[Back to top]

h – Set Hearth

    Instructs the user to set their hearthstone. Make sure to spell the town’s name exactly correctly, or it won’t auto complete correctly.


      h Warsong Hold |QID|11598|N|At the innkeeper.|


      Auto-completes on the message “TOWNNAME is now your home.” TOWNNAME is the name of the subzone showing on your minimap when you are standing at this location, sometimes this is the name of the inn or something else more specific than actual townname

[Back to top]

f – Get Flight Point

    Instructs the user to get the flightpath. While convention suggests you use the subzone name as the step text, it's not required.


      f Moa'ki Harbor|QID|11585|Z|Dragonblight|


      Auto-completes on the UI message "New flight point discovered". Does not require or use a subzone name.

[Back to top]

K – Kill U – Use B – Buy r – Repair/Restock l - Loot L - Level N - Note

    None of these steps auto-complete on their own. They all behave exactly the same, and you should supply a tag to help them auto-complete if at all possible. Avoid the N type step as much as possible since it doesn't give the user any visual cue on what to do.


      K Fjord Crows |QID|11227|L|33238 5|N|Until you have 5 Crow meat.|


      IMPORTANT: This step has no auto-completion on it's own! You'll need to supply a tag to do that. Commonly used tags include |L| and |QO|. The above example uses a |L| tag. You can also effectively auto-complete with the use of an |ACTIVE| or |AVAILABLE| tag followed by a QID, note: -QID means when the quest is NOT active. For Note, Fly, or Run steps, using an ACTIVE tag instead of the QID will make sure that step is only active when that quest is active. Similarly, using an AVAILABLE when those steps lead you to an Accept step will complete them once the quest gets in your quest log. The only tricky thing is when an Run or Portal step is part of a quest and it involves a loading screen. Sometimes if you are lucky there is a QO tag that you may be able to use to auto-complete the step or using the zone name as the step name to complete on that basis.

[Back to top]

; - Comment Step

    Use this to put a comment into the guide. Since the guide lines are in a LUA bracket quote pair, you can not use a LUA double hyphen (--) to comment out a line.


      ; Begin Class specific training quests for Level 3
      A Steady Shot|QID|14007|M|60.26,77.54|N|From Bamm Megabomb.|Z|Kezan|C|Hunter|

    When the parser encounters a comment step, it records the line, but does nothing with it. Empty lines or lines of just whitespace are discarded. Use of comments by guide writers is encouraged, particularly when you do something clever or complicated. A ; after a step also starts a comment, but is discarded by the parser. Hence, the first type of comment is visible when viewing the guide step in game if debug mode is enabled, but the second is not.

[Back to top]

$ - Treasure Step

    Use this to register a quest tagged treasure in the game. Many treasures in the game have a flag quest behind them that is completed upon looting the treasure.


      $ Gurun|QID|34839|M|47.00,55.20|Z|Frostfire Ridge|ITEM|111955|N|And [money=120.00]|

    A QID is required for this type of step. The primary item should be indicated in the ITEM tag. Any secondary rewards should be in the note.

[Back to top]


|QID|####| – Quest ID

    QID, ACTIVE or AVAILABLE tag is REQUIRED for every step

    Even on a step that has nothing to do with any quest (e.g. Hearth steps) it is still important to have one of these 3 tags there as well. Use the ID of a quest which, if completed, means the user no longer needs to complete that step.


      A Wanted: Dreadtalon |QID|12091|N|From the Wanted Poster just outside the door.|


      Regardless of what other tags the step has, if the addon detects that the QID quest has been turned in, this step will complete.

[Back to top]

|ACTIVE|####| – Active Quest ID

    This tag will skip the step if the given quest is not active. I.e. you need to be on this quest, but not have completed it. This ID can be prepended with "-" sign to mean not active.


      A The Grand Melee|QID|13761|ACTIVE|13717|M|76.40,19.00|N|From Airae Starseeker.|

[Back to top]

|AVAILABLE|####| – Available Quest ID

    This tag will skip the step if the given quest is not available. I.e. you need to not be on the quest or have completed it.


      R Go here for Grand Melee|AVAILABLE|13717|M|76.40,18.00;76.40,19.00|N|Take this path|

[Back to top]

|QG|Some text| – Quest Gossip

    This is used for quests where the NPC will ask you a question and then you need to supply an answer. In the Timeless Isle, for example, Senior Historian Evelyna has a trivia quiz. Here is am excerpt from the quiz:


      A A Timeless Question|QID|33211|M|65,50.6|N|From Senior Historian Evelyna, daily.|
      ; This first C step "catches" until you GOSSIP with Evelyna and then goes away when it does not match the gossip
      C A Timeless Question|QID|33211|QG|Senior Historian Evelyna|N|Chat with Evelyna to get your question.  The question will change each time you chat with her, but we have a cheat sheet.|
      C A Timeless Question|QID|33211|QG|assault on Icecrown|N|Mord'rethar|
      C A Timeless Question|QID|33211|QG|bloodied crown|N|King Terenas Menethil II|
      C A Timeless Question|QID|33211|QG|Broken|N|Nobundo|
      T A Timeless Question|QID|33211|M|65,50.6|N|To Senior Historian Evelyna.|

    When you are interacting with an NPC between the GOSSIP_OPEN/_CLOSED states, the addon samples the text and matches it against the text in the QG tag. The match is case insensitive. If it matches, the step is not skipped, if it does not match, the step is skipped. If we are not interacting with an NPC between the GOSSIP_OPEN/_CLOSED states, then the tag has no effect.


      It does not do any auto-completion. The quest turnin will take care of it!

[Back to top]

|QO|1| – Quest Objective

    This is used for quests where you won’t be completing all objectives at the same time or when the objective locations are very specific and static.

    Please note that the addon is smart enough to know that when you use a QO tag, you want it to behave like a QO step, NOT a C step – so you can still use the C step type to get the nice icon for users to see. The quest tracker will only track the correct quest objective, and the step will auto-complete when that objective is complete. Remember also that you can change the step text to be something other than the quest name and it won't hurt anything!

    You can also list multiple quest objectives in one step, and the step will complete when all of them are complete. Just separate them with a semicolon ";".

    You must use a number instead of text. The number is the ordinal of the quest of objective. The addon will use the localized text to display the goal so people playing on non-English game clients will have a better idea of what to do. (Older guides for older content may use text instead of the ordinal number, but as Blizzard has changed how they display quest objectives, this usage should be discontinued.)


      C Watchtower Burned|QID|11285|QO|2|U|33472|N|Use torch on Winterskorn Watchtower.|
      C Bridge Burned|QID|11285|QO|3|U|33472|N|Use torch on Winterskorn Bridge.|
      C Dwelling Burned |QID|11285|QO|1|U|33472|N|Use torch on Winterskorn Dwelling.|
      C Barracks Burned |QID|11285|QO|4|U|33472|N|Use torch on Winterskorn Barracks.|


      Auto-completes when the addon detects the the QO # or the exact QO text in the QID quest's leaderboard in the user's quest log. Spelling and capitalization is very crucial here! (As mentioned above, quest text only works with older content)

[Back to top]

|O| – Optional

    This tag makes the step optional and will only show if the player has the quest in their quest log.

    Use this on an Accept step with a Use tag and it will only show if the player has the item in their bags, useful for quests that come from items.

    You can also use the |PRE| tag with it to only display the objective if the quest with the QID listed in the |PRE| tag has been completed.

[Back to top]

|PRE|####| – Prerequisite

    This is used in quest skipping logic, so please use it for every quest that has a prerequisite, optional or not! You only need to use this on Accept steps, the guide will extrapolate from there.

    You don’t need to include previous steps in the chain with this tag, just the most recent. However, you CAN include multiple prerequisites if it is applicable by adding a ; (semicolon) or a + (plus) in between each the quest IDs. Use one or the other, don't mix. A semicolon indicates that all of the quests have to be completed for this step to activate. A plus indicates that any of the quests can be completed for this step to activate.

[Back to top]

|L|####| – Loot

    Used when you need to make sure the player has a specific item or amount of an item in their bags. Add the quantity after the item number with a space in between. If you only need one of an item, you do not need to specify a quantity.

    Note that in some quests you loot an item, but it may not appear in your bags.
    If so, you need to use the a QO tag instead.

    Please do not use this along with a C type step or with QO tags, as it will cause issues in the tracking display.


      Causes the step to complete when the user has the specified item in their bag.

[Back to top]

|U|####| – Use

    This will create a button for the item specified so you don’t have to dig through your bags to find it.

    You don't need to list this on hearth type steps, it's added automatically.

[Back to top]

|C|Priest,Mage,…| – Class |R|Orc,Troll,…| – Race

    These will only show the step if you are playing the specified class/race. Use commas to separate entries to list more than one race or class.

[Back to top]

|N|…| – Note

    A general note for the step to add additional information. Please try to limit these to one or two sentences.

[Back to top]

|M|55.55;55.55| – Mapping

    List coordinates here. You can list multiple coordinates by separating them with semicolons ";". Make sure you list coordinates for every step! The addon CAN get coordinates from the in-game quest blobs, but we'd rather have our own coordinates listed.

    If you have more than one coordinate, you need to specify one of the |CS|CC|CN| tags.

[Back to top]

|Z|Zone Name| – Zone

    Use this tag if the step goes outside the zone for the guide. IMPORTANT – if you don’t use this tag and the coordinates are not in the guide’s title zone, they will show up WRONG.

[Back to top]

|S| – Sticky |US| – Un-Sticky

    These are for do-as-you-go steps. Use |S| on the do as you go message. Use |US| on a step with the same name when you want to have the user actually complete the step.


      C Galgar's Cactus|QID|4402|N|Loot Cactus Apples from Cacti|S|
      C Vile Familiars|QID|792|N|Kill the Vile Familiars in the north.|M|44.7,57.7|
      C Galgar's Cactus|QID|4402|N|Loot Cactus Apples from Cacti|US|M|44.7,57.7|

    In this example, the user is instructed to pick up cactus apples while killing vile familiars. Once they kill all the familiars they need, the stickied cactus apple step becomes a normal step.


      |S| tagged steps auto-complete when the corresponding |US| type step becomes active, so only one will be active at a time.

[Back to top]

|ITEM|######| – Item - followed by item number

    Use this tag to show an item related to the step. The icon (which can be moused over for details) and the item name will be prepended to the note text. (i.e. placed in front of the text that follows the |N|) Usually this would be the drop from the rare mob or treasure. This is a link, not a clickable "use" item. (for Use items use the |U| tag)

[Back to top]

|LVL| – Level

    Use this tag to denote a step that requires a particular level. There is also a step type, L, to denote a step that completes once the user levels up.


      For L steps, completes when the user reaches the specified level.


      For non-L steps, enable the step if the user is at least the specified level.

    Alternate usage - Step - hiding:

      prepend the level with a minus "-" sign to cause the step to not display if the user is over the specified level. (|LVL|-109|)

[Back to top]

|LEAD| – Lead In Quest

    Use for lead in or breadcrumb type quests, followed by the QID for the quest it leads to. This step will be checked off if the user has already completed the quest it leads up to.


      Completes when the user completes the specified QID quest (sort of like a second QID).

[Back to top]

|T| – Target

    Follow by the name of the mob or NPC you want the user to be able to target.

[Back to top]

|P| – Profession

    Two arguments are required: the name of the profession and its "number". There are three optional arguments that follow:
        The required form, with the name and profession number. If the toon has at least 1 in Alchemy, the step will activate.


        This adds the profession level, which defaults to 1. A "*" can be used to mean max level for the expansion, 700 today. If the toon has at least 42 (>=) in Blacksmithing, this step will activate.


        This sets the profession max level flag. A non zero value flips the sense of the profession level test. I.e. the toon would need less than 42 in Enchanting for this step to activate.


        This sets the profession max skill level. This defaults to 0. It will active the step if the current max profession level the toon could get without re-training is less than the argument. So this would require the toon to have Engineering(200).

    The allowed values for the profession names and numbers are:

      First Aid;129
      (Thanks Fluclo!)

In addition, if the step is an "A" step and you do not have the profession, the step and QID are marked as skipped.

[Back to top]

|CC| – Coordinate Auto-complete |CS| – Coordinate Auto-complete in Sequence |CN| – No Coordinate Auto-complete

    Use either CC or CS in order to auto-complete an r/R/N step when the coordinate (or set of coordinates), given in the |M| tag, is reached. If you are using a set of coordinates, the |CS| tag will make the step auto-complete only when the player follows the coordinates in sequence, from the first to last (final) coordinate, and the |CC| tag will make it auto-complete when the player reaches the final coordinate, regardless of the previous ones.

    The |CN| tag is used to indicate that a set of coordinates are just markers on the map and NO auto-complete should be done.

    If a set of coordinates is used in the |M| tag, one of these three tags is required or an error message will be issued.

    Auto-Completion of r/R/N steps:

      Completes when the user reaches the specified coordinate or series of coordinates.

Other step types will present the waypoints, but will not auto-complete when the last one is reached.
Some other completion method must be used.

[Back to top]

|RANK| – Rank

    This tag should be used as much as possible from now on, and denotes how important a quest is. 1 is the most important and will NEVER be skipped. 3 is the least important. Vital quest chains with great XP and item rewards should be marked 1. Things that are neutral in rewards but which are convenient to do should be a 2. Things that take you out of your way and aren’t particularly rewarding should be marked a 3. Anything unmarked will be considered a 1. In general, a character with heirlooms and RAF should be able to get through the guide on a setting of 1, while a character with none of these bonuses and who doesn’t do instances or have rested would need a setting of 2. 3 is more for completionists trying to get as many quests done as possible.

    The only other note to this: If you use a rank tag, you must make sure all quests following that one in a chain must have the same rank or higher. We don’t want the user to be instructed to pick up a quest that he or she has not done the prerequisites for.

    More specific descriptions:


      You don’t need to use it, it’s implied if no rank is listed. Never skipped no matter what setting. Use for quest chains that lead to the “final” quest in the zone. I’m not sure how the high level zones go, but for the mid level ones there is usually one quest that yields very high quality rewards and “finishes” the story for that zone. All quests leading up to and including this kind of a quest should be rank 1.


      These steps are only skipped by people on the lowest completion setting. Use this for quest chains that don’t lead to the “final” quest – though NOT if there are a ton of quest chains like this. I would say as a general guideline, between 1/4 and 1/3 quests should have this tag.


      Really out of the way or annoying quests with little return. I haven’t been using it too often. Something the typical user would NOT want to do, something only completionists would want to do.


      Denotes a step you only want to show when a guide is being run on RANK 1. Typical usage is for R steps when you skip content that rank 2 or 3 walks you through.

[Back to top]

|NC| – Non-Combat

    Used with the C step, This changes the step icon to a cog, giving a visual clue that the user needs to click on something (rather than kill something) to complete it.

[Back to top]

|NA| – Not Automatic

    If a guide is marked as an auto-switching guide using WoWPro:GuideAutoSwitch(guide), this tag is used to make this particular quest as not triggering an auto-switch. This is used for things like dungeon quests or other quests that are going to hang around in your quest log for a long time and could result in many irritating offers to switch guides.

[Back to top]

|CHAT| – Chat

    Used with the C step, this changes the icon to the Gossip icon, so you know you need to talk to someone.

[Back to top]

|REP| – Reputation

    Takes a set of two required arguments and up to two optional ones. Lets take an example:

    |REP|Operation: Shieldwall;1376|

      This is the minimally acceptable form. The first argument is the name of the faction and the second is the faction number. You can get faction numbers off of WowHead. Yeah, the number is all you really need, but then the guide would be unreadable. Besides, Blizzard has changed the names of factions in past patches, but preserved the faction numbers, so we feel safer in using the numbers. The third argument defaults to neutral-exalted and the fourth to 0. Explanations for them follow. This form enables the step if the reputation with "Operation: Shieldwall" is neutral through exalted.

    |REP|Operation: Shieldwall;1376;friendly|

      The third argument is a reputation or friendship range.
        Reputations are: hated, hostile, unfriendly, neutral, friendly, honored, revered, exalted

        Friendships are: stranger, acquaintance, buddy, friend, good friend, best friend

      Reputations are used with factions, like the Scryers or Tillers. Friendships were introduced in 5.1 for your status with individual NPC's like Gina Mudclaw.

      A reputation range is separated by a '-' like neutral-exalted. If only one element is present, like the example, it is doubled up and interpreted as friendly-friendly and means that the step is enabled only when friendly with the faction. Do not mix reputation keywords and friendship keywords or evil things will result.

    |REP|Operation: Shieldwall;1376;friendly;950|

      The last argument is either the reputation level or the reputation bonus detector. In the example, it specifies that you need to be friendly and at least 950 points into friendly. It will not activate for any higher levels of reputation. You use this for quests that appear at specific reputation levels instead of reputation boundries. We may in the future choose to obey the upper reputation limit as well.

    |REP|Operation: Shieldwall;1376;revered;nobonus|

      The last argument is the reputation bonus detector. In the example, it specifies that you need to be revered and not have purchased and used the "Grand Commendation of Operation: Shieldwall". This can be used in guides to prompt the user to buy the commendation at the right rep level. The last argument could also be "bonus" to detect that you have the bonus, but we did that for completeness rather than utility.

[Back to top]

|ACH| – Achievement

    Takes a set of one required arguments and two optional ones. Lets take a few examples:


      This is the minimally acceptable form. The first argument is the number of the achievement, 6031, which you can look up in wowhead. In this form, the step completes if the whole achievement is complete.


      This is the second form. The first argument is the number of the achievement, 6031, which you can look up in wowhead. The second, specifies the step in the achievement, in this case "firing off the fireworks in Orgrimmar". In this form, the step completes if the portion of the achievement is complete.


      This is the third form. The first argument is the number of the achievement, 6031, which you can look up in wowhead. The second, specifies the step in the achievement, in this case "firing off the fireworks in Orgrimmar". The third augment is the "flip" argument. In this form, the step completes if the portion of the achievement is not complete.


      This is the fourth form. The first argument is the number of the achievement, 6031, which you can look up in wowhead. The second is set to nil, so it is equivalent to the first case. The third augment is the "flip" argument. In this form, the step completes if the whole achievement is not complete.

[Back to top]

|BUFF| – Unit Buff

    Buffs, those things that appear at the top, like Sayge's Dark Fortune of Strength, can be detected by this tag and cause the step to complete. Multiple buffs can be specified with the usual ';' delimited list. Example:
    N Sayge's Dark Fortunes|M|52.94,75.94|BUFF|23735;23736;23737;23738;23766;23767;23768;23769|N|Sayge offers different 2 hour buffs.  Pick one and elect to get a written fortune for a chance at a quest item! We pre-select based on your class.|

[Back to top]

|PET| – Pet Detect

    The PET tag takes one, two or three arguments, depending on what you are up to. The second and third arguments default to 3;false if not specified.


      In the one argument form, this tests to see if less than 3 of the indicated pet. The creature IDs are not well documented. As far as I know, the only place to get them are in the Blizzard web API or by using the WoW-Pro debug log, which lists the IDs for all the pets you have.


      In the two argument form, this tests to see if less than 1 of the indicated pet.


      In the three argument form, this tests to see if you have >= 1 of the indicated pet. A true value flips the sense of the test.

[Back to top]

|BUILDING| – Building Detect

    The BUILDING tag takes two or more arguments, depending on what you are up to. The first argument is ignored and is used for documentation and second and following arguments are building numbers. You can find a list of building numbers for WoD at . If you have none of the buildings specified, then the step is skipped. As a special bonus, if the step does not have a |M| tag, one for the building location will be added. The addon uses the building locations on your Garrison map, so it won't be perfect, but it is pretty good.


      In the two argument form, this tests to see if you have the indicated building. In this case, a level 1 Lumberyard.


      In the three argument form, this tests to see if you have either a level 1 or level 2 lumberyard.

    Two special buildings types exist:


      In this form, it tests your Town Hall level. In this case, it checks that the Town Hall (Garrison) level is exactly 2. Only one level can be tested for. Note that this form does NOT set the |M| tag.


      In this form, this tests to see if you have built no buildings. No other arguments are paid attention to!

[Back to top]

|RECIPE| – Recipe Detect

    The RECIPE tag is used with tradeskills to detect if you have a recipe in your profession "book".

    B Recipe: Koi-Scented Stormray|M|71.61,48.87|P|Cooking;185|RECIPE|201503|L|133819|N|From Markus Hjolbruk.|

    This detects if you have the recipe (Koi Scented Stormray Spell ID: 201503) and if not to buy it. You should include the profession tag with skill level required. The number in the |L| tag is the item id of the recipe (133819) you buy and then click to learn it.

[Back to top]


Thanks, I'll try + in the

Thanks, I'll try + in the quest IDs.

|QO| Step not auto-clear on loading up guide

If you leave the game in the middle of a quest with |QO| steps, it doesn't auto-check off the steps.

For example in the following steps:
C Bitterblossom|QID|25297|RANK|2|M|29.4,31.6|NC|N|Collect a Bitterblossom from around the edge of the pond.|QO|Bitterblossom: 1/1|
C Stonebloom|QID|25297|RANK|2|M|27.5,34.1|NC|N|Search around the base of the rock formations for Stonebloom.|QO|Stonebloom: 1/1|
C Darkflame Ember|QID|25297|RANK|2|M|28.4,35.8|NC|N|Collect a Darkflame Ember from the brazier.|QO|Darkflame Ember: 1/1|

If I leave the game after doing Bitterblossom but before Stonebloom, the guide will reload with the following step showing:

(COG) Bitterblossom
Collect a Bitterblossom from around the edge of the pond.
- Bitterblossom: 1/1 (C)

So the guide has recognised the quest part is complete, but it doesn't auto-check off and move to the next step.

Hmmmm, I would think that if

Hmmmm, I would think that if those lines in the guide had a loot tag (|L|item number|) they would auto clear.

Ludovicus_Maior's picture

Re: Hmmmm, I would think that if


The problem is that the Guide loader makes some assumptions about what steps that were previously marked as completed should be cleared.

Its a conflict due to stupid daily quests.   Either the logic in the guide loader needs to be fixed or the NextStep completion logic needs to get a chance at the guide in order to re-complete the steps.

It used to work in the past and I managed to do something to break it.

Ludovicus_Maior's picture

Re: |QO| Step not auto-clear on loading up guide

Yup; I don't even have to look at the code to know that this is true.

But it may be tricky to fix.    On the queue.


Sorry, I couldn't edit this page, can you update the link to Profession, on the link it's #profession, but the link is looking for #prof, this means the link doesn't work.

Ludovicus_Maior's picture

Re: Profession


Estelyen's picture


I see you have recently added the ACTIVE tag to this list Ludo, so why did you not include the REP tag? I asked about that one quite a while ago (in january actually, a comment further down on this page) and it's still not on here ;)

Life isn't like a box of chocolates, it's more like a jar of jalapeños: What you do today might burn your a** tomorrow.


Ludovicus_Maior's picture


... cause I forgot and I am  a lazy bum who would rather gamble on the auction house and corner the market on wool cloth than write documentation :-).

Anyways, if I wrote it in January, it would have been wrong.   Your recent queries about friendships made me really look at the code and figure it out.


Emmaleah's picture

Question re: Neutral guides

Question about neutral guides.  Is there something you have to do to "Make" a neutral guide?  I made Valley of the Four winds, it is neutral and it is working fine...  Now I am trying to make one for Kun-Lai Summit.  I originally made it as alliance and it was fine, I tried to change it to Neutral (by changing the word in the first line - and adding |FACTION|Alliance| as needed. I think I had it loaded that way(but I can't be sure as it was several days ago.  I know I had it loaded on a horde char).  Then I took it into Word so I could use version compare and in general muked it up. 

NOW... I can get it to load if I register it as a Horde guide and put it in the guide.xml in the Horde directory (with Horde and Alliance faction tabs where appropriate), but I can not get it to load if I register it as a Neutral guide and list it in the guide.xml in the neutral directory.  I can't imagine what the differance could be.  I looked in other guides and I see some (but not all) neutral guides list two guides for the follow up (horde|alliance) I tried it with both one and two follow up GID"s.  I tried it with made up GID"s, I tried it with real (but not correct-like winterspring)) GID's I'm really out of ideas.

Also possibly related.  I originally had it registered as zone Kun-Lai Summit, the name that shows up on your map and it was constantly giving me zone kun not found using XXX. (note: NOT kun-lai) So, I tried taking the '-' out and making a space.  I don't think this made any differance but it now says zone Kun Lai Summit not found, using xxx.  Is there a way to make it recognize the hyphen in the zone name?

edit to add:  I probably originally made the guide before downloading the changes you made on July 9.  Maybe something in the changes is affcting this one.  (I DL'd that on the 12th I think, and im pretty sure I started this guide before that)

[/sigh now I have to get the CAPTCH right agian]

Emmaleah == bravely leading the way since ... um a long time ago... Smiling

Netural Guides

Make sure you have Neutral in the header of the guilde.  For example:

WoWPro.Leveling:RegisterGuide('FlucloPanda', 'The Wandering Isle', 'Fluclo', '01', '12', 'WkjLoc1220|BitAzs1220', 'Neutral', function()return Also, make sure you move it to the Neutral Folder and add the name of the guide to the Guide.xml file.Yes, I hate the captions too and they really do not serve any purpose.

Emmaleah's picture

neutral guides

the 3 items you have mentioned. I have done.

I think... this is just theory that it is one of two things ..

1) time.  it majically worked this morning, with out me making any more changes.  I had also deleted the saved variables files (related to Wow-pro) in the WTF direcotry last night, and I wonder if those don't get reread till you log all the way out of WoW, (as opposed to out of the character/reloadUI). 

2) the followup guide (in the example above ('WkjLoc1220|BitAzs1220') being also loaded.  This makes less sense, since eventually the chain has to end so it can't require a followup guide to always be loaded.

Emmaleah == bravely leading the way since ... um a long time ago... Smiling

Netural Guides

As for 1, you do have to log completely out of game for it to pick up these type of changes.  Step changes can be done with a reload, but headers and directory changes you have to do a complete reload.

For 2, if you use Nil as a value for the next guide, it would then know to stop at that point.

Emmaleah's picture

Neutral guide

I figured out what I was doing wrong... and boy do I feel bright for not figuring it out days ago. (of course it could have been some other typo before)  It must be a Capital N. (i.e. Neutral does not = neutral)  Anyway I have been struggling with that for several days, finally decided I was never going to figure it out, and posted... and... voila... I figure it out.

New question - somewhat related.  This involves guides between multiple characters on the same account.  I aluded to this in an earlier question, but I think I have a better understanding of whats happening now.  I have made a guide for Kun-Lai Summit all the way thru with alliance/horde steps.  I made it first with an alliance char, saved the file, then went thru with a horde char saved that file and merged them using MS Word version compaire (after spending a couple of hours - at least - trying to manually merge them).  In that process I printed a map of the zone marked it all up, and rearranged some steps to facilitate less travel thru the zone, etc, so things are in a differant order than when I made it (i.e. what order the progress would be in the saved variables).  I am now playing it thru with another horde char and this morning I finally figured out why it wasn't loading as neutral (see above) so I decided to try an alliance char (No, I have no faction loyalty).  It loads the steps that are faction tagged with horde instead of alliance.  What I think it is doing is using a copy in some cached spot, rather than reloading the guide?  I am opening it with recorder enabled (7/9/12 version). I delete the guide (in recorder) and reload it (thru the leveling module) I then reset it in the leveling module, (which I thought would query the game for quests completed and mostly appropriate checkoffs would happen?)  I logged into the char I first made the guide with (90 gnome) who has obviously finished the guide and most of the steps dont auto check off (around half do) and still it is showing the horde steps and more disturbing, several are checked off.  ( I suspect that is because it is not recognizing that a new guide was loaded and looking at the saved variables file, where it lists 1, true, 2 true, etc)

anyway... thoghts, helpful suggestions... all wou ld be apreciated.

Emmaleah == bravely leading the way since ... um a long time ago... Smiling

Netural Guides

One other thing I thought of just in case you didn't.  Make sure you remove it from the Horde directory and the Alliance Directory (also the guides.xml).  Otherwise, you will load that one over the neutral one.

Netural Guides

There shouldn't be any cross-over of the data as it reletes to each chaacter, as each character is maintained seperately based on the toon name.  What may of changed is how MOP handles the query for completed quests.  Ludovicus will have to weight in on that subject as I have not kept up with the API changes comming.  One thing you might check is the QID's.  Usually Blizzard uses one number for alliance and a different one for horde.  Also, make sure you that you are using the FACTION tag.

Ludovicus_Maior's picture

Quest API Changes

Yeah, I have kept up with the changes and right now, if you reset the guide or reset the addon, all historical knowledge of which quests have been completed goes away.

I have some code that tries to fix it, but it is not ready for prime time yet.  It seems to tickle a bug in the MoP client and causes a hang.


Emmaleah's picture

Neutral Guides

Thanks for getting back to me,  I find the way the forums work on this site to be disorienting and I can never find what I'm searching for.  I usually resort to google with wow pro as part of my search string.

Anyway to the topic at hand...

Are you sure its in its own saved variables file? I know there are some settings in the acct level and some by char name, but I haven't figured out what is where.  Also, I checked the Alliance char and there is no wow-pro files in her saved variable directory, so something odd is happening. 

Yes, I am using faction tags and qid's.  What is happening is that the Horde steps (the ones with the horde faction tag) are showing up for the alliance character and the alliance steps are NOT showing up.  They are not checking off, since the QID's are differant.  I know that the file is only listed in the Neutral directory's guide.xml.  The file may have also been in the Horde directory but not in the guide.xml in that directory

Emmaleah == bravely leading the way since ... um a long time ago... Smiling

Ludovicus_Maior's picture

Neutral Guides

So the FACTION tag is a filter tag.  I.e.  At the time the guide is loaded, it checks the toons current faction and drops the step if it is a mismatch.

The same applies to the C, R, and GEN tags.  

The value of the faction tag can be either HORDE or alliance; it is not case sensitive and extra spaces are trimmed.

Are you sure you managed to keep the Horde/Alliance side straight w.r.t. QID's?

Post some sample troublesome steps....

Emmaleah's picture

troublesome steps

As I am still away from WoW, (I forgot to patch my laptop before I left home, and hotel connections just aren't good for 16gB downloads) I can't post specific steps.  But what I did deduce was that this behavior I am trying to report only seems to happen when you have the recorder on,  I have repeatedly checked for correct faction tags/qid's and what I have determined is that the recorder does not reinitialize the guide, the same way that the main program does. (I'm not sure it can reinitialize a guide).It has nothing to do with horde/alliance, it is just more obvious when switching char (same acct) when they are differant faction.   So, if I want to reload a guide in the recoder I have to either switch WoW accounts, or delete the correct files in the WTF directory (since I am away from home I don't remember which file that was, I may have posted it on some previous conversation on this subject.)



Emmaleah == bravely leading the way since ... um a long time ago... Smiling

Ludovicus_Maior's picture

RE: troublesome steps

Hmm, the recorder interacts with the leveling module in strange and mysterious ways.

It has not had any TLC for awhile, and had just enough of a face lift to pass in MoP.

Emmaleah's picture

<grin> its all strange and

<grin> its all strange and mysterious to me.

When it comes to this addon, I am a technician, not a master.  I try to help where I can, but when I open the LUA for the program itself, i just shake my head and say wow, how did they figure this stuff out.

PS. Ludovicus Maior, welcome back, I hope things are not just stable, but looking up at your house!

Emmaleah == bravely leading the way since ... um a long time ago... Smiling

question about use of RANK

I know the ranks are new and being added after the guides have been
previous coded and fully functional, but I seem to have found an

I'm playing through the Horde > Ashenvale guide (Release version 2.2.4) and I currently have my addon set to use Rank 1 as my quest filter, just the necessary quests.  Here's the bug (or oversight). For the quests in this guide marked as Rank 2, optional, only the accept steps are left out of my on-screen display.  The action and complete steps still display. Making Stumps and Wet Work are the quests / steps that I'm refering to.  This really confused me for a minute before I realized why the addon wasn't working as well as normal.  This is the first character where I"ve used the filter, and actually forgot I had turned it on at all.

Tested by switching to Rank 2, and the Pickup lines appeared in my guide. Back to 1, and those disappeared, but the action lines were still the next thing on my display.

Are all steps related to a quest required to have the RANK tag, and not just the initial pickup step? Does this continue to apply to subsequent quests in the same questline, or should PRE tags be used instead?

Hope this helps someone who better understand the coding to troubleshoot this. I personally know only enough to know it's best if I keep my nose out of the live code and just send my observations back here. :)   Looking forward to an update.

alt-addict & wow-pro fan, 5 years and counting.

Ludovicus_Maior's picture

Re: question about use of RANK

Well, by an odd co-incidence, I have spun up my first toon with boa gear and decided to set the rank at 1 and plow through zones.

I ran into the same bug yesterday and am gonna fix it for the next update.

I am also trying to see if I can quickly add RANK 1 tags for key quest lines in existing guides easily.

Crackerhead22's picture

CC tag

Not sure what is going on, but it does not seem to be working.

Ludovicus_Maior's picture

In order or out of order

The difference between CC and CS is supposed to be what the termination condition is.

I have noticed a bug when doing a CS that it does not show them in order.

Are you saying that CC does not finish when you get to the N/N coordinate?

Crackerhead22's picture

Yeah, even when there has

Yeah, even when there has only been one cord on the CC tag it doesn't complete. 

For example, in Azhara Horde guide before I changed it.

R Wings of Steel|QID|24497|M|60.58,52.55|CC|N|Hop in a Wings of Steel and fly to Valormok.| Getting to that spot would remove the waypoint but not complete the step.

Ludovicus_Maior's picture

Extended LVL tag

The current |LVL|slevel| tag autocompletes if slevel <= character level.

I would like the current single argument form changed to |LVL|levelLimit| and introduce a two argument form |LVL|minLevel;maxLevel|.  The single argument form is equivalent to this two argument expansion: |LVL|1;levelLimit-1|.


The LVL tag causes the step to autocomplete if character level < minLevel or character level > maxLevel.

The current behaviour for the LVL tag is the same.


This change would let me support the banded quests for the Love is in the Air event.


Sounds like you are starting

Sounds like you are starting to need/want the capabilites Grail has built-in (both from this level concept, and from the lead-in concept).  :-)  The level one should be pretty easy because quests have a minimum and maximum level range.  However, the lead-in concept can be quite nasty, especially in Firelands because you need to handle both AND and OR concepts to know the proper lead-in details.  Good luck.

Ludovicus_Maior's picture

Grail Integration

Yeah, I was going to try doing a simple grail integration that would fill in the information on each quest from Grail if it was availible as a first step.

I was thinking that the LVL and LEADIN information would be a good start.

Min/Max for |LVL|

I agree and ran across the same issue with the Darkmoon Faire guide and was going to tackle the issue at some point.  Unless you want to change all the guides that have LVL, you might want to consider that if its missing max level that max level= min level.

Estelyen's picture

LEAD tag

Is it possible to specify multiple QIDs after the LEAD tag? If so, how does this check work? Will the step complete if the player has completed ALL of the QIDs or if he has completed ONE of them?

I'm now doing the final additions and corrections to my Firelands Invasion Guide and can begin testing shortly with an alt, however I've just noticed this problem: At the last great unlocking stage of the event, the player can choose any of three unlocking quests and I'd like the guide to give different instructions if one of them has already been turned in, which is the reason for my question. Also, I'm going to wait with its release until the final revisions of the daily module have been completed, as some steps in my guide don't yet work as intended; the reasons for those are on the TO DO list of the ever hard-working Ludovicus Maior ;)

Life isn't like a box of chocolates, it's more like a jar of jalapeños: What you do today might burn your a** tomorrow.


Ludovicus_Maior's picture

The Simple LEAD tag

The LEAD tag currently takes only a single QID.  It is implemented for the Leveling, Dailies and WorldEvents modules.

If I was going to implement it, as I think there are quests with multiple leadin quests, some mutually exclusive and others not, I would say that |LEAD|1;2| would complete the step if quest 1 or quest 2 were completed.

Does that make sense?

Estelyen's picture

How about using AND/OR in guide code?

Yes, that would make sense and also solve the problem I'm having with the guide at the moment^^

However, that makes me think: Wouldn't it make sense to generally add AND/OR conditionals instead of the simple semicolon? Not only on the LEAD tag but for other things as well, maybe even for tags rather than parameters; that would give guide authors a lot more freedom, because I don't think we've seen the end of Blizzards additions to questing mechanics yet :P I know the addon is undegoing a lot of work at the moment, and since I don't know jack about lua in general and WOW-Addons in particular, I don't even know if this idea would be possible to implement, just wanted to make a suggestion ;)

Life isn't like a box of chocolates, it's more like a jar of jalapeños: What you do today might burn your a** tomorrow.


Ludovicus_Maior's picture

Boolean Logic

Yeah, it looks like Tepes has already sussed out that AND/OR logic would be necessary for some cases already.

I will implement simple OR logic to start with and then once we are down to a single parser, expand it to handle boolean logic.

OK.  For starters, I'll do the OR thing for the Dalies guide and get that out for you.

Ludovicus_Maior's picture

REP Tag broken in release 2.1.5, or did blizzard break something

Well, I'm not sure when it broke.

But the REP tags in Shadowmoon were not working right and I tracked it down to the names not matching.  The guide was looking for "Scryers" when the name of the faction was "The Scryers".  So here I am getting random quests for Aldor being a good scryer.

I have a fix and it will be in the next release.

Estelyen's picture

Did it get fixed? Because I

Did it get fixed? Because I would like to know how to use the REP tag, this page doesn't explain that one :( I take it that the REP tag refers to reputation. If there is a quest in the guide I'm writing that requires friendly reputation, should I do it like this?

A Quest Name|QID|12345|REP|FactionName Friendly|

Or do I have to use some numerical value? Or a ":" after the factions name like in the QO tag? I'm confused :P

Life isn't like a box of chocolates, it's more like a jar of jalapeños: What you do today might burn your a** tomorrow.



A Quest Name|QID|12345|REP|FactionName;FactionID;Friendly| (ex. Scryers;934;Friendly)

Ludovicus_Maior's picture

REP Redux

FactionName;FactionID;Friendly will be good only if you are Friendly with them.  If you are Revered, it will fail.

FactionName;FactionID;Friendly-Revered will be good if your rep is in the stated range.

FactionName;FactionID will use the default range neutral-exalted.

If your rep with the faction is hostile or hated and the step asks for neutral or better, it is marked as skipped.  A bug fix for today that fixes step counts in guides like Netherstorm with Scryers/Aldor quest lines.

Estelyen's picture

Wow, that was a quick

Wow, that was a quick response... Thank you very much!^^ I didn't even know there was such a thing as a FactionID, I just looked and I can get those from WoWhead as well. Someone should really add the REP tag to this site, it's missing ;)

Life isn't like a box of chocolates, it's more like a jar of jalapeños: What you do today might burn your a** tomorrow.



Steps with QO tags dont work for me (I'm using the german client)The quest objective isn't showing and there is no auto-complete.

Ludovicus_Maior's picture

QO Localization or Warum muss das Leben so kompliziert?

I guess that you get messages in the UI saying:

Sprecht mit Nomarch Teneth: 1/1

instead of:

Speak with Nomarch Teneth: 1/1

We are doing a string match of the QO string against the return value of  GetQuestLogLeaderBoard(), which returns locale variable strings.   But since clearly indicates a method to determine if an objective is completed and what the objective is based on the index and the quest ID, we could fix this by changing the QO tag to take either a string (in which case it has the current behaviour, or an objective ID (#1, #2).  Now the problem with doing by OID is that if blizzard alters the order, then our coordinates would be messed up.  But then we could get localization for multi-step quests for free.

Need to think some more about this.


using the OID sounds good to

using the OID sounds good to me

I don't think blizzard will alter the order... why should they? maybe when the quest and its objectives are changed themself, but then we would need to update this part of the guide anyway

Ludovicus_Maior's picture

Scraping OIDs

Yeah, I think I can write a program to query Wowhead's quest DB and map the text in the QO tags back to OIDs, assuming they listed them in the right order.   It might cover more than 90% of the cases. 

Editing the guides automagically will be a trick.

Gender specific quests?

The wow-pro addon has support in its syntax as shown above for quests that require a given Class or Race, however there are some quests where the version of the quest you are given is dependent upon the gender of your character.

An example of this is the new Goblin starting zone where you will be given different quests from your boyfriend/girlfriend based on your characters gender.

Could the addon be altered therefore to allow for Gender to be added along with Class and Race to specify if the quest should be show in the guide for a player?

Crackerhead22's picture

Hopefully with in the next

Hopefully with in the next update or two, that will be included.  In fact, the souce code page for the Goblin areas has the code in it waiting.

Crackerhead22's picture

Ok, so how am I supposed to

Ok, so how am I supposed to use the Profession tag? I used it like this |P|Cooking 350|; but would get a few errors.

Message: Interface\AddOns\WoWPro\WoWPro_Broker.lua:164: Usage: GetProfessionSkillLine(index)
Time: 01/09/11 07:16:37
Count: 1
Stack: [C]: in function `GetProfessionInfo'
Interface\AddOns\WoWPro\WoWPro_Broker.lua:164: in function `NextStep'
Interface\AddOns\WoWPro\WoWPro_Broker.lua:63: in function `UpdateGuide'
...ce\AddOns\WoWPro_Leveling\WoWPro_Leveling_Parser.lua:288: in function `LoadGuide'
Interface\AddOns\WoWPro\WoWPro_Broker.lua:40: in function `LoadGuide'
Interface\AddOns\WoWPro\WoWPro.lua:146: in function
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:543: in function `EnableAddon'
Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:635: in function
[C]: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:242: in function `UIParentLoadAddOn'
Interface\FrameXML\UIParent.lua:265: in function `CombatLog_LoadUI'
Interface\FrameXML\UIParent.lua:519: in function


Message: Interface\AddOns\WoWPro\WoWPro_Broker.lua:164: Usage: GetProfessionSkillLine(index)
Time: 01/09/11 07:16:38
Count: 1
Stack: [C]: in function `GetProfessionInfo'
Interface\AddOns\WoWPro\WoWPro_Broker.lua:164: in function `NextStep'
Interface\AddOns\WoWPro\WoWPro_Broker.lua:63: in function `UpdateGuide'
...ce\AddOns\WoWPro_Leveling\WoWPro_Leveling_Parser.lua:566: in function `EventHandler'
Interface\AddOns\WoWPro\WoWPro.lua:142: in function

Locals: (*temporary) = nil

Message: Interface\AddOns\WoWPro\WoWPro_Broker.lua:164: Usage: GetProfessionSkillLine(index)
Time: 01/09/11 07:16:38
Count: 1
Stack: [C]: in function `GetProfessionInfo'
Interface\AddOns\WoWPro\WoWPro_Broker.lua:164: in function `NextStep'
Interface\AddOns\WoWPro\WoWPro_Broker.lua:243: in function `NextStepNotSticky'
Interface\AddOns\WoWPro\WoWPro_Mapping.lua:282: in function `MapPoint'
...ce\AddOns\WoWPro_Leveling\WoWPro_Leveling_Parser.lua:744: in function `AutoCompleteQuestUpdate'
...ce\AddOns\WoWPro_Leveling\WoWPro_Leveling_Parser.lua:586: in function `EventHandler'
Interface\AddOns\WoWPro\WoWPro.lua:142: in function

Locals: (*temporary) = nil

Jiyambi's picture

Ewwww, gross. I think you've

Ewwww, gross. I think you've used it correctly, I'll look into the error. Sorry about that!

Crackerhead22's picture

Meh, it happens.  I was going

Meh, it happens.  I was going to use it for the cooking quest in Northrend.

out not our

|RANK|3| Really our of the way

Should read out