<onlyinclude>
The [[Game Metadata]] file should contain the essential details about a game. For example: title, developer, publisher, description, genre, URL(s) to buy or download, etc. We should include information that would be useful to a potential player when browsing games to check out, so we can look at existing platforms like Steam and itch.io for inspiration.

We'll need to decide exactly which details we want to include and how they should be represented in JSON.</onlyinclude>

== Considerations ==

Some details will be relatively straightforward to represent (e.g. title is a string property) but others will require more discussion (e.g. is genre a string property? an array of strings? an id/enum of some kind? does it need its own property or should be it be lumped into a more generic property like "tags" the way Steam handles it?).

Even a simple detail like game title may not be as straightforward as it first appears. Should the metadata include localized titles when available? If so, how does that change the JSON format?

=== Localization ===

The metadata schema should provide a way to include localized properties. You should also be able to specify what language the base properties are in. We shouldn't assume the base language will always be English.

<syntaxhighlight lang="JSON">
{
"title": "洞窟物語",
"language": "jp",
"localization":
[
{
"language": "en",
"title": "Cave Story"
}
]
}
</syntaxhighlight>

== Contents ==

{| class="wikitable"
|+ Metadata Contents
|-
! Item !! JSON Name !! Type !! Notes
|-
| Title || "title" || String ||
|-
| Description || "description" || String ||
|-
| Developer || "developer" || String ||
|-
| Publisher || "publisher" || String ||
|-
| Links || "links" || String Array || URLs to personal websites or store pages
|-
| Genre || "genre" || String Array ||
|-
| Tags || "tags" || String Array ||
|-
| Cover Art || "coverArt" || String || URL to an image
|-
| Screenshots || "screenshots" || String Array || URLs to images
|-
| Trailers || "trailers" || String Array || URLs to videos
|-
| News Feed || "newsFeed" || String || URL for an RSS feed for news/updates about the game
|}

=== Possible Inclusions ===

==== Price ====

Game price is an important detail when considering games to buy. However, there are some challenges with including price in the metadata:

* Multiple currencies (which ones to include?)
* Price differences between platforms (for games that are available in multiple places)
* Temporary discounts
* Multiple SKUs (e.g. standard edition vs special edition)

Maybe we can specify a means of including the price anyway, but try to make sure there's a disclaimer of some kind in applications that surface this data?

==== Age Rating ====

Need to investigate best practices around game ratings. Many small indie games won't have ratings data though. In that case, should we include a way to specify a custom rating?

== Example ==

<syntaxhighlight lang="JSON">
{
"title": "Hollow Knight",
"description": "Forge your own path in Hollow Knight! An epic action adventure through a vast ruined kingdom of insects and heroes. Explore twisting caverns, battle tainted creatures and befriend bizarre bugs, all in a classic, hand-drawn 2D style.",
"developer": "Team Cherry",
"publisher": "Team Cherry",
"links": [
"https://www.hollowknight.com/",
"https://store.steampowered.com/app/367520/Hollow_Knight/",
"https://www.gog.com/en/game/hollow_knight"
],
"genre": [
"Metroidvania",
"Platformer",
"Singleplayer"
],
"tags": [
"2D",
"Indie",
"Exploration"
]
}
</syntaxhighlight>

Game Metadata Contents

2025-08-18T01:52:02Z

Tom Voros: /* Contents */

Game Metadata

2025-08-18T01:43:02Z

Tom Voros: /* Potential Issues */

<onlyinclude>
Game developers could add to their websites a simple metadata file that contains all the essential details about their game(s) in a format that is easy to parse and aggregate by potential websites/services/tools/clients.

By standardizing the location and format of this metadata we can facilitate automated discovery processes (e.g. the development of scraping tools) and aggregation (e.g. building a library of games in a database).

By having developers host these metadata files themselves we give them ownership of the details of their games, how they're presented (to some degree), and where to drive interested players to download or purchase their games.</onlyinclude>

== Metadata Format ==
JSON is easy to read and write both in code and by hand which makes it a reasonable choice. Specifically, we should use [https://json5.org/ JSON5] for the added features.

== Metadata Contents ==
{{:Game Metadata Contents}}

Please see the [[Game Metadata Contents]] page for the detailed contents.

== Distribution ==
There are many potential ways that a game metadata file could be distributed but keeping in mind the objective of discoverability we should start with web-based distribution.

=== Well-known URI ===
There's an established standard for web-based metadata files being stores in a special [https://en.wikipedia.org/wiki/Well-known_URI .well-known subfolder]. We could add a new file here with a standardized name (e.g. <code>game-metadata.json</code>) to make the game metadata easy to find.

=== HTML Meta Tags ===
The metadata file could also be linked to a webpage using a <code><link></code> or <code><meta></code> tag in the <code><head></code> section. For example:

<code><link rel="alternate" type="application/game+metadata" href="game-metadata.json" /></code>

=== Included in Game ===
The metadata file could even be included in the distribution of the game itself. This could be useful in the development of game launchers.

== Metadata Applications ==
How will these metadata files be used? We probably shouldn't be very prescriptive about this, at least not from the perspective of defining the game metadata.

However, here are some possible ways that the data could be used:
* Building a web crawler that automatically discovers game metadata throughout the web to compile a comprehensive database.
* Building a curated index of games where developers can submit their games as metadata files or links.
* Using an index of game metadata (possibly compiled by another party) to build a website that resembles familiar platforms like Steam (except users will need to navigate to the developer website to make a purchase).
* Similar to the above but extended to a desktop game launcher.

Please use the [[Game Metadata Applications]] page to discuss this topic in more detail.

== Potential Issues ==
==== Bad actors could publish metadata files for other people's games ====
For example, a bad actor could publish a game metadata file with a link to malicious websites, even for a game they didn't make. If this malicious metadata is picked up by indexes/catalogs/search engines it could mislead players into thinking this is the official website for this game.

==== The Game Metadata file could be taken down ====
The original metadata file could be taken down for different reasons and we may want to differentiate between them.

* The developer wants to delist their own game
** We'll probably need a delisting process on the application side, or a special flag within the metadata to indicate a delisting request.
* The developer has moved their metadata file to a new location
* The host deleted the metadata file (and/or the entire website)

In general, we'll want to implement a reliable means of determining the developer's intent and react appropriately.

Game Metadata

2025-08-18T01:29:00Z

Tom Voros: /* Metadata Applications */

<onlyinclude>
Game developers could add to their websites a simple metadata file that contains all the essential details about their game(s) in a format that is easy to parse and aggregate by potential websites/services/tools/clients.

By standardizing the location and format of this metadata we can facilitate automated discovery processes (e.g. the development of scraping tools) and aggregation (e.g. building a library of games in a database).

By having developers host these metadata files themselves we give them ownership of the details of their games, how they're presented (to some degree), and where to drive interested players to download or purchase their games.</onlyinclude>

== Metadata Format ==
JSON is easy to read and write both in code and by hand which makes it a reasonable choice. Specifically, we should use [https://json5.org/ JSON5] for the added features.

== Metadata Contents ==
{{:Game Metadata Contents}}

Please see the [[Game Metadata Contents]] page for the detailed contents.

== Distribution ==
There are many potential ways that a game metadata file could be distributed but keeping in mind the objective of discoverability we should start with web-based distribution.

=== Well-known URI ===
There's an established standard for web-based metadata files being stores in a special [https://en.wikipedia.org/wiki/Well-known_URI .well-known subfolder]. We could add a new file here with a standardized name (e.g. <code>game-metadata.json</code>) to make the game metadata easy to find.

=== HTML Meta Tags ===
The metadata file could also be linked to a webpage using a <code><link></code> or <code><meta></code> tag in the <code><head></code> section. For example:

<code><link rel="alternate" type="application/game+metadata" href="game-metadata.json" /></code>

=== Included in Game ===
The metadata file could even be included in the distribution of the game itself. This could be useful in the development of game launchers.

== Metadata Applications ==
How will these metadata files be used? We probably shouldn't be very prescriptive about this, at least not from the perspective of defining the game metadata.

However, here are some possible ways that the data could be used:
* Building a web crawler that automatically discovers game metadata throughout the web to compile a comprehensive database.
* Building a curated index of games where developers can submit their games as metadata files or links.
* Using an index of game metadata (possibly compiled by another party) to build a website that resembles familiar platforms like Steam (except users will need to navigate to the developer website to make a purchase).
* Similar to the above but extended to a desktop game launcher.

Please use the [[Game Metadata Applications]] page to discuss this topic in more detail.

== Potential Issues ==
==== Bad actors could publish metadata files for other people's games ====
For example, a bad actor could publish a game metadata file with a link to malicious websites, even for a game they didn't make. If this malicious metadata is picked up by indexes/catalogs/search engines it could mislead players into thinking this is the official website for this game.

Tom Voros: Created page with "<onlyinclude> The metadata file should contain the essential details about a game. For example: title, developer, publisher, description, genre, URL(s) to buy or download, etc. We should include information that would be useful to a potential player when browsing games to check out, so we can look at existing platforms like Steam and itch.io for inspiration. We'll need to decide exactly which details we want to include and how they should be represented in JSON.</onlyin..."

Game Metadata

2025-08-17T22:11:34Z

Tom Voros: Created page with "<onlyinclude> Game developers could add to their websites a simple metadata file that contains all the essential details about their game(s) in a format that is easy to parse and aggregate by potential websites/services/tools/clients. By standardizing the location and format of this metadata we can facilitate automated discovery processes (e.g. the development of scraping tools) and aggregation (e.g. building a library of games in a database). By having developers host..."

<onlyinclude>
Game developers could add to their websites a simple metadata file that contains all the essential details about their game(s) in a format that is easy to parse and aggregate by potential websites/services/tools/clients.

By standardizing the location and format of this metadata we can facilitate automated discovery processes (e.g. the development of scraping tools) and aggregation (e.g. building a library of games in a database).

By having developers host these metadata files themselves we give them ownership of the details of their games, how they're presented (to some degree), and where to drive interested players to download or purchase their games.</onlyinclude>

== Metadata Format ==
JSON is easy to read and write both in code and by hand which makes it a reasonable choice. Specifically, we should use [https://json5.org/ JSON5] for the added features.

== Metadata Contents ==
{{:Game Metadata Contents}}

Please see the [[Game Metadata Contents]] page for the detailed contents.

== Distribution ==
There are many potential ways that a game metadata file could be distributed but keeping in mind the objective of discoverability we should start with web-based distribution.

=== Well-known URI ===
There's an established standard for web-based metadata files being stores in a special [https://en.wikipedia.org/wiki/Well-known_URI .well-known subfolder]. We could add a new file here with a standardized name (e.g. <code>game-metadata.json</code>) to make the game metadata easy to find.

=== HTML Meta Tags ===
The metadata file could also be linked to a webpage using a <code><link></code> or <code><meta></code> tag in the <code><head></code> section. For example:

<code><link rel="alternate" type="application/game+metadata" href="game-metadata.json" /></code>

=== Included in Game ===
The metadata file could even be included in the distribution of the game itself. This could be useful in the development of game launchers.

== Metadata Applications ==
How will these metadata files be used? We probably shouldn't be very prescriptive about this, at least not from the perspective of defining the game metadata.

However, here are some possible ways that the data could be used:
* Building a web scraper that automatically discovers game metadata throughout the web to compile a comprehensive database.
* Building a curated index of games where developers can submit their games as metadata files or links.
* Using an index of game metadata (possibly compiled by another party) to build a website that resembles familiar platforms like Steam (except users will need to navigate to the developer website to make a purchase).
* Similar to the above but extended to a desktop game launcher.

Please use the [[Game Metadata Applications]] page to discuss this topic in more detail.

== Potential Issues ==
==== Bad actors could publish metadata files for other people's games ====
For example, a bad actor could publish a game metadata file with a link to malicious websites, even for a game they didn't make. If this malicious metadata is picked up by indexes/catalogs/search engines it could mislead players into thinking this is the official website for this game.

Main Page

2025-08-17T22:11:20Z

Tom Voros:

The Game Discovery Project is an open, collaborative project aiming to assist game developers improve the discoverability of their games with a reduced dependency on existing major platforms.

This project could include various initiatives but is initially focused on a very simple idea: a standardized game metadata format.

== Game Metadata ==

{{:Game Metadata}}
Please see the [[Game Metadata]] page for further details.

== FAQ ==

==== Who made this? ====
The project was started by [https://bsky.app/profile/tom.voros.ca Tom Voros], an indie game developer.

==== Why? ====
The idea for a more open approach to game discovery was motivated by the [https://www.theverge.com/games/715299/itchio-games-delisting-payment-processor-paypal delisting of numerous games on Steam and itch.io] by payment processors in July 2025.

I saw some developers push for a more direct distribution model, selling games from their personal websites, and using the payment methods of their choice. The major downside of this approach is that you lose the discoverability of having your game on the major platforms. I wanted to think of alternative, more distributed, and more resilient methods to provide discoverability.

==== Can I join the project? ====
Yes! I believe this can only work as a collaborative project. Please reach out on [https://bsky.app/profile/tom.voros.ca Bluesky] or [https://mastodon.world/@apparition Mastodon].

==== Can I provide feedback or suggestions? ====
Of course! I consider everything about this project open to change (at least at this early stage).