Originally Posted by atl77
Carbonite.Quest already requests all required data (except position, but that is easily gathered from the map), but doesn't store or transmit it. Storing it wouldn't have much impact on performance, as long as it is done in an asynchronous manner (coroutine). Transmission can also be decoupled, e.g. via web browser outside of the game.
|
I think some of data is already stored in Carbonite.Quests.lua in WTF folder.
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