General Bug Reporting

Jiyambi's picture





Known Bugs:

Before submitting a bug, please check this list to make sure you aren't repeating a submission!

Submit Your Bug:

When submitting your addon bug, you MUST include the following:

  • The version number of your WoW-Pro installation
  • Any error text that WoW provided when your bug happened
  • Information about the guide you were using when the bug happened, including:
    • Faction (Alliance/Horde)
    • Zone
    • What step you were on
  • As many details as possible about what you were doing when the bug occurred.

Including this information will help us troubleshoot and possibly get you a temporary solution to the bug, and get it fixed as quickly as possible!

Comments

Shadowmoon valley and Frostfridge ridge guides breaking

Using the current version, 7.0.3H from this site.At about 80-95% of the way through the zone, the guide just breaks on both of these zones. It stops updating steps, showing 1 step and not populating the other 4 I normally have showing, showing steps I've completed with checkmarks but not scrolling on. If I switch to a different guide, it works fine, when I switch back it shows the steps of the guide I had previously switched to, but with them checked off (for guides I haven't done yet).I've completely uninstalled the guide, deleted all lua's from the act saved variables and the character specific, and then reinstalled. Still broken at the same place.It seems to be related to garrison things. The shadowmoon valley broke just before the podlings section, when I was back in the garrison turning in to the building manager guy. The horde one broke on the quest turning timber into profit.

Ludovicus's picture

Re: Shadowmoon valley and Frostfridge ridge guides breaking

Can you post a debug log?

WowPro addon lua errors upon login

As soon as I log in to Wow I get three Lua errors referencing WoWPro_Broker. Pasted below are the three errors from WoW. I am using the latest version of the addon installed this morning from this website: 7.0.3H

1:

Message: Interface\AddOns\WoWPro\WoWPro_Broker.lua:937: Usage: GetBuildings(garrisonType)

Time: 07/23/16 09:17:44

Count: 1

Stack: Interface\AddOns\WoWPro\WoWPro_Broker.lua:937: in function `NextStep'

Interface\AddOns\WoWPro\WoWPro_Broker.lua:1092: in function `NextStepNotSticky'

Interface\AddOns\WoWPro\WoWPro_Mapping.lua:439: in function `MapPoint'

Interface\AddOns\WoWPro\WoWPro_Broker.lua:1151: in function `CompleteStep'

Interface\AddOns\WoWPro\WoWPro_Broker.lua:646: in function `NextStep'

Interface\AddOns\WoWPro\WoWPro_Broker.lua:1092: in function `NextStepNotSticky'

Interface\AddOns\WoWPro\WoWPro_Mapping.lua:439: in function `MapPoint'

Interface\AddOns\WoWPro\WoWPro_Events.lua:231: in function `AutoCompleteQuestUpdate'

Interface\AddOns\WoWPro\WoWPro_Parser.lua:722: in function <Interface\AddOns\WoWPro\WoWPro_Parser.lua:647>

(tail call): ?

[C]: ?

