TrackNextActivityForZoneStory() acts like "show on map"

[Masteroshi430]

TrackNextActivityForZoneStory(ZoneID, nil, false) acts like "show on map" if the zone story activity is already in the quest tracker/journal, is there a way to check that before casting it to avoid the unnecessary worldmap opening?

[Baertram]

Does not look like there is any way. At least ZOs code neither checks it up in advanced.
Maybe you can check th quest jorunal before calling that func via

	
	
* CanZoneStoryContinueTrackingActivitiesForCompletionType(*integer* _zoneId_, *[ZoneCompletionType|#ZoneCompletionType]* _zoneCompletionType_)
** _Returns:_ *bool* _canContinueTracking_

* IsJournalQuestIndexInTrackedZoneStory(*luaindex* _journalQuestIndex_)
** _Returns:_ *bool* _isInTrackedZoneStory_

and if it's done already or in your questlog do not call the func?

If this does not work I would had expected the 3rd parameter TrackNextActivityForZoneStory to control the map shwing or not. Maybe this is a bug.
Try to ask ZOs_DanBatson here https://gitter.im/esoui/esoui or here https://www.esoui.com/forums/forumdisplay.php?f=187

[Masteroshi430]

Originally Posted by Baertram * CanZoneStoryContinueTrackingActivitiesForCompletionType(*integer* _zoneId_, *[ZoneCompletionType|#ZoneCompletionType]* _zoneCompletionType_) ** _Returns:_ *bool* _canContinueTracking_

this one doesn't work in that case

* IsJournalQuestIndexInTrackedZoneStory(*luaindex* _journalQuestIndex_)
** _Returns:_ *bool* _isInTrackedZoneStory_

I will try that one but I will have to check all quest indexes in a loop if I understand properly,
a IsTrackedZoneStoryInJournalQuest() would have come handy

[ZOS_DanBatson]

It's because of this in QuestTracker.lua

local function OnZoneStoryQuestActivityTracked(eventId, questIndex)
    self:ForceAssist(questIndex)
    ZO_WorldMap_ShowQuestOnMap(questIndex)
end

trackerPanel:RegisterForEvent(EVENT_ZONE_STORY_QUEST_ACTIVITY_TRACKED, OnZoneStoryQuestActivityTracked)

You'd have to override that event on FOCUSED_QUEST_TRACKER.trackerPanel if you wanted to stop that vanilla behavior. Active quests don't use setAutoMapNavigationTarget at all, so that argument doesn't mean anything for that context. SetAutoMapNavigationTarget is relevant for non-breadcrumbed quests only.