by Jiyambi
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
- Downloading the Recorder
- Creating a New Guide
- Editing an Existing Guide
- Recording
- Saving Your Work
- Working With the File
- Submitting Your Work
- Frequently Asked Questions
- 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
- The most current guides
- WoW-Pro Recorder
Unzip the file into your beta addons folder. You should have eight separate folders:
- WoWPro
- WoWPro_Achievements
- WoWPro_Dailies
- WoWPro_Leveling
- WoWPro_Profession
- WoWPro_Recorder (disabled by default)
- WoWPro_Utilities (not an addon)
- WoWPro_WorldEvents
Everything should be ready to go – fire up the client and log in!
By default WoWPro_Recorder is disabled, so you need to enable it in your addons list for each character you will use it on.
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.
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.
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
- Accept steps:
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!
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!
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.
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!
It’s because the achor frameIt’s because the achor frame doesn’t exist anymore. It’s just something simple I haven’t got around to fixing yet – you can remove the line or change AnchorFrame to MainFrame and you should be okay.Sorry about that, I’ll try to get around to updating the recorder soon, it needs an overhaul for the modules anyway!
Ok, the problem seems to beOk, the problem seems to be when the Width is set to less than or equal to 250. I checked it, setting it to 250 or less causes an error. If it is less than 250, it will re-size it to 250, and still causes the error.
Also, it will start working if the width is set to greater than 250 (record, etc).
From what I can tell the offending line is in the WoWPro_Recorder_frames.lua, line 1344 with
[code]WoWPro.AnchorFrame:SetWidth(250)[/code]
I should also mention thatI should also mention that making a new guide will not save it seems, nor will it pick up any quests.
Recorder with 2.1.2Getting the following error.
[hr]
Message: …ceAddOnsWoWPro_RecorderWoWPro_Recorder_Frames.lua:1344: attempt to index field ‘AnchorFrame’ (a nil value)
Time: 01/16/11 21:41:54
Count: 1
Stack: …ceAddOnsWoWPro_RecorderWoWPro_Recorder_Frames.lua:1344: in function `CustomizeFrames’
InterfaceAddOnsWoWPro_RecorderWoWPro_Recorder.lua:32: in function
(tail call): ?
[C]: ?
[string “safecall Dispatcher[1]”]:9: in function
(tail call): ?
InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:543: in function
(tail call): ?
InterfaceAddOnsWoWProWoWPro.lua:118: in function
(tail call): ?
[C]: ?
[string “safecall Dispatcher[1]”]:9: in function
(tail call): ?
InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:543: in function `EnableAddon’
InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:635: in function
[C]: in function `LoadAddOn’
InterfaceFrameXMLUIParent.lua:242: in function `UIParentLoadAddOn’
InterfaceFrameXMLUIParent.lua:265: in function `CombatLog_LoadUI’
InterfaceFrameXMLUIParent.lua:519: in function
Locals:
I was having some strangeI was having some strange issues with the recorder when I upgraded the addon to 2.1.1. No errors that I remember, but a lot of times, it wouldn’t recognize the quest being accepted, completed, turned-in. Also, I was having an issue where all the quests steps were having the same QID.
I like it! And I’m glad youI like it! And I’m glad you like the new repair step 🙂 I’ll add the new step type and submit it later tonight.
Small SuggestionI love the Repair/Restock option when adding a new step. I was wondering if it would be possible to add a Hearth to step?
For example: H hearthspot|QID|##|N|Hearth back to Lakeshire Inn, or run/fly if your hearth is on cooldown.|
It’s available from theIt’s available from the “Community Page” but I might make that a bit more accessible as well. Thanks for the tip 🙂
Nevermind–I had to googleNevermind–I had to google this, as I couldn’t find it linked anywhere from your main wow-pro addon pages, aside from the little “More content by this user” box on the right.https://www.wow-pro.com/node/3192#optionalMay I suggest publicizing that fantastic little page a little more? 😀
Optional steps?I haven’t written a wow-pro guide since you guys were porting all of your paper guides to TourGuide format. Something I liked about that format was the ability to make a step optional. That is, to display a step if (and only if) you had the associated quest. For example, I’m doing a Hillsbrad guide and would like to mark optional turn-ins for the breadcrumbs that lead there at the beginning–but only if the user already has those quests.Can we still do that here? I see no mention of how, but it’s entirely possible that I’m simply missing something or not reading the correct guide-writing guide. :)On an unrelated note, when I’m in the process of recording my guide, the guide display shows only blank steps rather than anything I’ve recorded. Nothing I can’t work around, though.
I think I have fixed this,I think I have fixed this, I’ll be updating it tonight.
Ack! No line spaces! Sorry!Ack! No line spaces! Sorry!
Another Recorder ErrorThis happen when I completed the quest after I added a loot tag. Date: 2010-12-01 18:29:44ID: 1Error occured in: GlobalCount: 1Message: ..AddOnsWoWPro_RecorderWoWPro_Recorder.lua line 355: attempt to compare string with booleanDebug: [C]: ? WoWPro_RecorderWoWPro_Recorder.lua:355: SaveGuide() WoWPro_RecorderWoWPro_Recorder.lua:296: AddStep() WoWPro_RecorderWoWPro_Recorder.lua:213: WoWPro_RecorderWoWPro_Recorder.lua:92AddOns: Swatter, v5.9.4960 (WhackyWallaby) Ace3, v AucAdvanced, v5.9.4960 (WhackyWallaby) AucFilterBasic, v5.9.4960 (WhackyWallaby) AucFilterOutlier, v5.9.4960.2531 AucMatchUndercut, v5.9.4960.2531 AucScanData, v5.9.4960 (WhackyWallaby) AucStatHistogram, v5.9.4960 (WhackyWallaby) AucStatiLevel, v5.9.4960 (WhackyWallaby) AucStatPurchased, v5.9.4960 (WhackyWallaby) AucStatSales, v5.9.4960.2842 AucStatSimple, v5.9.4960 (WhackyWallaby) AucStatStdDev, v5.9.4960 (WhackyWallaby) AucStatWOWEcon, v5.9.4960.2530 AucUtilAHWindowControl, v5.9.4960.3311 AucUtilAppraiser, v5.9.4960.2530 AucUtilAskPrice, v5.9.4960.3175 AucUtilAutoMagic, v5.9.4960.3142 AucUtilCompactUI, v5.9.4960.2530 AucUtilEasyBuyout, v5.9.4960.3583 AucUtilFixAH, v5.9.4960 (WhackyWallaby) AucUtilGlypher, v5.9.4960.2545 AucUtilItemSuggest, v5.9.4960.3108 AucUtilPriceLevel, v5.9.4960.2545 AucUtilScanButton, v5.9.4960.2530 AucUtilScanFinish, v5.9.4960.2530 AucUtilScanProgress, v5.9.4960.2530 AucUtilScanStart, v5.9.4960.4819 AucUtilSearchUI, v5.9.4960.3655 AucUtilSimpleAuction, v5.9.4960.4546 AucUtilVendMarkup, v5.9.4960.2530 Babylonian, v5.1.DEV.130 Bagnon, v2.14.0 BagnonConfig, v BagnonForever, v1.1.2 BagnonTooltips, v BeanCounter, v5.9.4960 (WhackyWallaby) Configator, v5.1.DEV.282 DebugLib, v5.1.DEV.275 Enchantrix, v5.9.4960 (WhackyWallaby) EnchantrixBarker, v5.9.4960 (WhackyWallaby) Informant, v5.9.4960 (WhackyWallaby) RatingBuster, v SlideBar, v5.9.4960 (WhackyWallaby) Stubby, v5.9.4960 (WhackyWallaby) Titan, v5.0.1.40000 – Revision 485 TitanBag, v5.0.1.40000 TitanClock, v5.0.1.40000 TitanCurrency, v0.4 TitanDurability, v1.20 TitanGold, v5.0.1.40000 TitanLocation, v5.0.1.40000 TitanLootType, v5.0.1.40000 TitanPerformance, v5.0.1.40000 TitanRepair, v5.0.1.40000 TitanVolume, v5.0.1.40000 TitanXP, v5.0.1.40000 TomTom, vv40000-1.0.4 WoWPro, v2.0.4 WoWProLeveling, v2.0.4 WoWProRecorder, v2.0.1 BlizRuntimeLib_enUS v4.0.3.40000 <us> (ck=7ed)
Cool! Thanks! AfterCool! Thanks! After re-logging, some of what I recorded is there, so I didn’t lose everything. lol. I does seem to randomly add in a certain quest tho. Called Death’s Door. Haven’t figured that one out yet. 🙂 It really didn’t want me to add the Hearth to step, lol. But that was after the error, so maybe that’s why.
Thanks Bits. This appears toThanks Bits. This appears to be due to part of the code for writing L tags, actually. I think I’ve fixed it.
Error when trying to registerDate: 2010-12-01 15:05:39
ID: 1
Error occured in: Global
Count: 1
Message: ..AddOnsWoWPro_RecorderWoWPro_Recorder.lua line 355:
attempt to compare string with boolean
Debug:
(tail call): ?
WoWPro_RecorderWoWPro_Recorder.lua:355: SaveGuide()
WoWPro_RecorderWoWPro_Recorder.lua:296: AddStep()
…ceAddOnsWoWPro_RecorderWoWPro_Recorder_Frames.lua:511:
…ceAddOnsWoWPro_RecorderWoWPro_Recorder_Frames.lua:510
(tail call): ?
[C]: ?
[string “safecall Dispatcher[3]”]:9:
[string “safecall Dispatcher[3]”]:5
(tail call): ?
…nfig-3.0AceConfigDialog-3.0AceConfigDialog-3.0.lua:797:
…nfig-3.0AceConfigDialog-3.0AceConfigDialog-3.0.lua:612
(tail call): ?
[C]: ?
[string “safecall Dispatcher[4]”]:9:
[string “safecall Dispatcher[4]”]:5
(tail call): ?
Ace3AceGUI-3.0AceGUI-3.0.lua:314: Fire()
…dOnsAce3AceGUI-3.0widgetsAceGUIWidget-Button.lua:21:
…dOnsAce3AceGUI-3.0widgetsAceGUIWidget-Button.lua:19
AddOns:
Swatter, v5.9.4960 (WhackyWallaby)
Ace3, v
AucAdvanced, v5.9.4960 (WhackyWallaby)
AucFilterBasic, v5.9.4960 (WhackyWallaby)
AucFilterOutlier, v5.9.4960.2531
AucMatchUndercut, v5.9.4960.2531
AucScanData, v5.9.4960 (WhackyWallaby)
AucStatHistogram, v5.9.4960 (WhackyWallaby)
AucStatiLevel, v5.9.4960 (WhackyWallaby)
AucStatPurchased, v5.9.4960 (WhackyWallaby)
AucStatSales, v5.9.4960.2842
AucStatSimple, v5.9.4960 (WhackyWallaby)
AucStatStdDev, v5.9.4960 (WhackyWallaby)
AucStatWOWEcon, v5.9.4960.2530
AucUtilAHWindowControl, v5.9.4960.3311
AucUtilAppraiser, v5.9.4960.2530
AucUtilAskPrice, v5.9.4960.3175
AucUtilAutoMagic, v5.9.4960.3142
AucUtilCompactUI, v5.9.4960.2530
AucUtilEasyBuyout, v5.9.4960.3583
AucUtilFixAH, v5.9.4960 (WhackyWallaby)
AucUtilGlypher, v5.9.4960.2545
AucUtilItemSuggest, v5.9.4960.3108
AucUtilPriceLevel, v5.9.4960.2545
AucUtilScanButton, v5.9.4960.2530
AucUtilScanFinish, v5.9.4960.2530
AucUtilScanProgress, v5.9.4960.2530
AucUtilScanStart, v5.9.4960.4819
AucUtilSearchUI, v5.9.4960.3655
AucUtilSimpleAuction, v5.9.4960.4546
AucUtilVendMarkup, v5.9.4960.2530
Babylonian, v5.1.DEV.130
Bagnon, v2.14.0
BagnonConfig, v
BagnonForever, v1.1.2
BagnonTooltips, v
BeanCounter, v5.9.4960 (WhackyWallaby)
Configator, v5.1.DEV.282
DebugLib, v5.1.DEV.275
Enchantrix, v5.9.4960 (WhackyWallaby)
EnchantrixBarker, v5.9.4960 (WhackyWallaby)
Informant, v5.9.4960 (WhackyWallaby)
RatingBuster, v
SlideBar, v5.9.4960 (WhackyWallaby)
Stubby, v5.9.4960 (WhackyWallaby)
Titan, v5.0.1.40000 – Revision 485
TitanBag, v5.0.1.40000
TitanClock, v5.0.1.40000
TitanCurrency, v0.4
TitanDurability, v1.20
TitanGold, v5.0.1.40000
TitanLocation, v5.0.1.40000
TitanLootType, v5.0.1.40000
TitanPerformance, v5.0.1.40000
TitanRepair, v5.0.1.40000
TitanVolume, v5.0.1.40000
TitanXP, v5.0.1.40000
TomTom, vv40000-1.0.4
WoWPro, v2.0.4
WoWProLeveling, v2.0.4
WoWProRecorder, v2.0.1
BlizRuntimeLib_enUS v4.0.3.40000
(ck=7ed)
I can’t save! Eek! When I hitI can’t save! Eek! When I hit save on the recorder, nothing happens! What have I done!?! The horror….the hoooorrrrroooorrrrr.
Ok, the erros should be fixedOk, the erros should be fixed on my git forked version. But I can’t reproduce this: “When using the |CC| tag, and having multiple cords, it does not seem to
always auto-complete. Most of the time it will, but I have noticed that
if I unchecked the step it will not auto-complete when I go to the
final cord.” Can you clarify that?
Yes, but we would then beYes, but we would then be doing things based on quest names, rather than IDs. This would be good for these very special cases, but keep in mind this breaks if the user has a different language client.
Still, this is definitely worth looking into!
I think so. I believe there’sI think so. I believe there’s a open issue on github about that, but I never got to it.
Would it be able to grab itWould it be able to grab it from the chat log? I believe it does show on there.
Bwahahahaha! I am the karmaBwahahahaha! I am the karma goddess! I giveth and I can taketh away!
No, I wouldn’t claim too…No, I wouldn’t claim too… you should know now I am testing the creator’s limits to when she starts deducting my Karma points 😀 lol
Hush. You knew exactly whatHush. You knew exactly what you were talking about, I just wanted to clarify that hopefully 1 was/will be fixed and 2 was intended behavior. You can’t be expected to know more than the developer about her own creation 😉
Oh I went there…There I go pretending I knew what I was talking about and you had to kill my ego 😛 Thanks Sir Max or Un’goro 😛
#1 is fixed in the most#1 is fixed in the most recent version of the recorder, I beleive. It’s fixed in the github version anyways.
#2 sounds like it might be the issue. But it is in fact intended behavior, so that you can record things at an earlier place in the guide if you so desire!
I actually usually list it asI actually usually list it as whatever type of question/exclamation mark shows above the NPCs head, so the user gets a visual cue. But, it really doesn’t matter – either way it won’t auto-complete, sadly, because the quest never touches the quest log. I’m hoping to add support for these types of quests at a later time, but for now as Gylin said, you’ll just need to leave a note for the user.
Two thingsTwo things can cause this…1. If you /reload your UI or log out then in, after reordering steps in the recorder (move up move down) without hitting the save process, it will revert back to it's original ordering.2. If you for some reason highlight a step further up your guide, it will start placing steps after that particular step in the guide, as opposed to the end of it.
Recorder not saving in the order…Recorder is not saving in the order of the steps that I am completing them. It is making so I have to cut and paste lines instead of blocks. Does anyone have any ideas why this might be happening?
Thank you.Thank you.
Turn InI believe it is done with a Turn in step. Just put a note tag in to let them know about this.
With quests that complete without an acceptWith quests that complete without an accept, for example “The Egg Lives On”, to try and get them to auto-complete. Should I have the tag as a turnin, or as an accept?
Please, don’t feel bad! Also,Please, don’t feel bad! Also, even if CS works, they have different functionalities, so it would be just a workaround fix.
Yeah, I’m looking into thisYeah, I’m looking into this and also glad. Thanks for the detailed bug reports. 🙂
The errors are easy to fix, I will do that tomorrow. But why it’s not autocompleting properly, I’ll have to do some tests ingame on my own.
At some point soon, I’ll probably have to change all that code anyway, along with our own tracking system, instead of TomTom.
I just feel bad that I keepI just feel bad that I keep breaking the code. XD
I’ll give the CS tag a try and see.
No it does not matter whereNo it does not matter where in the line that the CC tag occurs.
I am not familiar with the code that handles these tags (Silvann did that code, and I think he’s looking into this) but I’m wondering if for multiple coordinates you possibly need to use CS tags instead.
I AM very glad we are testing this feature out, since it hasn’t really gotten much attention previously.
Hate to say it but I foundHate to say it but I found another one. Not sure if it is related to this one or not, but here goes.
When using the |CC| tag, and having multiple cords, it does not seem to always auto-complete. Most of the time it will, but I have noticed that if I unchecked the step it will not auto-complete when I go to the final cord. Out of curiosity, does it matter where the |CC| tag is on the line?
Also if I log in with the step with the multiple cords, I get quite a few errors. For the sake of not having a huge wall of text, I archived them and uploaded them. http://www.filefront.com/17578043/CC-tag-errrors.rar/
Thanks, I’ll take a look atThanks, I’ll take a look at this.
|CC| tag errorOk, when choosing a guide, and there is a R tag that has a |CC| as well, and I am in a different zone then what the |Z| has. When I reach that step, I get the following error.
Message: InterfaceAddOnsWoWProWoWPro_Mapping.lua:387: attempt to perform arithmetic on local ‘iactual’ (a nil value)
Time: 11/28/10 18:48:41
Count: 2
Stack: InterfaceAddOnsWoWProWoWPro_Mapping.lua:387: in function `MapPoint’
…ceAddOnsWoWPro_LevelingWoWPro_Leveling_Parser.lua:388: in function
Locals: self = {
note = {
}
index = {
}
zone = {
}
CreateGuideWindowScrollbar = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:533
modules = {
}
target = {
}
CreateHeading = defined @InterfaceAddOnsWoWProWoWPro_Widgets.lua:100
optional = {
}
Tags = {
}
MapPoint = defined @InterfaceAddOnsWoWProWoWPro_Mapping.lua:264
Titlebar = Titlebar {
}
CreateSkipStepsDialog = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:653
UpdateGuide = defined @InterfaceAddOnsWoWProWoWPro_Broker.lua:48
SetDefaults = defined @InterfaceAddOnsWoWProWoWPro_Config.lua:14
Leveling = {
}
IsEnabled = defined @InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:467
RegisterTags = defined @InterfaceAddOnsWoWProWoWPro.lua:169
NextStep = defined @InterfaceAddOnsWoWProWoWPro_Broker.lua:133
UnregisterEvents = defined @InterfaceAddOnsWoWProWoWPro.lua:190
ActiveStickyCount = 0
CreateMiniMapButton = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:629
FramesLoaded = true
RegisterEvents = defined @InterfaceAddOnsWoWProWoWPro.lua:180
StickyFrame = WoWPro.StickyFrame {
}
ResetMainFramePosition = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:15
OnEnable = defined @InterfaceAddOnsWoWProWoWPro.lua:90
Version = “2.0.2”
prof = {
}
PaddingSet = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:74
missingQuest = false
DebugMode = false
TitleText = {
}
CreateMouseNotes = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:599
OnInitialize = defined @InterfaceAddOnsWoWProWoWPro.lua:81
NewModule = defined @InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:256
NextGuideDialog = Guide Completed {
}
AnchorSet = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:268
RowSet = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:325
FauxItemButton = WoWPro_FauxItemButton {
}
GetName = defined @InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:300
name = “WoWPro”
noncombat = {
}
Disable = defined @InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:330
action = {
}
CreateTargetButton = defined @InterfaceAddOnsWoWProWoWPro_Widgets.lua:81
rows = {
}
Print = defined @InterfaceAddOnsWoWProWoWPro.lua:23
DragSet = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:46
leadin = {
}
CreateMainFrame = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:380
RowColorSet = defined @InterfaceAddOnsWoWProWoWPro_Frames.lua:129
NextStepNotSticky = defined @InterfaceAddOnsWoWProWoWPro_Broker.lua:237
QuestLog = {
}
SkipStepsCancelButton = Cancel {
}
CreateBG = defined @InterfaceAddOnsWoWProWoWPro_Widgets.lua:117
SetDefaultModuleLibraries = defined @InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:383
GuideFrame = WoWPro.GuideFrame {
}
CompleteStep = defined @InterfaceAddOnsWoWProWoWPro_Broker.lua:252
step = {
}
LoadNilGuide = defined @InterfaceAddOnsWoWProWoWPro_NilGuide.lua:5
baseName = “WoWPro”
IterateEmbeds = defined @InterfaceAddOnsAce3AceAddon-3.0AceAddon-3.0.lua:458
level = {
}
CreateCheck = defined @InterfaceAddOnsWoWProWoWPro_Widgets.lua:5
map = {
}
CreateScr
Waypoint Complete/Series errorUsing WoWPro addon version 2.0.3.
If I forget to make the step Waypoint Complete/Series, and then go back into edit the step, I get the error below. Works fine if done from scratch, can edit the cords and all that fine. The error only happens when editing an existing step. Also, when wanting to make an existing step no long a Waypoint Complete/Series, the option will not check itself off.
Message: InterfaceAddOnsWoWProWoWPro_Broker.lua:161: attempt to index local ‘prof’ (a string value)
Time: 11/28/10 15:17:15
Count: 7
Stack: InterfaceAddOnsWoWProWoWPro_Broker.lua:161: in function `NextStep’
InterfaceAddOnsWoWProWoWPro_Broker.lua:63: in function `UpdateGuide’
…ceAddOnsWoWPro_RecorderWoWPro_Recorder_Frames.lua:834: in function
(tail call): ?
[C]: ?
[string “safecall Dispatcher[2]”]:9: in function
(tail call): ?
…nfig-3.0AceConfigDialog-3.0AceConfigDialog-3.0.lua:798: in function
(tail call): ?
[C]: ?
[string “safecall Dispatcher[3]”]:9: in function
(tail call): ?
InterfaceAddOnsAce3AceGUI-3.0AceGUI-3.0.lua:314: in function `Fire’
…nsAce3AceGUI-3.0widgetsAceGUIWidget-CheckBox.lua:68: in function
Locals:
While I have no idea why thatWhile I have no idea why that happened at that particular time, I do see where I totally effed up the profession section, which is causing that error to be thrown. Oops! Fixed, will update ASAP.
Thanks for the report! I’llThanks for the report! I’ll fix it ASAP!
Changing Action Type ErrorUsing WoWPro addon version 2.0.3
Ok, when trying to edit a step that has a Complete tag to make it into a Run to tag. I get the following error:
Message: InterfaceAddOnsWoWProWoWPro_Broker.lua:161: attempt to index local ‘prof’ (a string value)
Time: 11/28/10 15:25:14
Count: 4
Stack: InterfaceAddOnsWoWProWoWPro_Broker.lua:161: in function `NextStep’
InterfaceAddOnsWoWProWoWPro_Broker.lua:63: in function `UpdateGuide’
…ceAddOnsWoWPro_RecorderWoWPro_Recorder_Frames.lua:641: in function
(tail call): ?
[C]: ?
[string “safecall Dispatcher[2]”]:9: in function
(tail call): ?
…nfig-3.0AceConfigDialog-3.0AceConfigDialog-3.0.lua:798: in function
(tail call): ?
[C]: ?
[string “safecall Dispatcher[3]”]:9: in function
(tail call): ?
InterfaceAddOnsAce3AceGUI-3.0AceGUI-3.0.lua:314: in function `Fire’
…otLibsAceGUI-3.0widgetsAceGUIWidget-DropDown.lua:439: in function
(tail call): ?
[C]: ?
[string “safecall Dispatcher[3]”]:9: in function
(tail call): ?
InterfaceAddOnsAce3AceGUI-3.0AceGUI-3.0.lua:314: in function `Fire’
…3AceGUI-3.0widgetsAceGUIWidget-DropDown-Items.lua:345: in function
Locals:
I’m liking thisI’m liking this AddOn already after one try of about 20 minutes. Ran through the Undead starting zone up to level 5 to test it. Can totally see why this is useful not only for the AddOn guides but for the text guides as well.[br][br]Result after my first try (complete starting zone):[br][br]WoWPro.Leveling:RegisterGuide(‘UndeadGID’, ‘Tirisfal Glades’, ‘Manovan’, ‘1’, ’12’, ‘NextGID’, ‘Horde’, function()
return [[
A Fresh out of the Grave|QID|24959|M|29.36,70.96|N|From Agatha.|
T Fresh out of the Grave|QID|24959|M|30.04,71.23|N|To Undertaker Mordo.|
A The Shadow Grave|QID|28608|M|30.04,71.23|N|From Undertaker Mordo.|
C The Shadow Grave|QID|28608|M|29.68,72.04|
T The Shadow Grave|QID|28608|M|30.11,71.39|N|To Undertaker Mordo.|
A Those That Couldn’t Be Saved|QID|26799|M|30.11,71.39|N|From Undertaker Mordo.|
A The Wakening|QID|24960|M|30.62,71.46|N|From Caretaker Caice.|
C Those That Couldn’t Be Saved|QID|26799|M|30.26,70.44|
C The Wakening|QID|24960|M|30.75,69.16|
L Level 2|QID|24960|LVL|2|N|You should be around level 2 by this point.|
T Those That Couldn’t Be Saved|QID|26799|M|30.12,71.23|N|To Undertaker Mordo.|
T The Wakening|QID|24960|M|30.61,71.41|N|To Caretaker Caice.|
A Beyond the Graves|QID|25089|M|30.61,71.41|N|From Caretaker Caice.|
T Beyond the Graves|QID|25089|M|31.70,65.69|N|To Deathguard Saltain.|
A Recruitment|QID|26800|M|31.70,65.69|N|From Deathguard Saltain.|
A Scourge on our Perimeter|QID|26801|M|30.93,66.21|N|From Shadow Priest Sarvis.|
C Scourge on our Perimeter|QID|26801|M|32.12,62.31|
C Recruitment|QID|26800|M|32.79,63.23|
T Recruitment|QID|26800|M|31.65,65.48|N|To Deathguard Saltain.|
L Level 3|QID|26801|LVL|3|N|You should be around level 3 by this point.|
T Scourge on our Perimeter|QID|26801|M|30.94,66.21|N|To Shadow Priest Sarvis.|
A Trail-Worn Scroll|QID|24962|M|30.94,66.21|N|From Shadow Priest Sarvis.|
A The Truth of the Grave|QID|24961|M|30.91,66.18|N|From Novice Elreth.|
T Trail-Worn Scroll|QID|24962|M|31.52,65.64|N|To Xavier the Huntsman.|
A The Thrill of the Hunt|QID|24964|M|31.52,65.64|N|From Xavier the Huntsman.|
C The Thrill of the Hunt|QID|24964|M|31.67,66.25|
T The Thrill of the Hunt|QID|24964|M|31.51,65.66|N|To Xavier the Huntsman.|
C The Truth of the Grave|QID|24961|M|32.67,65.79|
T The Truth of the Grave|QID|24961|M|30.93,66.12|N|To Novice Elreth.|
A The Executor In the Field|QID|28672|M|30.93,66.12|N|From Novice Elreth.|
T The Executor In the Field|QID|28672|M|32.90,61.14|N|To Executor Arren.|
A The Damned|QID|26802|M|32.90,61.14|N|From Executor Arren.|
C The Damned|QID|26802|M|35.45,57.08|
L Level 4|QID|26802|LVL|4|N|You should be around level 4 by this point.|
T The Damned|QID|26802|M|33.04,61.06|N|To Executor Arren.|
A Night Web’s Hollow|QID|24973|M|33.04,61.06|N|From Executor Arren.|
C Night Web’s Hollow|QID|24973|M|25.74,59.43|
T Night Web’s Hollow|QID|24973|M|32.91,61.12|N|To Executor Arren.|
A No Better Than the Zombies|QID|24970|M|32.91,61.12|N|From Executor Arren.|
T No Better Than the Zombies|QID|24970|M|35.68,62.28|N|To Darnell.|
A Assault on the Rotbrain Encampment|QID|24971|M|35.68,62.28|N|From Darnell.|
C Assault on the Rotbrain Encampment|QID|24971|M|36.24,67.90|
L Level 5|QID|24971|LVL|5|N|You should be around level 5 by this point.|
T Assault on the Rotbrain Encampment|QID|24971|M|30.93,66.20|N|To Shadow Priest Sarvis.|
A Vital Intelligence|QID|24972|M|30.93,66.20|N|From Shadow Priest Sarvis.|
Somehow I managed to fix itSomehow I managed to fix it with a simple reboot. Must have been a temporary bug.
Hmm, make sure you have bothHmm, make sure you have both WoWPro and WoWPro Leveling modules enabled/selected, along with the Recorder, when you log in with a character. Other than that, I have no idea what could it be. :/
I downloaded it from threeI downloaded it from three different sources. 1. This thread. 2. wkjezz’s link below. 3. Jiyambi’s link below. I had the core version installed and active when I tried them.
Where did you download itWhere did you download it from? If it’s from wkjezz‘s link below, then also install the core and leveling versions:https://github.com/downloads/Jiyambi/WoW-Pro-Guides/WoWPro%20v2.0.1.zip
ConfusionI downloaded the 2.0.2 version but ended up very confused. This is why:[br][br]http://img703.imageshack.us/img703/9716/errorki0.jpg[br][br]First of all: the Lua error and second of all: there are only three buttons next to the recorder.
You need to…I was having the same issue, but Jiyambi did an update for me the other day. The updated recorder only file can be downloaded at:
http://cloud.github.com/downloads/Jiyambi/WoW-Pro-Guides/WoWPro%20Recorder%20v2.0.2.zip
This is ONLY the recorder, not the core addon.
Before installing this, you might want to make a backup to your current recorder’s saved variables LUA file found in your game directory’s WTF folder
Example:
C:UsersPublicGamesWorld of WarcraftWTFAccount<>SavedVariablesWoWPro_Recorder.lua