roippi
Developer
Current status quo: at login, load three pages of questlog.php, parse them, and store quest completion data in QuestLogRequest.java.
problems:
-three unnecessary pageloads.
-most quests are still not tracked
-character state can still get out-of-sync
solution:
Store quest completion data in preferences. (lastXXX format) Load state from preferences on login. If we visit questlog.php, parse it then and adjust preferences.
see Veracity's post here for more details.
----
The number of quests that QuestLogRequest currently parses is surprisingly small:
chatAvailable
dungeonOfDoomAvailable
whiteCitadelAvailable
friarsAvailable
blackMarketAvailable
hippyStoreAvailable
hermitHax0red (already a preference)
I envision tracking for not only the above (which are required to set availability of NPCs, stores, etc) but also pretty much every council, guild, and miscellaneous quest through freeing the king. This will allow us to close out a good number of bug reports/feature requests.
problems:
-three unnecessary pageloads.
-most quests are still not tracked
-character state can still get out-of-sync
solution:
Store quest completion data in preferences. (lastXXX format) Load state from preferences on login. If we visit questlog.php, parse it then and adjust preferences.
see Veracity's post here for more details.
----
The number of quests that QuestLogRequest currently parses is surprisingly small:
chatAvailable
dungeonOfDoomAvailable
whiteCitadelAvailable
friarsAvailable
blackMarketAvailable
hippyStoreAvailable
hermitHax0red (already a preference)
I envision tracking for not only the above (which are required to set availability of NPCs, stores, etc) but also pretty much every council, guild, and miscellaneous quest through freeing the king. This will allow us to close out a good number of bug reports/feature requests.