Race to 100% completion with friends
A race to 100% completion with friends is a challenge to finish the same agreed achievement list before your rival. Choose the same game, platform list and starting condition, then compare recorded achievement completion while playing on your own schedules. Here, 100% means the full agreed achievement list; an in-game completion counter or finishing the story is a different finish line.
Agree on the finish before anyone starts
Choose the exact list you will compare, including whether extra content belongs in the challenge. If you exclude part of a list, call the goal completion of that subset; do not describe it as the full tracked hundo. OppsCity tracks achievement completion, and a private agreement does not change its displayed total.
For a fresh-start race, both players should begin without earned achievements on that list. If one already has progress, either accept the head start explicitly or choose a pace duel that compares gains from each player’s starting position. Agree how to handle any change to the list before declaring a winner.
Use the same evidence standard for both players. Platform-synced progress is verified; manual check-offs remain self-reported. The verification guide explains that distinction.
Follow a race from the start to the receipt
This is an illustrative rivalry between @example-one and @example-two, not a real result. It supplies no product percentages or achievement names.
| Stage | Agreed rule and example outcome |
|---|---|
| Start | Both players begin with no earned achievements on the same agreed list. They race to complete that entire list using platform-synced evidence. |
| Early lead | @example-one moves ahead in recorded achievement completion. Being ahead is provisional; it is not a win. |
| Pass | @example-two goes from behind to strictly ahead on the same completion measure. Drawing level would be a tie, not a pass. |
| Finish | @example-two completes the agreed list first, with evidence sufficient to establish the order. @example-one still has an unearned entry. |
| Receipt | The players check the recorded result and share a receipt showing completion and rivalry events without achievement names. They explain the agreed finish separately. |
Settle close finishes using evidence
Check Tracker for recorded progress, Radar for the rivalry position and Beef Feed for activity. A screen checked earlier is not proof of an earlier unlock: sync and play happen at different times. If the available platform evidence cannot establish who finished first, record a tie or an unresolved finish under your agreed rule. Do not turn a refresh order into a winning time.
A receipt records the tracked result. It does not certify that every private rule was followed, and it does not make self-reported progress verified. Review what receipts prove before sharing.
Find the other formats in the competition hub, or use how OppsCity works to connect the race to the tracking workflow.
Give your next race to the hundo a rival and a result worth keeping.