[GH-ISSUE #329] Feature Request: Add dedicated "Edition" field to Game Metadata #164

Open
opened 2026-02-17 17:06:18 -05:00 by yindo · 0 comments
Owner

Originally created by @Jeansy91 on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/329

I would like to propose the addition of a dedicated, optional field for the game Edition. Currently, specific release information (such as Definite Edition, Game of the Year Edition, or Complete Edition) must be tucked away inside the Markdown description, where it is easily overlooked.

Proposed Solution

Introduce a new, optional metadata field called "Edition". This field would:

  • Stand alone: Be a separate string field, independent of the game title and the description block.
  • UI Integration: Display the edition clearly in the game details view (e.g., as a subtitle or a badge near the title).
  • Alternative Approach: This could also be implemented as an extension of the existing versioning system, allowing users to specify the edition alongside or as part of the version number.

Use Case

While not everyone collects multiple versions of the same game, knowing the specific edition is crucial for understanding what is included. For instance, seeing "Gold Edition" or "Director's Cut" immediately tells the user that certain expansions or visual upgrades are part of the package, without them having to read through a long description text to find out.

Potential Implementation Details (Suggestions)

  • Metadata: A simple string field edition within the game object.
  • UI: Place the input field directly below the "Title" field in the "Edit Game" modal.
  • Formatting: In the library view, the edition could be rendered in a slightly smaller font or a different color to maintain a clean hierarchy.
  • Optionality: The field should be entirely optional; if left empty, no placeholder or empty label should appear in the UI.
Originally created by @Jeansy91 on GitHub (Jan 23, 2026). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/329 I would like to propose the addition of a dedicated, optional field for the game **Edition**. Currently, specific release information (such as *Definite Edition*, *Game of the Year Edition*, or *Complete Edition*) must be tucked away inside the Markdown description, where it is easily overlooked. ### Proposed Solution Introduce a new, **optional** metadata field called **"Edition"**. This field would: * **Stand alone:** Be a separate string field, independent of the game title and the description block. * **UI Integration:** Display the edition clearly in the game details view (e.g., as a subtitle or a badge near the title). * **Alternative Approach:** This could also be implemented as an extension of the existing versioning system, allowing users to specify the edition alongside or as part of the version number. ### Use Case While not everyone collects multiple versions of the same game, knowing the specific edition is crucial for understanding what is included. For instance, seeing **"Gold Edition"** or **"Director's Cut"** immediately tells the user that certain expansions or visual upgrades are part of the package, without them having to read through a long description text to find out. ### Potential Implementation Details (Suggestions) * **Metadata:** A simple string field `edition` within the game object. * **UI:** Place the input field directly below the "Title" field in the "Edit Game" modal. * **Formatting:** In the library view, the edition could be rendered in a slightly smaller font or a different color to maintain a clean hierarchy. * **Optionality:** The field should be entirely optional; if left empty, no placeholder or empty label should appear in the UI.
yindo changed title from Feature Request: Add dedicated "Edition" field to Game Metadata to [GH-ISSUE #329] Feature Request: Add dedicated "Edition" field to Game Metadata 2026-06-05 14:21:50 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop#164