Compare game progress with friends in a pace duel
To compare game progress with friends fairly when you start at different completion levels, record each player’s starting achievement completion and compare the gain over the same time window. This is a pace duel: end completion minus starting completion determines the gain. It measures progress during the window, not who has the highest total or who plays most efficiently per hour.
Choose the comparison you actually want
Use the same game and achievement list so that the completion measures refer to the same inventory. Agree on the opening and closing time, including the time zone, and retain both starting records. Without a baseline, you can compare current totals but cannot reconstruct a fair gain comparison.
| Measure | What it answers | Limit |
|---|---|---|
| Current completion | Who is further through the tracked list? | A head start stays in the total. |
| Change in completion | Who gained more during the agreed window? | It does not account for hours played or difficulty of remaining unlocks. |
| Unlock order | Who reached an agreed milestone first? | It needs evidence that establishes the order. |
When comparing completion percentages, subtract the starting percentage from the ending percentage and describe the result in percentage points. Keep the underlying list fixed. A list change or missing baseline makes the comparison unreliable; agree to restart the window or leave it unresolved instead of inventing a correction.
Work through a duel with unequal starts
This illustrative example uses @example-one and @example-two. No actual product percentages or real player results are asserted.
| Moment | Example rivalry |
|---|---|
| Opening record | @example-one starts ahead in total completion. Both players retain their own synced baseline for the same list and window. |
| Rule | The larger increase from the player’s own baseline wins. Equal increases are a tie. |
| Mid-window comparison | @example-two’s gain moves from below @example-one’s gain to above it. This is a lead change under their private pace rule. |
| Pass distinction | @example-two remains behind in total completion, so the pace lead change is not an OppsCity completion pass. A completion pass would require overtaking the opp’s total. |
| Closing record | The closing records show @example-two gained more, while @example-one still has the higher total. @example-two wins the agreed pace duel. |
| Receipt | They share the receipt for the tracked completion position and explain the baseline comparison separately. They do not present the card as an automatic pace-duel scorecard. |
Keep the comparison reproducible
OppsCity’s Tracker, Radar and Beef Feed help you follow recorded completion and rivalry activity. This format is an agreement between players, not a claim that the app provides a custom timed scoring mode or stores your chosen start and end snapshots. Keep the records needed to apply your rule yourself.
Use a shared evidence standard. Platform-synced records are verified; manual records stay self-reported. If the boundary records are incomplete, wait for relevant evidence and agree whether it can establish progress within the window. A later total alone does not prove when its gains occurred.
A duel over a shared window measures observed progress, not equal effort. If available playtime or remaining difficulty matters more than gains, adjust your agreement before starting rather than changing the result afterward.
See how OppsCity works for the tracking loop and receipts for the proof boundary. Return to the competition hub for other ways to compare.
Put your next stretch of progress beside an opp’s, with the starting line written down.