[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>

(tail call): ?

...Ons\ElkFactions\libs\AceBucket-3.0\AceBucket-3.0.lua:118: in function `func'

...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0.lua:55: in function <...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0.lua:48>

 

Locals: <none>

 

2:

Message: Interface\AddOns\WoWPro\WoWPro_Broker.lua:937: Usage: GetBuildings(garrisonType)

Time: 07/23/16 09:18:28

Count: 2

Stack: Interface\AddOns\WoWPro\WoWPro_Broker.lua:937: in function `NextStep'

Interface\AddOns\WoWPro\WoWPro_Broker.lua:1092: in function `NextStepNotSticky'

Interface\AddOns\WoWPro\WoWPro_Mapping.lua:439: in function `MapPoint'

Interface\AddOns\WoWPro\WoWPro_Events.lua:231: in function `AutoCompleteQuestUpdate'

Interface\AddOns\WoWPro\WoWPro_Events.lua:703: in function <Interface\AddOns\WoWPro\WoWPro_Events.lua:417>

 

Locals: k = 396

i = 1

GID = "EmmFrostfire"

skip = false

QID = "36137"

Name = "lumbermill"

ids = "40;41;138"

numList = 3

idHash = <table> {

 138 = true

 41 = true

 40 = true

}

QidMapReduce = <function> defined @Interface\AddOns\WoWPro\WoWPro_Broker.lua:12

Rep2IdAndClass = <table> {

 good friend = <table> {

 }

 best friend = <table> {

 }

 hated = <table> {

 }

 friend = <table> {

 }

 friendly = <table> {

 }

 stranger = <table> {

 }

 revered = <table> {

 }

 honored = <table> {

 }

 hostile = <table> {

 }

 buddy = <table> {

 }

 unfriendly = <table> {

 }

 neutral = <table> {

 }

 exalted = <table> {

 }

 acquaintance = <table> {

 }

}

3:Message: Interface\AddOns\WoWPro\WoWPro_Broker.lua:937: Usage: GetBuildings(garrisonType)Time: 07/23/16 09:17:44Count: 1Stack: Interface\AddOns\WoWPro\WoWPro_Broker.lua:937: in function `NextStep'Interface\AddOns\WoWPro\WoWPro_Broker.lua:289: in function <Interface\AddOns\WoWPro\WoWPro_Broker.lua:253>(tail call): ?[C]: ?[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>(tail call): ?...Ons\ElkFactions\libs\AceBucket-3.0\AceBucket-3.0.lua:118: in function `func'...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0.lua:55: in function <...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0.lua:48>Locals: <none>

Ludovicus's picture

Re: WowPro addon lua errors upon login

Fixed in the next release tomorrow.

Russian symbols did noot show

I installed 7.0.3Hit seems works fine but in quests log i have somthing like this

 

 

russian discription did not show correctly. I try change font for it, but it did not help (

Ludovicus's picture

Re: Russian symbols did noot show

I must confess I have never tried the client in Russian, since I only know latin alphabet languages.

But, I can clearly see that the ??? characters should be something else.

Let me see what I can do.  Did you ever use our Addon in Russian and succeed or is this your first time using it?

---Ludovic

Game won't load

Hey! Been using the addon for years, never had a problem, until about 3 weeks ago, and I couldn't get the game to load if I'm running the addon. It only does it with this computer, any other computer in my house that I play wow on it works. I even copied the interface folder from a computer I confirmed it worked with. I've disabled every addon except tomtom and wow-pro, and it still doesn't load, but I'm pretty sure it is wow-pro because the game loads with tomtom enabled. I've done everything I can think of short of a full reinstall, and thought I'd try you guys first, and maybe alert you to the problem. The addon (and all my other addons) are fully updated, the game is updated, all my drivers are updated. I'm using Windows 10.

Dalaran Map

I'm using version 6.2.4. When I went into Dalaran I got the error: Zone [4395] is not in Zone2MapID. Please Report! 

I'm currently trying to use The Storm Peaks guide for lvl 77-80. The TomTom arrow isn't showing up for inside of Dalaran.

Guide selector generates a bug

I'm just levelled up my rogue to 100 and wanted to start doing the professions. As soon as I hover over a guide bugsack reports an error.

I'm also using LUA V3 if that makes any difference.

53x WoWPro\WoWPro-6.2.3.lua:766: attempt to compare number with stringWoWPro\WoWPro-6.2.3.lua:766: in function `LevelColor'...ns\WowPro_Profession\WoWPro_Profession_GuideList.lua:60: in function `GuideTooltipInfo'WoWPro\WoWPro_GuideList.lua:345: in function <WoWPro\WoWPro_GuideList.lua:344>Locals:row = WoWPro_Profession_Guide_Row4 { 0 = <userdata> GID = "LudoShopBlacksmithing" Name = <unnamed> { } Progress = <unnamed> { } Author = <unnamed> { } module = <table> { }}tooltip = tooltip { 0 = <userdata>}guide = <table> { sequence = <function> defined @WowPro_Profession\Vendors\BlacksmithPlans.lua:24 name = "Blacksmithing Plans" zone = "Blacksmithing" guidetype = "Profession" author = "Ludovicus" endlevel = " " startlevel = "0"}(*temporary) = <function> defined =[C]:-1(*temporary) = GameTooltip { 0 = <userdata> updateTooltip = 0.14799999892712 comparing = false shoppingTooltips = <table> { } SetPetAction = <function> defined =[C]:-1 SetShapeshift = <function> defined =[C]:-1 hasMoney = 1 numMoneyFrames = 1 needsReset = true SetAction = <function> defined =[C]:-1}(*temporary) = "Category:"(*temporary) = nil(*temporary) = 1(*temporary) = 1(*temporary) = 1(*temporary) = <function> defined =[C]:-1

Ludovicus's picture

Re: Guide selector generates a bug

I'm pretty sure I fixed this bug in release 6.2.4, but I'll double check when the server comes back before I release.

Compatibility problem with Dugi Questing Essential?

I can't get the WoWPro addon to work with Dugi Questing Essential (http://www.curse.com/addons/wow/dugi-questing-essential), which is imo THE new major quest addon on the "market" today and replaced Carbonite for me. 

Dugi Questing Essential (DQE) has a TomTom Emulation function but when I use WoWPro it doesn't create any waypoint in DQE. The /way x y command does work with DQE though, so any idea why WoWPro isn't working with DQE? I'm using WoWPro 6.2.2A and I don't have any error message, the waypoints coords are just not "pushed" to DQE.

Thanks!

Sound Not Working for Completed Steps?

The Sound options for completed steps are not working. Is this a known bug or has it been removed from the addon and the options still exsist?

Ludovicus's picture

Re: Sound Not Working for Completed Steps?

Huh!   I did not know about that feature.  

Let me look into it.   Blizzard proibably changed the path to the sound and we never noticed the change.

 

PS:   Yup.  In 6.1 they changed from .wav files to .ogg files.   Fixing the pathnames makes it immediatly noisy.

Fixed in https://github.com/Jiyambi/WoW-Pro-Guides/commit/6330665d8d4e59d034c3e49cb7c36050ac007a7c for the next patch.

WoWPro.lua error on line 588 when trying to auto switch guides.

Upgraded to the newest version of the addon today (6.2.0) and when I was going through checking off all the guides I had completed after deleting my lua save (just in case of a conflict) I got the following error when the addon tried to automatically switch from the Spires of Arrak guide to the Nagrand.

Date: 2015-06-25 01:44:29

ID: 9

Error occured in: Global

Count: 1

Message: ..\AddOns\WoWPro\WoWPro.lua line 588:

   attempt to index field '?' (a nil value)

Debug:

   WoWPro\WoWPro.lua:588: GetGuideName()

   WoWPro\WoWPro_Parser.lua:475: ParseSteps()

   WoWPro\WoWPro_Parser.lua:528:

      WoWPro\WoWPro_Parser.lua:506

   (tail call): ?

   [C]: ?

   [string "safecall Dispatcher[1]"]:9:

      [string "safecall Dispatcher[1]"]:5

   (tail call): ?

   ...ce\AddOns\Archy\Libs\AceBucket-3.0\AceBucket-3.0.lua:118: func()

   ...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0.lua:55:

      ...s\AckisRecipeList\libs\AceTimer-3.0\AceTimer-3.0.lua:48

Locals:

None

AddOns:

 

Ludovicus's picture

Re: WoWPro.lua error on line 588 when trying to auto switch

Thanks for the report.   I'll fix this later today and it will be released as part of 6.2.0A next Thursday.

Without even looking at the code, I can see in my head what I did wrong ;-).

Normally run all my guides

Normally run all my guides with Difficulty/Completeness set to 3, so I get everything.

Today I decided to run it Difficulty/Completeness set to 1, which was great until it got to the end of the guide. In the title, I had 114/127, and the window was blank, it didn't automatically move onto the next guide.

Ludovicus's picture

Re: Normally run all my guides

As of 6.2.0 all guides now have a "D" step added to the end to fix this problem for real.

I will also be adding an L step to the start of every guide to enforce the minimal level and will remove the ones you started adding.

It is a good idea, but there is no need for guide writers to implement it.

Ludovicus's picture

Re: Normally run all my guides

Whoops!   I suspect that if you skip quests in a guide, that the same thing will happen.

I know where to look.  The fact that the count is off means that the completeness total is off.

Thansk for the report.   I'll have it fixed for Wednesday,.

Also experiencing bad framerates

No LUA errors, just really bad framerates, so bad I had to disable the addon.

 

I am running a Core2Quad 4.2Ghz system, 4 gig ram, 1 TB HD, nVidia GForce GT460 video card.

Ludovicus's picture

If you have bad framerates with WoWPro ...

Please try the development version of the addon at :

https://github.com/Jiyambi/WoW-Pro-Guides/archive/master.zip

and be sure to disable the recorder, or you will get confused.  I updated all of the support libraries, which I forgot to do after 5.4 was released.   Some were VERY stale.

Also the addon saves a copy of the latest log in your world of warcraft directory.  You can get it at:

  • /Applications/World of Warcraft/WTF/Account/6666666#1/SavedVariables/WoWPro.lua
  • C:\Program files (x86)\World of Warcraft\WTF\Account\6666666#1\SavedVariables\WoWPro.lua

Just send me that file.   If you want to be even more helpful.  Download and install this addon:

http://www.curse.com/addons/wow/brokercpu

and then left click on the minimap button that looks like a computer with a red wave on it and select "CPU profiling".  Then quit out of WoW and start it again.  It will be monitoring your FPS and collecting data on all your addons.  To see a report, just bring the mouse over the minimap button.  Send me a screenshot of things that are bad.

 

 

FPS drops when WoWPro is enabled

When the addon isn't enabled I have an FPS of 50 - 80. When enabled, and after doing a few quests, it drops to 2 - 10 which is not really playable. When disabling the addon, the FPS goes up right away. This happens to me in all Pandaria leveling guides.  It has been happening to me for the last few versions actually.

I tried to look at the debug log, to see if that would provide anything. Upon clicking to show the log, it first froze my WoW and then my entire computer, forcing me to reboot.  So debug log is not really possible, LUA error is not given.

Ludovicus's picture

Re: FPS drops when WoWPro is enabled

Can you tell me what kind of computer you are running on?

Can you tell me what other addons you have loaded?

The fact that you can't get a debug log makes me think something is very wrong.

My FPS never gets below 60, so I suspect that our addon is interacting with another addon.

 

I am using ElvUI,

I am using ElvUI, arkinventory, deadly bossmods and a few battlepet addons.

I did notice this: it only happens when accepting certain quests, I disable the addon, do what I have to do, run back to where I have to turn in the quests, enable the addon and turn them in WITH the addon enabled.  My FPS goes back to normal as soon as the quests are turned in.  It's the quests where the horde enter pandaria.  

 I do have to say, I tried it on another alt and it hasn't happened anymore as soon as my first char bit through the FPS drops.  Maybe it was an addon causing this that has been updated since, I have no clue.  But at the moment I can play without FPS drops.  In case this changes again I will let you know.

Is there any other way to check the debug log (file in the WTF folder or something), maybe it will point out what was going wrong when I tried to open it in-game.

I'm running wow on windows 7 Home Premium, 6 gigs of RAM, AMD  A8 - 4500M APU radeon (it's a laptop).  I never had problems running wow, cept for those few times that the FPS dropped in the past.

Ludovicus's picture

Re: I am using ElvUI,

Hmm, let me see if I can rig a test for you to run.

I'll also double-check I am using the latest support libraries for the addon.   Sometimes they need updates after a release.

 

Lua Error

I get the following LUA-error when starting WoW.  I use the 2.7.3 version.

 

Date: 2013-12-15 20:44:34

ID: 1

Error occured in: Global

Count: 1

Message: ..\AddOns\WoWPro\WoWPro.lua line 55:

   bad argument #4 to 'format' (string expected, got nil)

Debug:

   [C]: ?

   [C]: format()

   WoWPro\WoWPro.lua:55: dbp()

   WoWPro\WoWPro_Broker.lua:306: NextStep()

   WoWPro\WoWPro_Broker.lua:722: NextStepNotSticky()

   WoWPro\WoWPro_Mapping.lua:431: MapPoint()

   WoWPro\WoWPro_Events.lua:192: AutoCompleteQuestUpdate()

   WoWPro\WoWPro_Events.lua:586:

      WoWPro\WoWPro_Events.lua:349

Ludovicus's picture

Re: Lua Error

I had this happen to me and I checked in a fix for it (https://github.com/Jiyambi/WoW-Pro-Guides/commit/be07342893fad0d147525b5739e8fc96871351e5) and it stopped happening to me.

I guess I need to look harder!

 

 

Addon being goofy

Version is the newest one, the 2.7.0 from Sept 10th, 2013.

No exact error message, but everytime i log on it starts me back at the begining of the guide for the zone i am in. And once i get back to where i was it wont complete the steps, so i have to do it manually, and then after a couple quests it goes backwards mutiple steps.

Current Guide: Grizzly Hills

Faction: Its happening on both for my toons

Step: all of them

Same Problem

I am having all the same issues are Jardi but in the Draenor Zones both on Horde and Alliance. Its like sometimes the addon wont advance after picking up or turning in a quest. And sometime when I come back online its on a quest way back (Example Frostfire ridge Horde side quest Pale Loot bag. The one from rescuring the baby frost wolf by the first town).  Tried uninstalling and reinstalling no luck. Am using version F and set to rank 3.

Emmaleah's picture

Pale Loot Sack Specifically

That step will not auto check off, I have tried and tried to figure out why and can't.  I have debated taking it out of the guide but havent yet, I think I put a comment you have to manually check this off.. If I havent I will go do that now. :(  Im just going to change it to the next QID then it still wont check off when you do it, but at least once you check it off manually, it will stay checked off.

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

Emmaleah's picture

Found right QID for Pale Loot sack

I was randomly stumbling around on wowhead and came across their guides to treasure by zone, I know have the CORRECT QID for Pale Loot Sack.  I spent so long trying to figure that out in Beta :(

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

Ludovicus's picture

Blizzard bug 170644

Well, I dug around the source code to the Blizzard Quest UI and found this gem:

    --The counts may have changed with SetNearestValidSelection expanding quest headers.
    --Bug ID 170644
    numEntries, numQuests = GetNumQuestLogEntries();

I ran a test on a Level 90 toon that had a bunch of quests in progress (17) and the dammed function would return 12,17 and find only 7 quests!

Trying to use the UI to even look at 17 quests was hard, as things would misbehave left and right.

It looks like numEntries is wrong, but numQuests is right.
I'll see what I can do to toughen up our code.

Ludovicus's picture

Re: Blizzard bug 170644 (Testers Needed)

OK, so there are two bugs here.

  1. We relied on the number of entries returned from GetNumQuestLogEntries to be constant.  But anytime you expand or collapse a header that number changes.  So a simple linear for loop iterating over the number of entries can get into trouble as the number of entries under a header may be bigger than the number of headers!
  2. If the QuestLog UI is up, this code can't run or horrible things happen.

So I will check the code in for this shortly.  Any testers?  Use the development zip at

https://github.com/Jiyambi/WoW-Pro-Guides/archive/master.zip

 

GetNumQuestLogEntries() craziness

Hi.  I have not checked your code, but you are correct in the number of quests being returned is correct no matter which headers are open or closed.  However, the location (index into GetQuestLogTitle()) of quests will move depending on whether they are in closed headers.  For example, quest at index 2 (in an open header) will move to the end of the list if that header is closed.  Not knowing the total count of the quests through which to iterate (because GetNumQuestLogEntries() will not return the proper number if headers are closed) means to get the complete list of quests in the log one needs to continually iterate until no title is returned.  I believe this should give all quests and headers, though not necessarily in any convenient order.

Ludovicus's picture

Re: GetNumQuestLogEntries() craziness

A code review of https://github.com/Jiyambi/WoW-Pro-Guides/blob/master/WoWPro/WoWPro_Broker.lua#L765 would be appreciated, but I think I ended up implementing something close to your suggestion. When I expanded a header section and was about to collapse it because we hit the next header, I reset the index into the quests to end up being one past the old header, which is where the new header was ending up after the collapse.

To further refine it, I will change the repeat loop termination condition from:

                if ( i > 50 ) then
                 break
                end
        until num == numQuests

to:
        until not questTitle

and eliminate:
                if not questTitle and (num < numQuests) then
                 WoWPro:Error("PopulateQuestLog: return value from GetQuestLogTitle(%d) is nil.",i)
                end

PS: There are two new undocumented return values from GetQuestLogTitle() Smiling

This is the routine I use in

This is the routine I use in Grail.  (The next release as I updated it based on your previous findings.)

 

-- Returns a table whose key is the questId and whose value is a table made of the quest title and the completedness

-- of the quest for each quest in the Blizzard quest log.  If there is nothing in the log, an empty table is returned.

_QuestsInLog = function(self)

if nil == self.cachedQuestsInLog then

local retval = {}

-- It tuns out that numQuests will be correct, but numEntries will not reflect the total number of values that

-- will be returned from GetQuestLogTitle() if any of the headers are closed.  With closed headers, the quests

-- that would normally be in them are going to be at the end of the list, but not necessarily in any specific

-- order that is helpful.

-- local numEntries, numQuests = GetNumQuestLogEntries()

-- for i = 1, numEntries do

local i = 1

while (true) do

local questTitle, level, questTag, suggestedGroup, isHeader, isCollapsed, isComplete, isDaily, questId, startEvent = GetQuestLogTitle(i)

if not questTitle then

break

else

i = i + 1

end

if not isHeader then

retval[questId] = { questTitle, isComplete }

end

end

self.cachedQuestsInLog = retval

end

return self.cachedQuestsInLog

end

 

 

After looking at your code I believe there is no need to do all the work with expansion and collapsing of the headers.  If you based your control structure on the while loop I implemented here I imagine you can just do all your work in the "if not is header then" block.  Of course I do not know if the calls to things like GetNumQuestLeaderboards() will work with the indexes that are past the "entries" value that is returned from GetNumQuestLogEntries().  But since GetQuestLogTitle() does work with those values, I would hope the rest of the Blizzard API would.

 

I just realized you use the header name for each quest, so my suggestion will not be that great since my loop does not care about which header a quest is in, and in fact cannot know this because the quests in closed headers are at the end of the list in an unknown order.

Ludovicus's picture

Re: This is the routine I use in

You might want to try the following experiment. 

Collapse all the headers in the Quest Log UI.  Then run your function.

It used to be the case that a straight loop like yours would not pick up any quests!

My function works with all

My function works with all the headers collapsed.  At least this new version does.

Ludovicus's picture

Re: My function works with all

Turns out we do use the header in *1* place:   The guide recorder uses it to detect class specific quests.

 

 

That sort of sucks.  Is there

That sort of sucks.  Is there no other way around this?  Perhaps you can just hardcode the list of class specific quests internally and reference those?

Ludovicus's picture

Re: That sort of sucks. Is there

Its there for new guides, so by definition, the quests may not be in the usual lists, particularly in the PTR.

Is the guide recorder

Is the guide recorder something that is an optional function?  If so, perhaps just make the guide recorder use the complicated form of getting the Blizzard quest list, and have the normal addon use a simpler form?  For the complicated form I have no idea what the problems are when the Blizzard quest panel is open, but I would normally think walking through the list one time to open all the headers, recording which ones I opened, and then going through the entire list to get the quest information (since the API that returns the counts should be valid since all the headers are open, and even if it weren't you could just do the same type of while loop until the title is nil), and then go back and close the headers that I open.

Ludovicus's picture

Re: My function works with all

So I had to poke at why both work. I used this function to test:

function WoWPro:Tepes()
    local i = 1
    while (true) do

        local questTitle, level, questTag, suggestedGroup, isHeader, isCollapsed, isComplete, isDaily, questId, startEvent = GetQuestLogTitle(i)
        if not questTitle then
            break
        else
            i = i + 1
        end
        if not isHeader then
            WoWPro:Print("%d: %s",questId,questTitle)
        else
            WoWPro:Warning("%s: %s",tostring(isCollapsed),questTitle)
        end
    end
end

and I got the following:

20131202/1529.646 ~ WoWPro: 1: Battle Pets
20131202/1529.647 ~ WoWPro: nil: Blackrock Caverns
20131202/1529.648 ~ WoWPro: 28735: To the Chamber of Incineration!
20131202/1529.649 ~ WoWPro: nil: Brawler's Guild
20131202/1529.650 ~ WoWPro: 32851: Blingtron 3000
20131202/1529.651 ~ WoWPro: 32844: Secret of the Ooze
20131202/1529.652 ~ WoWPro: 1: Hallow's End
20131202/1529.653 ~ WoWPro: 1: Legendary
20131202/1529.654 ~ WoWPro: 1: Mana-Tombs
20131202/1529.655 ~ WoWPro: 1: Pandaren Brewmasters
20131202/1529.656 ~ WoWPro: 1: Stormstout Brewery
20131202/1529.657 ~ WoWPro: 1: The Arboretum
20131202/1529.658 ~ WoWPro: 1: Vale of Eternal Blossoms
20131202/1529.659 ~ WoWPro: nil: Valley of the Four Winds
20131202/1529.660 ~ WoWPro: 31323: Buy A Fish A Brewery?
20131202/1529.661 ~ WoWPro: 31813: Dagra the Fierce
20131202/1529.662 ~ WoWPro: 31889: Battle Pet Tamers: Kalimdor
20131202/1529.663 ~ WoWPro: 11131: Stop the Fires!
20131202/1529.664 ~ WoWPro: 31902: Battle Pet Tamers: Eastern Kingdoms
20131202/1529.665 ~ WoWPro: 8311: Hallow's End Treats for Jesper!
20131202/1529.666 ~ WoWPro: 31468: Trial of the Black Prince
20131202/1529.667 ~ WoWPro: 31473: The Strength of One's Foes
20131202/1529.668 ~ WoWPro: 10977: Stasis Chambers of the Mana-Tombs
20131202/1529.669 ~ WoWPro: 30567: Blanche's Boomer Brew
20131202/1529.670 ~ WoWPro: 31327: Trouble Brewing
20131202/1529.671 ~ WoWPro: 31539: A Thing of Beauty
20131202/1529.672 ~ WoWPro: 33229: A Flash of Bronze...
20131202/1529.673 ~ WoWPro: 29371: A Time to Lose

Note that all of the "hidden" quests show after the last item that shows in the UI (Buy A Fish A Brewery?). So your code does work if you don't care about which header they were under.

So now I gotta see if we use that information anywhere.
If not, I can simplify our code.

Ludovicus's picture

QuestLog Being Goofy

This bug occured previously and we added code to "uncollapse" the sections so we could see the bugs, but with account wide quests, people are probably running right near the edge of what the UI is allowing to be displayed/queryied.

I'll give that code a looking over.  It would not be the first time Blizzard changed its behaviour.

 

Ludovicus's picture

Re: Goofy Grizzly Hills

Could someone give me a  log with debugging enabled?

Also, pull up the current guide and mouse over the quests that should be checked off, but are not.

It should tell you why the quest was not selected.

WowPro Why Box

Ludovicus's picture

Debug Log from demonllama@Curse

In a nutshell, it's WoW-Pro conflicting (somehow) with the Account-wide Pet Battle quests. Abandon those, and it works fine. Other than the guides "not working", observably behavior is that in the Quest Log, it keeps auto-collapsing all the quest sections every time something happens to update the log (accepting a new question, completing an existing one, etc). For some reason, that nailed the Grizzly Hills guide and the Mount Hyjal guides pretty hard. The error I was getting was that, for some reason, it was saying it couldn't find the quest in the Quest Log. For example:

20131201/0123.501 ~ WoWPro: Called WoWPro:NextStep(41,1)
20131201/0123.502 ~ WoWPro: Signaled for UpdateGuide
20131201/0123.503 ~ WoWPro: Running: UpdateGuideReal()
20131201/0123.504 ~ WoWPro: Called WoWPro:NextStep(1,1)
20131201/0123.505 ~ WoWPro: Step C [Flamebreaker] skipped as not in QuestLog
20131201/0123.506 ~ WoWPro: Step T [Flamebreaker] skipped as not in QuestLog
20131201/0123.507 ~ WoWPro: Step C [The Return of Baron Geddon] skipped as not in QuestLog
20131201/0123.508 ~ WoWPro: Running: WoWPro:RowUpdate()
20131201/0123.509 ~ WoWPro: Called WoWPro:NextStep(41,1)
20131201/0123.510 ~ WoWPro: Called WoWPro:NextStep(42,2)
20131201/0123.511 ~ WoWPro: Step T [The Return of Baron Geddon] skipped as not in QuestLog
20131201/0123.512 ~ WoWPro: Step T [Emerald Allies] skipped as not in QuestLog
20131201/0123.513 ~ WoWPro: Step T [The Captured Scout] skipped as not in QuestLog
20131201/0123.514 ~ WoWPro: Step C [Twilight Captivity] skipped as not in QuestLog
20131201/0123.515 ~ WoWPro: Step T [Twilight Captivity] skipped as not in QuestLog
20131201/0123.516 ~ WoWPro: Step T [Return to Alysra] skipped as not in QuestLog
20131201/0123.517 ~ WoWPro: Called WoWPro:NextStep(54,3)

When Flamebreaker was most definitely in my quest log.

Ludovicus's picture

Re: Goffy Grizzly Hills

OK.  I'll take a look at the guide to see if I can guess why.

But I may need a debug log for this one.

Estelyen's picture

Can confirm

I just entered Grizzly Hills with my druid twink and I get the same problem.

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.

~Garfield

Cannot download newest version 2.7.0

The addon page says the newest version is 2.7.0 released on September
10, 2013. When I click download, it is giving me version 2.6.4. I would
really like to download the newest version that is for WoW 5.4. Please
fix this! Thank you for your guides.

-Iconoclast

What happened to being able to mark things as sticky?

I remember that I used to be able to right click (I think?) on a step and see a menu that included an option to make it sticky.  It was helpful and I miss being able to do that. Now, when I click or right click on the text for the step, it highlights the text block in yellow, which isn't useful and doesn't let me mark things as sticky.