Separate Play Status from Game Completion

📋 Summary

Split Game Progress into two independent fields:

• Play Status: Whether the user is currently playing or finished with a game

• Completion: How much of the game the user actually completed

❗ Problem

The current Game Progress field combines two different concepts.

Finishing with a game does not necessarily mean completing it. A user might reach 60% of the story and decide they are finished playing, while another user might pause at the same point with plans to return.

A single value cannot accurately represent both situations.

💡 Proposal

Introduce two independently managed fields.

Play Status

• Not Started

• Playing

• Paused

• Finished Playing

• Abandoned

Completion

• Unfinished

• Beaten

• Completed

• Mastered

• Continuous or Not Applicable

An optional completion percentage could provide additional detail.

This would support combinations such as:

• Finished Playing + Unfinished

• Finished Playing + Beaten

• Playing + 60%

• Paused + Unfinished

• Abandoned + 40%

• Finished Playing + Mastered

🧩 Automation

Automation could update each field independently:

• Launching a game could set Play Status to Playing

• Users could manually mark games as Paused, Finished Playing, or Abandoned

• Achievement integrations could update Completion without changing Play Status

• Manual selections should take priority over automatic rules

🧩 Use Cases

• Stop playing a game without claiming to have beaten it

• Pause a partially completed game and return later

• Finish the main story without completing every optional objective

• Continue playing after beating or mastering a game

• Track achievement completion separately from personal play status

📦 Benefits

• More accurately represents different playing habits

• Removes ambiguity between finishing and completing a game

• Improves backlog and active-game management

• Enables more useful filters, playlists, badges, and statistics

• Provides better information for timeline and play-history views

⚠️ Considerations

• Existing Game Progress values would need a clear migration path

• Custom progress values may require user-defined mappings

• Both fields should support filtering, bulk editing, playlists, badges, and syncing

• Completion percentages should identify whether they are manual or supplied by an external source