-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Locking #19
Comments
Locking, as in making the achievement unable to be completed but allowing everyone that already has it to keep it? |
Still not an existing feature. I'll set this as a feature request and work on it! |
I meant opposite of unlocking. For example if user unlocked achievement for completing all exercises in category and there is new one added, then I want to revoke his achievement. |
Currently the API does not expose a way to lock an achievement again. But I have a suggestion on how you should proceed in your use case. The function that checks if an achievement is unlocked do the following checks:
In your use case, you are adding a new exercise and want the users to reach this new progress point in order to unlock the achievement. Assuming that you're tracking the progress numerically (i.e. you have X exercises and set the achievement to be unlocked with X progress points) his is how I suggest you do it:
If that's not clear, please let me know. |
I am looking for a way to lock achievement. Is is possible?
The text was updated successfully, but these errors were encountered: