20 odd pages a little much to get through.
Problem I have seen is the quest popup dialog always shows the last 'items required' as part of the quest requirements, even if nothing to do with the quest.
For example, did quest for 5 raptor horns, when I then look at any other quest, they all show a need for 5 raptor horns...
This a known problem?
I keep fubar updates using the wowaceUpdater program every couple of days.
Does anyone know which part of questfu uses babble-2.2?
Very late reply, but QuestsFu uses TouristLib, which in turn requires Babble-Zone-2.2 specifically, although both the TouristLib and QuestsFu TOCs call for Babble-2.2.
It would be nice if this could be updated to use LibSink-2.0, and either LibTourist-3.0 or LibBabble-Zone-3.0 or both if necessary. I really like the layout of the improved detached tooltip, and the party information is nice to have. I tried BetterQuest, but it throws errors here and there (and have been mentioned before), and my color settings don't get saved on a reload or a relog. I also dislike the count on the right hand side of the zone name, and I couldn't find an option to turn that count off.
Updated LightHeaded yesterday, throws this error when I open a quest description from QuestFu, posted on Lightheaded thread, Cladhaire said it's not Lightheaded throwing this.
[2008/05/30 09:00:33-1456-x2]: LightHeaded-239\LightHeaded.lua:117: attempt to compare number with string
LightHeaded's API has changed to use Wowhead quest IDs and QuestsFu needs to be updated to use the new API. Here's a patch I made that fixes it: http://www.doxxx.net/wow/Comments.lua.patch
Edit: Is that all of the comments lua?If not what part do I exchange?
That file is a patch file which describes the changes to be made to the original file. Each section starting with @@ describes a particular change. The @@ line describes where the change starts, so e.g. @@ -108,8 +108,12 @@ means that the change starts at line 108. @@ -147,12 +151,14 @@ means that the change would have started at line 147 in the original file but after applying changes that appeared prior to this section it now starts at line 151. Within each @@ section the lines starting with - are to be removed and the lines with + are to be added in their place. Lines without a + or - at the start stay the same.
Why does the party log window always say "doesn't have Quixote" even when they have the same version of Questsfu installed and showing the party log is enabled? It worked yesterday and doesn't today, no settings were changed, so what needs to be done?
(Also, it works perfectly fine with some characters of me and my quest companions', but it doesn't with our mains)
I am also having the same problem as the above poster. Anyone have an idea? I've tried updating. I've tried using Quixote-2. It just keeps telling me and my wife that it's not installed.
Not really an error, but I have QuestFu showing some random numbers and letters (maybe a hex sequence or something?) showing my current completed quests. For a specific note, here's a pic of it:
That setting is "quests completed / total current quests". Basically, I don't have any more quests in my quest log and that shows up on the FuBar panel for QuestFu. Any way to fix this to actually say "0/0" and not "01FE01001FE01/0"? Thank you.
Not really an error, but I have QuestFu showing some random numbers and letters (maybe a hex sequence or something?) showing my current completed quests. For a specific note, here's a pic of it:
That setting is "quests completed / total current quests". Basically, I don't have any more quests in my quest log and that shows up on the FuBar panel for QuestFu. Any way to fix this to actually say "0/0" and not "01FE01001FE01/0"? Thank you.
looks like there is a missing character (the "function divider" or what it should becalled, like the : in dogtags) in the code between the number 0 and the hex value for its color (1FE010).
I'm sorry to bring this up again. Is it remotely possible to ADD the correct comments for us Lightheaded users??? Guess I should be appreciative that you are at least still maintaining this, but it's frustrated having to find my saved copy of the comments section,and have to dig it open to change it. And who knows is someday you may even need to update the comments.
I'm sorry to bring this up again. Is it remotely possible to ADD the correct comments for us Lightheaded users??? Guess I should be appreciative that you are at least still maintaining this, but it's frustrated having to find my saved copy of the comments section,and have to dig it open to change it. And who knows is someday you may even need to update the comments.
same here. Everytime this mod is updated I have to go in and fix it so that wowhead works again. It used to be supported, and then about 4 or 5 months ago, it just stopped working.
The fix that most of us are implementing would be VERY easily added to an updated version of questfu. Just puzzling.
Sorry if this was asked earlier...but in order to see the quest objectives people in my party still need in the tracker, I have to turn on Completed Objectives and see ALL the objectives, even the ones everyone has completed. Is there an option to only hide objectives EVERYONE has completed, not just the ones you've completed? (I.E. show the ones that you've completed, but your party hasn't yet?) If not, can this be added? >.>
I'd like to second IceShadow's request. I often quest with my partner and those quests which require collecting items that only one person in the party can loot at a time means that when I finish collecting first, the tracker collapse the quest line so I can't see the other person's progress. If it could only collapse down when all party members have completed the quest, that would be great.
Every time I load up QuestsFu, on 3.0.2, I stop seeing Blizzard Error messages on spellcast such as the target out of LoS or OOR messages. If I turn it off, they come back. As a healer these messages give me some important feedback, and it has been annoying to need to logoff to turn off this mod anytime I want to run an instance.
quote=Bremic;244477]Every time I load up QuestsFu, on 3.0.2, I stop seeing Blizzard Error messages on spellcast such as the target out of LoS or OOR messages. If I turn it off, they come back. As a healer these messages give me some important feedback, and it has been annoying to need to logoff to turn off this mod anytime I want to run an instance.[/quote]
I made a bit of research into this as it annoys me too as a healer.
The core of the problems seems to be in the Player Status module, as disabling it in modules menu is enough to bring the error messages back.
And no, disabling / enabling the blizzard error message thingy in Player status menu doesn't help, you need to disable the whole module.
But I'll look into it if I can make a quick hotfix for it.
Edit: Read my next post 3 posts ahead of this, it's all there
Problem I have seen is the quest popup dialog always shows the last 'items required' as part of the quest requirements, even if nothing to do with the quest.
For example, did quest for 5 raptor horns, when I then look at any other quest, they all show a need for 5 raptor horns...
This a known problem?
I keep fubar updates using the wowaceUpdater program every couple of days.
Very late reply, but QuestsFu uses TouristLib, which in turn requires Babble-Zone-2.2 specifically, although both the TouristLib and QuestsFu TOCs call for Babble-2.2.
It would be nice if this could be updated to use LibSink-2.0, and either LibTourist-3.0 or LibBabble-Zone-3.0 or both if necessary. I really like the layout of the improved detached tooltip, and the party information is nice to have. I tried BetterQuest, but it throws errors here and there (and have been mentioned before), and my color settings don't get saved on a reload or a relog. I also dislike the count on the right hand side of the zone name, and I couldn't find an option to turn that count off.
Each time this thread hits a new page, please continue to repost that, since having it added probably isn't happening.
I don't understand why he wouldn't add it.Maybe he isn't reading the posts here..I dunno.
[2008/05/30 09:00:33-1456-x2]: LightHeaded-239\LightHeaded.lua:117: attempt to compare number with string
---
Edit: Is that all of the comments lua?If not what part do I exchange?
That file is a patch file which describes the changes to be made to the original file. Each section starting with @@ describes a particular change. The @@ line describes where the change starts, so e.g. @@ -108,8 +108,12 @@ means that the change starts at line 108. @@ -147,12 +151,14 @@ means that the change would have started at line 147 in the original file but after applying changes that appeared prior to this section it now starts at line 151. Within each @@ section the lines starting with - are to be removed and the lines with + are to be added in their place. Lines without a + or - at the start stay the same.
Edit: For those who can't easily use patch files, I've uploaded a fixed version of Comments.lua to http://www.doxxx.net/wow/Comments.lua
(Also, it works perfectly fine with some characters of me and my quest companions', but it doesn't with our mains)
That setting is "quests completed / total current quests". Basically, I don't have any more quests in my quest log and that shows up on the FuBar panel for QuestFu. Any way to fix this to actually say "0/0" and not "01FE01001FE01/0"? Thank you.
looks like there is a missing character (the "function divider" or what it should becalled, like the : in dogtags) in the code between the number 0 and the hex value for its color (1FE010).
same here. Everytime this mod is updated I have to go in and fix it so that wowhead works again. It used to be supported, and then about 4 or 5 months ago, it just stopped working.
The fix that most of us are implementing would be VERY easily added to an updated version of questfu. Just puzzling.
I made a bit of research into this as it annoys me too as a healer.
The core of the problems seems to be in the Player Status module, as disabling it in modules menu is enough to bring the error messages back.
And no, disabling / enabling the blizzard error message thingy in Player status menu doesn't help, you need to disable the whole module.
But I'll look into it if I can make a quick hotfix for it.
Edit: Read my next post 3 posts ahead of this, it's all there