I just switched to windows 7 x64 with comodo internet security. and now everytime I restart my computer I got a window telling me that comodo and curse client can have problem together. Can you make sure that this window is only displayed once. also the shortcut on the desktop is added back everytime can you make sure it's not added back once I've deleted it.
LightHeaded, EveryQuest, TourGuide are great addon but none of them provide their data in other language than English.
Instead of doing an addon that would contain all the data they need why not give addon author access to a data repository which contain all basic quest data. They can then choose which data to use and which format to store the data in their addon.
It's a good thing they are adding a way to retrieve completed quest history.
My only concern with this is that they are only giving quest id. If no api is provided to retrieve quest data we'll have to rely on a quest db.
would it be possible to build such db automatically from a wowhead automatic datamining? (in all available languages?)
The following information would be interesting for each quest id
quest name
quest zone
is daily
start npc (or start item)
end npc
previous quest id if in a quest chain
next quest id if in a quest chain
/script tomQuest2:Print(tomQuest2.firstRun and "FIRST" or "NOT FIRST")
Response:tomQuest2: FIRST
/script tomQuest2:Print(tomQuest2.db.profile.quests.questsSorting)
Response:tomQuest2: weightedA
/script tomQuest2:Print(tomQuest2.db.profile.quests.zoneSorting)
Response:tomQuest2: levelA
And after the last three scripts the tracker has appeared :)
Thank you for the great addon and keep up the excellent work
Edit:
Every time i try to change the fonts on anything it gives me this error
[2009/10/04 18:35:13-55-x1]: tomQuest2_Config-10505\config.lua:773: attempt to index global 'LSM' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0-36:794: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:609>
AceConfigDialog-3.0-36:842: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:834>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-28 (ButtonFacade):305: in function `Fire'
...cade\Libs\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:152: in function <...cade\Libs\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:141>:
Locals:
Sometimes debuglocals() returns nothing, it's one of those times... (FYI: This message is a HotFix from Decursive to prevent a C stack overflow)
---
Edit2: Update about the tracker after the initial update the tracker stays the same for the rest of the session and running those scripts again doesn't appear to work.
apparently there is some problem with the parsing of questlog.
can you run this script and give me the result:
/script for uid, questData in pairs(tomQuest2.quests) do if questData.id and not questData.extras then tomQuest2:Print(uid) end end
Can you try the following scripts and giving me back the results :
/script tomQuest2:Print("numEntries"..tomQuest2.numEntries);
/script tomQuest2:Print("numQuests"..tomQuest2.numQuests);
/script local numQuests = 0; for k in pairs(tomQuest2.quests) do numQuests = numQuests + 1 end; tomQuest2:Print("numQuestsInTable"..numQuests);
/script tomQuest2:Print("numSortedQuests"..#(tomQuest2.sortedQuests));
/script local numZones = 0; for k in pairs(tomQuest2.zones) do numZones = numZones + 1 end; tomQuest2:Print("numZones"..numZones);
/script tomQuest2:Print("numSortedZones"..#(tomQuest2.sortedZones));
/script tomQuest2:Print("quests list");
/script for uid in pairs(tomQuest2.quests) do tomQuest2:Print(uid) end;
It was a bug in tomQuest2 beta 19, I changed my hook on GameTooltip to "manual" hook but forgot to put back the orig function in case I disabled the tooltip module. This is fixed in beta 20. (raid mode automatically disable tooltip module when entering a raid instance and enable it when leaving the zone instance)
I forgot to mention that i am using QuestGuru (from Curse) for quest log enhancement.
I hope this helps.
That might be the problem. Can you try disabling tomQuest2 and using the standard blizz tracker what happen when you click on a quest in the bliz tracker? is it opening the questlog?
0
0
0
Instead of doing an addon that would contain all the data they need why not give addon author access to a data repository which contain all basic quest data. They can then choose which data to use and which format to store the data in their addon.
0
My only concern with this is that they are only giving quest id. If no api is provided to retrieve quest data we'll have to rely on a quest db.
would it be possible to build such db automatically from a wowhead automatic datamining? (in all available languages?)
The following information would be interesting for each quest id
quest name
quest zone
is daily
start npc (or start item)
end npc
previous quest id if in a quest chain
next quest id if in a quest chain
0
http://github.com/tekkub/wow-ui-source
0
thanks :)
0
Also can you tell me what is the locale of your client?
0
EPGP.RegisterCallback(self, "MassEPAward")
0
0
0
apparently there is some problem with the parsing of questlog.
can you run this script and give me the result:
I'll correct the config error in a next release
0
can you tell me the result of this
then run the following and tell me if after that you see the quests in the quest tooltip / tracker:
0
0
0
That might be the problem. Can you try disabling tomQuest2 and using the standard blizz tracker what happen when you click on a quest in the bliz tracker? is it opening the questlog?