-
Notifications
You must be signed in to change notification settings - Fork 4
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
displaying score and best time #51
Comments
4/7/16 dev meeting decisions:
Yes.
Last score.
When timer is on and you have a perfect score, show the best time for any perfect score.
No. |
Reopening. I'm responsible for 3 sims where this is an open (non-blocking) issue:
While #51 (comment) was the dev team consensus, there are other thoughts from @kathy-phet in phetsims/graphing-lines#61 (comment). And according to phetsims/graphing-lines#61 (comment), this is on @amanda-phet's list as a design issue. |
Discussed briefly 12/7/23 (and we will have a more definitive discussion next week) but @arouinfar @marlitas @ariel-phet and I think best score and best time are the most logical decisions for what to display. |
Discussed 12/15/23 with @ariel-phet @arouinfar @amanda-phet @marlitas @pixelzoom @kathy-phet We would like to prioritize consistency between sims, as much as possible. Showing best score is the most logical, and moving forward we'd like to only show best score. Regarding time, we think it's ok to keep a clock option to time yourself playing a level (optional for sims and games), and you can see your time upon completing of a level, but we agree we should not show any times on the level selection screen. |
@ariel-phet requested that this be relocated from phetsims/balancing-act#63.
Things to discuss:
(1) Do all games need to behave the same wrt score and best time?
(2) Should 'best score' or 'last score' be shown on the level selection screen?
(3) When should best time be shown on the level selection screen?
(4) Should we show best time in the scoreboard, next to the current time?
The text was updated successfully, but these errors were encountered: