Daily tracking quests for Archiereus and Timeless Champion kills

[Hoosier269]

Since you are only able to loot the Archiereus of Flame once daily, I imagine that there is an invisible tracking quest that updates after the first time you loot him. I swap between a lot of alts and haven't done a very good job of tracking which ones have killed him so far each day, so I was wondering if anyone knew the quest ID for the tracker so that I could run it through a macro similar to world boss checks (e.g. /run for k, v in pairs({ Galleon = 32098, Sha = 32099, Nalak = 32518, Oondasta = 32519, Archiereus = XXXXX}) do print(format("%s: %s", k, IsQuestFlaggedCompleted(v) and "\124cff00ff00Yes\124r" or "\124cffff0000No\124r")) end

I had also heard a rumor that the first timeless isle rare mob looted per day has an increased drop chance of its special item/vanity drop. If anyone can confirm, I'd suspect it would work under a similar mechanic that could be tracked using a quest ID.

[Hoosier269]

After poking around a bit today I searched WoWhead for quests introduced in Patch 5.4 that have no level requirement, a criteria characteristic of quest flags. I found a lot more quests than I expected but waded through them and decided that three of the flags were worth tracking on a daily basis--Archiereus, Spritewood, and Zarhym. There are flags that track the first daily kill/completion of each rare on the island, but besides these three quests which prevent you from looting the rare a second time I could not find any use for tracking the other ones. It is possible that the loot tables change after the first kill each day but I have not been able to confirm whether that is the case. Anyways, here's the macro I made to track the three daily rares:

/run for k, v in pairs({ Spritewood = 32961, Archiereus = 33312, Zarhym = 32962}) do print(format("%s: %s", k, IsQuestFlaggedCompleted(v) and "\124cff00ff00Yes\124r" or "\124cffff0000No\124r")) end

EDIT: The macro breaks pretty easily... not sure why but I get a lot of false negatives unless I relog while resting, then it usually works.