You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue because when we need to use a count of available (completable) challenges, within a week, the function will store ALL the challenges in the season.
This value is going to be used to check for the potential to earn XP. For example, if there are no bounties present and the user has completed all their seasonal challenges, then this means their potential to earn XP is technically zero. (as far as Synergy is concerned anyways).
Just cross-reference each seasonal challenge back to its node definition, where the current week is stored to get the amount of currently-completable challenges. Store the value in a new variable.
The text was updated successfully, but these errors were encountered:
This is an issue because when we need to use a count of available (completable) challenges, within a week, the function will store ALL the challenges in the season.
This value is going to be used to check for the potential to earn XP. For example, if there are no bounties present and the user has completed all their seasonal challenges, then this means their potential to earn XP is technically zero. (as far as Synergy is concerned anyways).
Just cross-reference each seasonal challenge back to its node definition, where the current week is stored to get the amount of currently-completable challenges. Store the value in a new variable.
The text was updated successfully, but these errors were encountered: