[Request]
Say you mouse-over 'Spider' and for the quest 'Kill Spiders' you need to kill 10 'Spiders' On the tooltip, it would be nice if it displayed 'Kill Spiders: 0 / 10'
This would also be nice on items
That functionality is available through numerous other addons, like Fubar_QuestFu.
This addon extends the functionality of Cartographer not your tooltip imo.
I am having a problem with some quests where QuestObjectives thinks i still am on the same part in the series as the previous one.
For example Clefthoof Mastery in Nagrand where you have to kill 30 Clefthoof Bull's and in the next part your just going to kill one huge Clefhoof elite.
I am having a problem with some quests where QuestObjectives thinks i still am on the same part in the series as the previous one.
For example Clefthoof Mastery in Nagrand where you have to kill 30 Clefthoof Bull's and in the next part your just going to kill one huge Clefhoof elite.
Unfortunately WoW does not provide any sort of unique ID for quests, so I have to figure out manually what different quests are. Currently it uses the quest name and the level of the quest, which works most of the time, but as you saw in that particular quest line it didn't work perfectly. Is the second quest a group quest? In that case it will work better in the next version because I will store the type of the quest as well.
For example Clefthoof Mastery in Nagrand where you have to kill 30 Clefthoof Bull's and in the next part your just going to kill one huge Clefhoof elite.
Unfortunately WoW does not provide any sort of unique ID for quests
One way to overcome this would be to create a MORE unique ID for quests. Lvl+Quest+Questgiver+Objectives should do it. If a quest had multiple objectives (3 for example), it would be Lvl+Quest+Questgiver+Objective1+Objective2+Objective3.
I am having a problem with some quests where QuestObjectives thinks i still am on the same part in the series as the previous one.
For example Clefthoof Mastery in Nagrand where you have to kill 30 Clefthoof Bull's and in the next part your just going to kill one huge Clefhoof elite.
Unfortunately WoW does not provide any sort of unique ID for quests, so I have to figure out manually what different quests are. Currently it uses the quest name and the level of the quest, which works most of the time, but as you saw in that particular quest line it didn't work perfectly. Is the second quest a group quest? In that case it will work better in the next version because I will store the type of the quest as well.
Yeah i thought that was done already and it was bugged or somerthing. Yes it's an elite quest witch suggest 2 players.
Would it be an idea to generate your own ID, for instance, by calculating the MD5 hash of quest name and objective?
Just thinking out loud here, this may not be a smart idea at all...
is it possible to have a button that execute a "/way x y" for the quest we are currently reading? (if present on the database ofc) it would be nice to have that button embedded in the quest log like the addon "bookmark" does.
Also, id like the addon to recognize the npc that starts or ends a quest, which is also a quest target. It would be easy to copy all NPCs and its coordinates from wowhead.
if this is to become diassociated from Cartographer, what name will it go by?
I'd like to be ready so i can make sure I keep this one up to date :-)
Also any news of when we can get rid of cartographer_quests? (i hate this because the mark it gives covers over the bright yellow dot on my map for Q hand-ins)
is it possible to have a button that execute a "/way x y" for the quest we are currently reading? (if present on the database ofc) it would be nice to have that button embedded in the quest log like the addon "bookmark" does.
Also, id like the addon to recognize the npc that starts or ends a quest, which is also a quest target. It would be easy to copy all NPCs and its coordinates from wowhead.
Both of these features are planned. :D
Quote from se99jmk »
if this is to become diassociated from Cartographer, what name will it go by?
I'd like to be ready so i can make sure I keep this one up to date :-)
Also any news of when we can get rid of cartographer_quests? (i hate this because the mark it gives covers over the bright yellow dot on my map for Q hand-ins)
I have thought a lot about the name. I think the first new big version will still be called Cartographer_QuestObjectives if no other reason than make upgrading the old DB simple. I will probably just change the name to QuestObjectives but I'm not sure the best way to go about doing this. I suppose I could leave Cart_QO up on the SVN as a mod that just displays a big fat message on login explaining the name change.
As for timing... I've been working on it a lot, but there's still a lot of work to be done. I figure it'll probably be a couple weeks.
Its a try to get a huge DB from all quests of game but have a little problems to share these information.
First its a Huge file its time to divide the problem ?
like Alliance/Horde .lua files ?
Cartographer_QuestObjectives_Horde.lua
Cartographer_QuestObjectives_Alliance.lua
and some day need separate by level 0-40 41-60 61-70? or the file dont have size limit ?
A cool adition to mod can be a "import file" to get data from another people, like Cartographer_QuestObjectives_Import.lua once time read adn merged with correct lua can be delete.
Subxero: OverloadUT has an import feature planned which is why I stopped writing my own. He's also going to make some changes to the DB structure that will improve the file size. However, he is also planning on storing a lot more information, so I suspect the size will end up being similar.
That being said...
OverloadUT: I "DO" have some suggestions about the database..
About 50-60% of all quest are exactly the same for both Horde or Alliance characters. The questgiver is often different, but the quest title and objectives are exactly the same.
One of the things I recently did was convert quite a few of these from my Horde database to an Alliance database. The problem is that the amount of information loaded is verging on huge because of all the duplicate data from both factions when you have both in the same file.
I suggest a couple of alternative solutions:
#1) Upon receiving a new quest (or at login), search for the quest in the Faction database you are currently playing. If it's there, do nothing else and continue as normal. If it is NOT there, then begin a search in the quest database of the OPPOSITE faction. When doing this, perform a check on objectives as well to make sure it is actually the same quest. If it IS the same quest, move it to a third table called "Both". Obviously, in actual practice, the search order would be current faction, then both, then opposite faction.
- First, this cuts down on the overall size of the tables because it eliminates the duplicates.
- Second, it allows someone with a database in one faction to take advantage of quest information they have in another format.
- As noted above, while the objectives and titles are the same, the questgiver is often different. Since you plan on storing this as well, I would simply note it as ["horde"] = { ["questgiver"] = "",["turnin"] = "" } within each quest. That way, you could add other unique faction info if the need ever arised.
#2) Alternately, you could simply make the databases Load-On-Demand for each faction.
I'm not a huge advocate of the second option because I love the idea of searching the other factions quests if it's not in my faction. Right now, I am leveling an alliance toon that is 41 and a horde toon that is 47. If I complete a quest with the 47, I would love to have that recorded for the 41.
#3) You could also check the faction of the questgiver and if it's one of the Nuetral races, put it in the "Both" table.
Unfortunately using the faction of the quest giver is not a sure fire way to tell if a quest is cross faction.
However, the new version of the DB will handle pretty much exactly what you want. The short description is that mob locations will be stored in a separate cross-faction table, so if you get a quest on the Horde to kill the same mobs you had to for an alliance quest, it will already know where those mobs are. :)
However, the new version of the DB will handle pretty much exactly what you want. The short description is that mob locations will be stored in a separate cross-faction table, so if you get a quest on the Horde to kill the same mobs you had to for an alliance quest, it will already know where those mobs are.
Or that's another way to do it. :D:D I assume that this will be the case for all objectives (drops, gears) and not just mobs. If so--very very cool.
This doesn't seem to be working for me, I have it enabled but when i finish quest objectives nothing actually happens. It worked when I First Installed it Since than, no luck.. Any ideas.
not sure if been stated, but i can't track quests normally. this really sucks because Quest_Objectives from Cartographer dosn't register QuestFu tracking, and thus i get no points on the map until i get something on the quest - then blizzard's auto tracker picks it up.
not sure where - but ive posted this in QuestFu thread under Fubar
EQL 3.7.12a is the version I am using. EQL also conflicts with the arena menu when you click on your team on the pvp tab. I have sent both of these to the author. I am going to be removing EQL3 tonight. The features of this mod outway the use of that one. I just wish someone could make a similar mod.
[2007/04/05 00:01:39-642-x1]: Cartographer_QuestObjectives\addon.lua:922: attempt to perform arithmetic on local 'numGot' (a string value)
AceEvent-2.0-30806 (FuBar):765: in function <...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:759>
<in C code>: ?
AceEvent-2.0-30806 (FuBar):427: in function <...face\AddOns\FuBar\libs\AceEvent-2.0\AceEvent-2.0.lua:403>
---
This Addon works without any problems with the German client. But when I want to share the database with my brother, there happen nothing... =/ There is no chat message and I didn't get any notes from him.
Where is the problem? Which lines I had to localize to German?
Edit: If you can help with the sharing on german clients, it would be nice, when the sharing between different clients didn't work. A lot of German people use the Englisch client =/
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Say you mouse-over 'Spider' and for the quest 'Kill Spiders' you need to kill 10 'Spiders' On the tooltip, it would be nice if it displayed 'Kill Spiders: 0 / 10'
This would also be nice on items
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis addon extends the functionality of Cartographer not your tooltip imo.
For example Clefthoof Mastery in Nagrand where you have to kill 30 Clefthoof Bull's and in the next part your just going to kill one huge Clefhoof elite.
Unfortunately WoW does not provide any sort of unique ID for quests, so I have to figure out manually what different quests are. Currently it uses the quest name and the level of the quest, which works most of the time, but as you saw in that particular quest line it didn't work perfectly. Is the second quest a group quest? In that case it will work better in the next version because I will store the type of the quest as well.
One way to overcome this would be to create a MORE unique ID for quests. Lvl+Quest+Questgiver+Objectives should do it. If a quest had multiple objectives (3 for example), it would be Lvl+Quest+Questgiver+Objective1+Objective2+Objective3.
Yeah i thought that was done already and it was bugged or somerthing. Yes it's an elite quest witch suggest 2 players.
Just thinking out loud here, this may not be a smart idea at all...
Also, id like the addon to recognize the npc that starts or ends a quest, which is also a quest target. It would be easy to copy all NPCs and its coordinates from wowhead.
I'd like to be ready so i can make sure I keep this one up to date :-)
Also any news of when we can get rid of cartographer_quests? (i hate this because the mark it gives covers over the bright yellow dot on my map for Q hand-ins)
Both of these features are planned. :D
I have thought a lot about the name. I think the first new big version will still be called Cartographer_QuestObjectives if no other reason than make upgrading the old DB simple. I will probably just change the name to QuestObjectives but I'm not sure the best way to go about doing this. I suppose I could leave Cart_QO up on the SVN as a mod that just displays a big fat message on login explaining the name change.
As for timing... I've been working on it a lot, but there's still a lot of work to be done. I figure it'll probably be a couple weeks.
If you see the work of sid67 http://www.wowace.com/forums/index.php?topic=5092.0
Its a try to get a huge DB from all quests of game but have a little problems to share these information.
First its a Huge file its time to divide the problem ?
like Alliance/Horde .lua files ?
Cartographer_QuestObjectives_Horde.lua
Cartographer_QuestObjectives_Alliance.lua
and some day need separate by level 0-40 41-60 61-70? or the file dont have size limit ?
A cool adition to mod can be a "import file" to get data from another people, like Cartographer_QuestObjectives_Import.lua once time read adn merged with correct lua can be delete.
That being said...
OverloadUT: I "DO" have some suggestions about the database..
About 50-60% of all quest are exactly the same for both Horde or Alliance characters. The questgiver is often different, but the quest title and objectives are exactly the same.
One of the things I recently did was convert quite a few of these from my Horde database to an Alliance database. The problem is that the amount of information loaded is verging on huge because of all the duplicate data from both factions when you have both in the same file.
I suggest a couple of alternative solutions:
#1) Upon receiving a new quest (or at login), search for the quest in the Faction database you are currently playing. If it's there, do nothing else and continue as normal. If it is NOT there, then begin a search in the quest database of the OPPOSITE faction. When doing this, perform a check on objectives as well to make sure it is actually the same quest. If it IS the same quest, move it to a third table called "Both". Obviously, in actual practice, the search order would be current faction, then both, then opposite faction.
- First, this cuts down on the overall size of the tables because it eliminates the duplicates.
- Second, it allows someone with a database in one faction to take advantage of quest information they have in another format.
- As noted above, while the objectives and titles are the same, the questgiver is often different. Since you plan on storing this as well, I would simply note it as ["horde"] = { ["questgiver"] = "",["turnin"] = "" } within each quest. That way, you could add other unique faction info if the need ever arised.
#2) Alternately, you could simply make the databases Load-On-Demand for each faction.
I'm not a huge advocate of the second option because I love the idea of searching the other factions quests if it's not in my faction. Right now, I am leveling an alliance toon that is 41 and a horde toon that is 47. If I complete a quest with the 47, I would love to have that recorded for the 41.
#3) You could also check the faction of the questgiver and if it's one of the Nuetral races, put it in the "Both" table.
However, the new version of the DB will handle pretty much exactly what you want. The short description is that mob locations will be stored in a separate cross-faction table, so if you get a quest on the Horde to kill the same mobs you had to for an alliance quest, it will already know where those mobs are. :)
Or that's another way to do it. :D:D I assume that this will be the case for all objectives (drops, gears) and not just mobs. If so--very very cool.
PS. Its not showing an error or anything either.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumnot sure where - but ive posted this in QuestFu thread under Fubar
Where is the problem? Which lines I had to localize to German?
Edit: If you can help with the sharing on german clients, it would be nice, when the sharing between different clients didn't work. A lot of German people use the Englisch client =/