Quote:
|
Quote:
|
Quote:
|
Collecting quest information can slow the UI down or not depending on what information is collected. For Grail, the NPC and quest information that is gathered does not really slow anything down as it does the basic location, name, level, reputation type of thing. However, if you started recording areas where quest objectives are being satisfied (which Grail does not do), I imagine you might start slowing the user experience down. I would definitely make such collection an option so only those serious about adding to the database would sacrifice the game play for the good of all.
|
Quote:
|
Quote:
What we need to gather: - quest name + if its available quest id - quest starter (name, coords, zone) - quest ender (name, coord, zone) - quest objectives (text for each objective as ids may not be available) + maybe objectives coords like in wowdb or wowhead (but collecting this data may lower overall module performance) Storing this data localy. How we could make trasmiting this data to our server: - make an in-game notice to player if he wants to transfer his quest data to our server - this in game notice would show periodically - not in dungs, raids, bgs and not in combat - user sould have option to totally disable this notices and to set how much the time between notices - transfering data could show progress of transmiting data to our server |
Maybe create a new Carbonite. Collect Modul. So not everyone need to install.
Also, did you take a look into WoWHead Collector Addon? Maybe we can use this one for collecting these Data's |
Quote:
The thing is that some users will not install this addon, so no data gathering there. Better solution is to have it in Quests module and if user doesnt want to collect data he will just disable this option. But by default it is enabled. |
There is alao a WoW Addon and an uploader ;)
|
Quote:
|
1 Attachment(s)
http://de.wowhead.com/client it is both included
http://www.wowinterface.com/forums/a...1&d=1419786123 here the addon itself |
Quote:
|
Quote:
|
Quote:
Personally I believe the quest objective information from Blizzard APIs can be used as needed, so recording that information may not be needed. The last piece of information Blizzard now provides in its own way that may be adequate assuming you can get it to put onto the Carbonite map instead of Blizzard's maps. However, if that information cannot be gotten, this is where you need to determine it for the new quests to record for the addon. This might be recordable when you accomplish one of the objectives for a quest by noting your current location, and just make a list. Turning that list into a region instead of a bunch of points will take your gathering data from a lot of users, and either some fancy algorithms or a lot of manual region making. For single points, you should be ok. |
Quote:
Quote:
Quote:
|
I'm a sucker for fancy algorithms ;)
|
Quote:
|
The only way Carbonite can show you where are the locations of a quest givers that still have uncompleted quests for you're player is if it have them all in a DB and can check which ones are you still missing.
|
Just added pull request for Quest Data Gathering.
Added new setting in Quest Module (default its off), so please enable it to gather test data: All gathering goes to SavedVariables/Carbonite.lua. |
Quote:
BTW You should probably remove the Carbonite.Quests/NxQuest.lua.bak file from the pull request. |
All times are GMT -6. The time now is 03:06 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI