Most achievements in a week: run a fair challenge
A most-achievements-in-a-week challenge awards the win to the player who earns the most eligible achievements within the same agreed week. Choose one game and achievement list, record what each player already owns, and count only newly earned entries inside the window. This is a player-agreed comparison of unlocks, not a custom scoring mode in OppsCity.
Write down the week and the counting rule
Set an exact opening time and a closing time with a named time zone. Use a seven-day window, include unlocks at the opening boundary and exclude those at the closing boundary. A launch-week sprint uses that same rule around the players’ chosen start; it does not depend on any particular game’s release date.
Count each eligible achievement once. Do not weight it by gamerscore, difficulty or time spent. Those would be different competitions. Choose whether the full list or a stated subset is eligible, and make sure both players can identify the same scope without revealing secret names.
A shared fresh start is easiest to judge. If players already have different unlocks, retain their opening records and acknowledge that they have different opportunities remaining. For comparing changes from unequal starting totals, consider a pace duel.
Follow an illustrative weekly rivalry
This is a fictional example for @example-one and @example-two, not a real result or a claim about an achievement catalog. No product counts or percentages are supplied.
| Boundary or event | Rule applied to the example |
|---|---|
| Opening | Both start without earned entries on the same eligible list. They retain the opening records and agree to use platform-synced evidence. |
| Early window | @example-one earns more eligible entries and leads the weekly count. |
| Lead change | @example-two’s eligible count moves from below to above @example-one’s count. Under the shared fresh-start, same-list conditions, a higher completion total is also a pass. Equal counts would only draw level. |
| Closing | @example-two has the larger eligible count inside the window and wins. An unlock at the closing boundary belongs outside this sprint. |
| Receipt | They share the recorded completion result after checking the evidence. Their caption identifies the agreed week; the receipt does not independently certify a custom weekly tally. |
Check unlock timing before declaring the winner
Use Tracker to review recorded progress and Beef Feed to follow rivalry activity. Count eligible entries from evidence that establishes their unlocks within the agreed window. An achievement first appearing after a sync is not, by that fact alone, proven to have been earned at the sync time.
If a delayed record establishes an eligible in-window unlock, include it under the agreed rule. If the evidence cannot establish the boundary, leave the result provisional or unresolved. Equal final counts are a tie; do not invent a last-minute tie-breaker.
Keep manual check-offs labelled self-reported, including in the caption. Avoid secret achievement names when discussing how someone pulled ahead: the receipt guide explains why result cards use completion and events instead.
Read how OppsCity works for the tracking workflow, and visit the competition hub to choose another format.
Give the next week of unlocks a clear finish and someone to compare them with.