Petroix wrote:1. Every relog or /reloadui makes world map reset to default mode/setup. Let's say you selected fullscreen or look'n'feel mode but later have to relog or /rl. After that, you are back with default windowed world map. There are several /questie commands that requires UI reload so it can be a little bit annoying. Without Questie enabled there is no problem. It looks like Questia tried to force world map to display in specified mode or something like that.
2. If you click on any Quest Objective on world map (brown sack?) it causes lua error to pop out:
Keep up the good work man, I dream you could work on that stupid cartographer too, instead of it's author
Thanks! And OPPS! LOL...
1. I fixed the map issue. I had to make Cartographer an "Optional" dependency in order to allow the modules to work right and survive a ReloadUI() or a Re-log. In my initial test pass I had it setup as a dependency until I re-wrote the detection check. Then I removed it in one of my test passes and my code still worked but I didn't check to see if Cartographers settings would stick through a Re-load/Re-log. So opps. Dependency is back and it's all working now.
2. Another opps... it was late when I wrote this code and my brain hiccuped.
Old code:
- Code: Select all
function SetArrowObjective(hash)
if arrow_objective == hash then
wayframe:Hide();
arrow_objective = 0;
return;
end
arrow_objective = hash
local objective = QuestieTrackedQuests[hash]["arrowPoint"]
SetCrazyArrow(objective, objective.dist, objective.title)
end
The issue is the local objective - it's looking in the QuestieTrackedQuests table. Well... if the player doesn't have a quest actively "tracked" then there is no [hash] number. I changed it to look in the QuestieSeenQuests table. The [hash] will always be there regardless of status as long as it's in the players quest log.
I'm going to check in these fixes. I've already checked in a quick fix for better error handling for folks not paying attention to the release notes.
I wrote an extra check function that will look in the payers SavedVariables file for missing entries and then add them.
These fixes will have to be installed manually as there aren't enough changes to warrant a new release. Besides I'd like for you guys to test this stuff before I include it in a future release.