Self.db.global.One of the most useful addons to have – ever. Self:Print("Updating MythicPlus PlayerData with values: levelMax = ", levelMax, ", Player = ", currentRealmChar, "Event triggered was: ", event) Values: levelMax = ", levelMax, ", Player = ", currentRealmChar, "Event: ", event) Self:Print("Not Updating because MythicPlus Update was called with NIL Event. If (event ~= "CHALLENGE_MODE_MAPS_UPDATE") then C_MythicPlus.RequestRewards() end - RequestRewards() itself triggers CHALLENGE_MODE_MAPS_UPDATE event, prevent looping Possible Workaround, still need to do more testing: There's a new event MythicPlusNewWeeklyRecord (MYTHIC_PLUS_NEW_WEEKLY_RECORD), maybe this could be of some use? RequestRewards itself triggers CHALLENGE_MODE_MAPS_UPDATE, so we should avoid running into a loop.ģ.
I'm not sure where exactly this call is triggered, but as a workaround we could tell it to not update the db when event is nil?Ģ. When switching to another character, when Ailo:UpdateMythicPlus is called the first time (event is nil), GetWeekl圜hestRewardLevel() still receives the values of the previous character, even when calling RequestRewards() first. Local levelMax = C_MythicPlus.GetWeekl圜hestRewardLevel() GetWeekl圜hestRewardLevel returns level, rewardLevel, nextRewardLevel LevelMax = (levelMax > level) and levelMax or level Local _, _, level = C_ChallengeMode.GetMapPlayerStats(maps) Local maps = C_ChallengeMode.GetMapTable() [=[ leaving old code commented out in case GetWeekl圜hestRewardLevel doesn't work out If event = "CHALLENGE_MODE_MAPS_UPDATE" thenĮlseif not fChallengeModeMapsAvailable then Local fChallengeModeMapsAvailable = falseįunction Ailo:UpdateMythicPlus(event. What if we add C_MythicPlus.RequestRewards() in front of the C_MythicPlus.GetWeekl圜hestRewardLevel() call?
0 kommentar(er)
