Scoring summary for card games
@corinnewo is already working on this.
Since Mar 20, 2023.
- Dominant language
- Rust
- Stars
- 14
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Here are the decisions we made at ideation regarding the scoring:
-
Matching - scoring should be according to the item being dragged, not according to the top row.
-
There are now 2 types of scoring - coins and the actual percentage - coins are for motivating the children, percentage is for teacher.
-
Score within JIG will be in coins (Gali has changed the score tab to reflect this) - please use 100 coins at a time, not just 1, so that there is a nice amount of coins at the end!
-
If the JIG has scoring, but the activity does not have scores (like in poster, cover), then there is a tab shown in the google sheet, with thumbnail, but no score - could us '-' or a checkmark
-
At the end of the activity, need to emphasize the score - (Emphasize the points, add sounds, 'tongue' of the score comes in a little)
-
Final screen of whole JIG - will show total of all coins, as well as a percentage. If under 60%, don’t ever show the percentage.
-
Listen and learn - will get a thumbnail in the spreadsheet, and 2 points every time they click something
Regular mode
- Coins accumulate - Can replay and coins get more
- After each time they replay, the percentage appears briefly with a sound over the coins
- Teacher table - will get an average of the score for each activity, if activity is repeated.
- Show average percentage and all coins on the last screen
Assessment mode:
- Student can only do an activity once: Can’t replay and can’t go backwards
- Coins do accumulate
- Show percentage on the last screen
- Teacher table - gets the score for each activity (student will add in their name before playing so that teacher knows who played)
Scoring table: https://docs.google.com/document/d/1GfR48JcLd1ZJMUOh8pHoGaZ3BEWItzd8cK4rzdjFx9c/edit
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.