[Challenge] Addressing Existing Confusions with the "Maximum Completions before Challenge Expires" Field
For ConsiderationFor the "Maximum Completions before Challenge Expires" field, we have observed a series of problems for new Admin users.
New Admin users tend to make the mistake of confusing this with the "How often may players complete this challenge" field. We observed that they have been setting "1" for "Maximum Completions before Challenge Expires", believing that the field actually implies "Maximum Completions Per Player".
To achieve an effect similar to having "1" for "Maximum Completions Per Player", you need only change the value of the "How often may players complete this Challenge" field to "Only once" (if your Challenge supports it).
We understand that there are other options for "How often may players complete this challenge", such as "Every hour", "Every 12 hours", etc. As an Admin user, you may also want to have a setting that is semantically similar to "We want our players to be able to complete this challenge every hour, up till their 10th completion", or "We want the challenge to expire after 10 players have completed it, regardless of the number of times each player has completed the same challenge". This is where it is trickier.
The UI/UX team is proposing the following resolution, in 2 to 3 phases:
It will take a while to modify the existing API to support the aforementioned use cases. Thus, I propose using the same API to create my prototype "I would like this challenge to expire after [ ] players have completed this challenge" field.
To use the same API but create a similar effect, this field will only be available if the "How often may players complete this challenge?" field is set to "Only once".
We are pushing for the "I would like this challenge to expire after [ ] players have completed this challenge" field in phase 1 and 2, as opposed to the "Maximum number of completions per player" field. This is because we feel that "I would like this challenge to expire after [ ] players have completed this challenge" is more semantically similar to our original implementation "Maximum completions before challenge expires".
Phase 3: Maximum number of completions per player
I will be discussing with the tech team further to see how we can roll this out, ie. what do we do about existing Challenges which already has a value set for the existing "Maximum completions before challenge expires".
-
Official comment
This post has been edited for clarity and searchability.
Comment actions -
Per my email dated 3 July 2019:
Hello all,
Sorry for digging this up. We had a UI/UX discussion today, and we will have to put this on hold for further discussions for the time being. The rationale is that I have discovered a roadblock pertaining to existing Admin users and their existing Challenge settings. This prevents me from just jumping in and changing things on the front-end. Thus, there couldn't be a Phase 1 for this approach.The roadblock is the fact that there may be existing Admin users who have the following settings: (1) a "How often may players complete this challenge?" value that is NOT "Only once", and (2) a "Maximum completions before challenge expires" value that is NOT the default "Unlimited".My Phase 1 is dependent on the fact that "I would like this challenge to expire after [ ] players have completed this challenge" is just a repurposed "Maximum completions before challenge expires" setting that is only displayed if "How often may players complete this challenge?" is set to "Only once".In order for this repurposing of "How often may players complete this challenge?" to happen:- We will need to reset the either or both values for the existing Admin users who have already had Challenges with (1) a "How often may players complete this challenge?" value that is NOT "Only once", and (2) a "Maximum completions before challenge expires" value that is NOT the default "Unlimited".
- Identify said users, and communicate these changes.
This requires cross-functional coordination between the Marketing/CS and backend/DB teams, whom are unfortunately tied up with client projects at the moment. Additionally, such a reset may also result in other settings conflicts that we have not yet envisioned.Thank you for your patience, and I apologise for the inconvenience caused.
Please sign in to leave a comment.
Comments
3 comments