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
The endpoint accepts a user id and in return gives a list of available rewards. Each reward will have an image url, name, description (describing requirements and such) as well as the url that links to the download of the reward. Rewards will be sabers, banners, etc.
Now, checking if a reward is unlocked or not must be handled on a case by case basis depending on the event (like finishing x songs in the pool). Other considerations need to be made as well like if we want to open source this endpoint or not, it can be hidden and obfuscated or it is openly available but as an honour system where we assume everyone follows the rule.
The text was updated successfully, but these errors were encountered:
The endpoint accepts a user id and in return gives a list of available rewards. Each reward will have an image url, name, description (describing requirements and such) as well as the url that links to the download of the reward. Rewards will be sabers, banners, etc.
Now, checking if a reward is unlocked or not must be handled on a case by case basis depending on the event (like finishing x songs in the pool). Other considerations need to be made as well like if we want to open source this endpoint or not, it can be hidden and obfuscated or it is openly available but as an honour system where we assume everyone follows the rule.
The text was updated successfully, but these errors were encountered: