Games
English «
For information on how to correctly enter the game details, please see Add game information, which will explain the various database standards for games. It is important that you read and follow these carefully.
Before attempting to add a game to the database, please be sure that the type of game is acceptable for inclusion in the database.
In general, if you aren't sure if a game qualifies for inclusion in the database, please first before adding it.
Note: The standards for what kind of submissions are acceptable may and probably will evolve over time. For the initial launch of Glitchwave we want to keep the scope limited to things that obviously should be part of a games database (meaning we will focus on games that fit the conventional definition of an official game release). We may expand the scope of the site later to include some of the above mentioned things that are currently not allowed. We just want to make sure that before we allow those types of entries that the site is set up to handle them correctly to avoid turning the database into a mess.
Some cartridges on consoles weren't licensed from the console makers (such as Nintendo's seal of approval). They would usually have different shapes and looks than the regular cartridges in order to bypass the console's locking system. These cartridges are still acceptable to add in the database, as long as they contain original game(s) and aren't bootleg mutlicarts or ROM hacks. Ports are also acceptable, as long as they don't break copyright laws. Beware of pirated re-releases of games, those aren't acceptable.
To avoid entering a duplicate, always begin by searching the database to ensure that the game you're about to add hasn't already been added by someone else.
If your search didn't find the game then you can go ahead and click the Submit link that appears under the 'Games' section on the side bar on the games portal page. This will take you to the entry form where you can begin submitting the game. If your search returns the game, but the specific release you want is not present in the database yet, see Adding game releases for info on how to proceed. Remember to double check the releases list, as your specific release could be in the database already but its info may not be complete or needs corrections/updates. In that case, submit a correction by clicking on "Edit" from the specific game release page.
If during your submission you receive a notification about possible duplicate entries, please verify that the game you are submitting is not any of the entries listed there before you go ahead and submit it.
Please see Add game information for specific instructions on how to enter information in each field of the submission profile.
There are three types of game entries in Glitchwave: Game, Collection and Expansion. Each type have specific particularities which define how the entry should be formatted and presented in Glitchwave.
This is the default game entry. Game entries are the base entries, which can be associated or not with collections and expansions. Most entries will fall into this category.
Collections are compilation entries, containing two or more existing games. When submitting collection entries you must enter the [GameXXX] shortcuts for every game included in them (or plain text only for cases where it's applicable, as seen below). Make sure the games are already added in the database before creating a collection entry which contains them.
Expansions are entries regarding complementary content to a game. Every expansion entry must be linked to the respective game entry they are expansion of, using the [GameXXX] shortcut. Expansions have some additional requirements to be added in Glitchwave. Not all extra-base game content that exists for a certain game is eligible to be entered as an expansion entry. As a rule of thumb, an expansion should only be entered if it presents itself as a relatively significant addition to the game.
An update or DLC which is simply a standalone new weapon, cosmetic content such as skins and costumes, or a single fighter for a fighting game are not proper expansions by Glitchwave standards. Instead, the weapon, costumes or fighter should be part of a major content pack which could be considered an eligible expansion entry to be added. This heavily depends of how the developers/publishers choose to release, promote and market the extra content for the game, being presented or not as a proper expansion pack, most of times featuring an unique title and attributes.
When in doubt, refer to to check if the community verifies the entry eligibility before adding it to the database.
A game entry can have several game releases, with each game release entry representing a different version or edition of a game. To add a new release, click on the link found in the bottom right of the release list for the game. As a general guideline, if the release you want to add have particularities that differ from the Primary release or the other releases present in the release list (such as barcodes, medias, platforms, released locations, titles, edition names, etc.), then it's eligible to be entered. Below are some points that should help identifying whether a release is eligible or not to be added.
Sometimes it is not fully clear if a certain game should be entered as a release from another existing game entry, or as a new and separated entry. This doubt usually comes up when dealing with enhanced versions, remakes, ports, reboots, console-to-handheld versions and vice-versa, games with the same names or from the same licensee brand, etc. It's not possible to decide on a specific rule regarding the remake and port terms, given their recurrent erroneous usage by the general game industry. Ultimately, games should be grouped in a single entry as long as the core game is maintained between them.
It is important to remember that Glitchwave files game releases under a container entry named "generic entry". The generic entry will carry info that is mostly applied to all releases under it. That info regards to entry type, genres, characters, franchises, soundtracks, cast and credits. All that info should be majorly compatible with all the releases under the generic entry, to avoid incorrect documentation.
Games in this situation should be decided on a case-by-case basis. Below are presented aspects favoring a game to be either filed as a release or as a separated stand-alone entry, serving as a helpful guide for verification for existence of the same core game between versions. The decision should lean in the direction of the category with the most compatible verified aspects when comparing the game in question with the existing game tree.
It is possible to quantify the compatible aspects from each category for a more precise decision. However, remember that some aspects are very relative, so common sense should be applied as best as possible according to the type of the game. If there are still uncertainties on how to proceed, see for community support. Remember that the legacy and relevance (the last aspect in both lists), could weight more than all the others aspects, depending of the situation.
These standards are made so that games can be carefully documented and tagged in the way that most makes sense for the Glitchwave userbase. Below are some generic cases and how to proceed with them.
Some games can be released in two or more alternative versions of itself, being the same core game with little difference between them. Such games releases should be grouped, with the generic entry title being modified to the generic name of the game series (see Game title for more info). For example, the Pokémon handhelds games Pokémon Red and Pokémon Blue would be grouped, with the generic game entry titled Pokémon Red & Blue for the English language.
Similar to alternate version and episodic games, some games are released in two or more parts (each one with its distinct and unique release), which complete the full game (e.g. Shin Onigashima, Higurashi When They Cry). These games should be all under the same Game tree, since they are essentially parts of the same game, with each part/chapter release being added with their own respective GameRelease.
Some online distribution services (PSN, Nintendo eShop, XBLA, GoG, Steam, etc.) release direct ports of games from other platforms for the platforms those services are available. All these games should be added as releases of the original game, with their respective platforms. These games tend to be exactly the same as the originals, sometimes featuring upscaled resolution and bug fixes.
There are fighting games which had a specific release model in which multiple re-worked editions were developed and re-released, under new and distinct labels from the previous game versions. For the purposes of these standards, such editions will be addressed as iterations. Each game iteration is a re-worked (either in minor or major scale) game version with updates, enhancements, revisions, adjusted balancing, physics and mechanics, addition/removal of features and characters, etc. Basically, the developers/publishers are responsible for defining new iterations through new release cycles, either to address game issues or to continue support and interest of their games through the years. These cases were even more common before the popularization of game patches and additional downloadable content support through online services. Known figthing game franchises with game entries with multiple iterations are Street Fighter, Guilty Gear, Dead or Alive, Mortal Kombat and Tekken.
The presentation and promotion of each new iteration allow those games to be considered semi-sequels or sister games of their previous iterations. Note that new iterations are very commonly released for the same platforms of their previous iterations, this is something which seems unimportant at first but in reality they affect a lot functionalities like platform-specific charts, depending on the manner they are handled. For accurate documentation, cataloguing and rating purposes, these iterations should be entered on Glitchwave as their own stand-alone entries. Those games need sources to prove their ability to be identified as distinct iterations before being added to the database. Note that most ports are not considered new iterations, but rather different versions of a specific iteration that should be entered as a Release under their specific iteration's Game entry.
There are rare cases where a game was entirely rebranded or redesigned while maintaining the same core gameplay, before being released in a different region. In these cases, it does not make sense to group releases, since they are most likely completely different and feature different characters/frachises/credits. The most famous case of rebranding regards to Yume Kōjō: Doki Doki Panic vs. Super Mario Bros. 2. Both games should be added as separated stand-alone entries. Other notable cases of rebranding are Panel de Pon vs. Tetris Attack, Asterix vs. Taz Atari 2600 games, and Wonder Boy in Monsterland vs. Mônica no castelo do dragão.
Built-in games refer to software that is installed or integrated by default on the platform. These games should have the media field set to "built-in", and the same release dates of the platform model/version they were included with. See Built-in releases images for the specific image standards for this type of game release.
Episodic games are released and available in parts, called episodes. These types of games should be added in their full format, as a season or series. Episodes should not be added as game releases separately. For example, only The Walking Dead: Season 1 would be added as a game entry, with all of its individual episodes not being entered in the database. Under the generic entry, retail releases and complete season packs can be added as release entries. Complete season packs are usually available from the start, together with the first episode availability, so those should be set as the primary release of the game entry. The release date for season packs should be the same as the release date of the first episode (For example, Life Is Strange game entry would have January 30, 2015 as release date). Retail releases (if existant) should be entered with their own release dates, which most of the time will differ from the individual episodes release dates. Remember that certain games are marketed as episodic games, though they are not released in actual parts, seasons or series. Such games should have its "episodes" added as separated, normal games entries (e.g. Sonic the Hedgehog 4: Episode I and Sonic the Hedgehog 4: Episode II)
Contents |
Acceptable content
Before attempting to add a game to the database, please be sure that the type of game is acceptable for inclusion in the database.
Acceptable
- Games that have had an official release on at least one specific platform
- Games that have been officially made available by the developers/publishers as full-featured games, even if they are considered to be in alpha/beta stage of development (e.g. Dungeon Crawl Stone Soup, Dwarf Fortress)
- Games that have been officially announced by the developer/publisher and which have an announced release date within a year from now (so if it's March 2016 you can add any games announced for March 2017 or earlier). If a game's release is further off than that (or entirely unknown), do not add it to the database yet.
Unacceptable
- Unreleased games with no official release date
A game must have an officially announced release date before it can be eligible for entry in the database. This is to avoid cluttering the database with games that are still years away from coming out, or that will never come out at all. - Games unofficially released/available
Certain games that were cancelled and/or never officially released nor available can be acquired through the circulation of ROM images of prototypes and beta/alpha builds, sometimes with unofficial patches. As long as the availability of such ROM images or builds is unofficial, these games should not be added to the database (e.g. Star Fox 2, Resident Evil for GBC, Space Fantasy Zone) - Games released by yourself or by your friends, with the exception of officially-licensed console games released before 2007
You should generally not add games that you created yourself or that were created by your friends. If they meet notability standards for inclusion in Glitchwave, then someone who is not associated with you will eventually add it to the site. There is an exception, however: you are permitted to add games if they were released on a standalone console system, officially-licensed by the maker of that console, and released before 2007. - Hobby/personal projects without significant notability
Games that are created as a hobby or personal project, including games which are based on game engines such as RPG maker are generally not permitted to be added unless they already have significant notability or are published on a curated distribution platform. Exceptions can be made on a case-by-case basis; post in the thread linked below to ask for an exception or if you are unsure whether a game falls under this criteria. - Games that are not video games
While we use the word "games" as a short hand a lot, this is a video games database. Anything that can't reasonably be considered a video game should not be submitted (so no board games, card games, pachinko, pinball and slot machines, etc.) - Games that have no suitable platform in the list
If the game you want to add wasn't released on one of the platforms in the list, do not add it (yet). You can try suggesting the platform and if it meets our criteria we'll add it so you can add the game afterwards. Games that have no platform as such, like standalone handheld games (Tamagotchis, etc.) are not eligible for inclusion in the database. - Mods
Mods (modifications) are usually third-party creations that are based off an existing game and which use that game's engine (and often assets), and which require the existing game in order to play them. Often mods are created using the official tools/SDK released by the developer of the game, but even games with no official tool sets have had mods developed by people who figured out the file formats, scripting, etc. on their own. For the time being, mods are not acceptable to add to the database, even if they are total conversions that bear no resemblance to the original game. We might consider expanding the database scope to allow inclusion of mods at some point in the future.
Additionally, any other games which might not be considered a mod, but still require an existing game or software in order to play them shouldn't be added at this time.
Occasionally games start out as a mod but are later turned into official standalone games. Once that point is reached they become eligible to be in the database like any other game. Some notable examples of this are Counter-Strike and Day of Defeat, which started out as Half-Life mods but were later bought and released as stand-alone products by Valve. - Unnofficial ROM hacks
ROM hacks are essentially modifications of existing games' ROM images. Unofficial ROM hack games should not be added to the database at this time. - Unofficial/bootleg multicarts
Bootleg multicarts are usually compilations of two or more games (sometimes including clones and ROM hacks), available in an unofficially issued single cartridge. Such game releases are not eligible as collection entries and should not be added to the database at this time. - Demos
Demos and shareware of existing released games are not proper full games, so these should not be added to the database, same goes for free or "lite" versions of full iOS/Android games. Remember that games that can stand on their own despite being considered teasers of other games (e.g. P.T.) are allowed.
In general, if you aren't sure if a game qualifies for inclusion in the database, please first before adding it.
Note: The standards for what kind of submissions are acceptable may and probably will evolve over time. For the initial launch of Glitchwave we want to keep the scope limited to things that obviously should be part of a games database (meaning we will focus on games that fit the conventional definition of an official game release). We may expand the scope of the site later to include some of the above mentioned things that are currently not allowed. We just want to make sure that before we allow those types of entries that the site is set up to handle them correctly to avoid turning the database into a mess.
Unlicensed
Some cartridges on consoles weren't licensed from the console makers (such as Nintendo's seal of approval). They would usually have different shapes and looks than the regular cartridges in order to bypass the console's locking system. These cartridges are still acceptable to add in the database, as long as they contain original game(s) and aren't bootleg mutlicarts or ROM hacks. Ports are also acceptable, as long as they don't break copyright laws. Beware of pirated re-releases of games, those aren't acceptable.
Steps for adding a game
Search for the game
To avoid entering a duplicate, always begin by searching the database to ensure that the game you're about to add hasn't already been added by someone else.
Add game
If your search didn't find the game then you can go ahead and click the Submit link that appears under the 'Games' section on the side bar on the games portal page. This will take you to the entry form where you can begin submitting the game. If your search returns the game, but the specific release you want is not present in the database yet, see Adding game releases for info on how to proceed. Remember to double check the releases list, as your specific release could be in the database already but its info may not be complete or needs corrections/updates. In that case, submit a correction by clicking on "Edit" from the specific game release page.
If during your submission you receive a notification about possible duplicate entries, please verify that the game you are submitting is not any of the entries listed there before you go ahead and submit it.
Please see Add game information for specific instructions on how to enter information in each field of the submission profile.
Determining the game entry type
There are three types of game entries in Glitchwave: Game, Collection and Expansion. Each type have specific particularities which define how the entry should be formatted and presented in Glitchwave.
Game
This is the default game entry. Game entries are the base entries, which can be associated or not with collections and expansions. Most entries will fall into this category.
Is this a game?
If the game is a stand-alone game which can be included in collections or have expansions, then it most certainly should have its entry type set to "game". Editions of the game including the base game with a selection of expansions in the same release should still be added as a game release under the generic game entry. For more information about adding and determining game releases, see Adding game releases and Should I add this as a release or a completely new entry?.
Collection
Collections are compilation entries, containing two or more existing games. When submitting collection entries you must enter the [GameXXX] shortcuts for every game included in them (or plain text only for cases where it's applicable, as seen below). Make sure the games are already added in the database before creating a collection entry which contains them.
Is this a collection?
Collection entries must be presented as collections, and contain two or more game entries. A game release edition containing the base game and all its expansions is not considered a collection; rather, it is a release that should be added under the original game's generic entry. Additionally, expansions included in a collection should not be listed, unless the expansion is originally stand-alone. Collections containing exclusively expansions (no base game) are acceptable (e.g. The Sims Expansion Collections).
It should be noted that not all releases which contain two or more games are considered collections. Certain releases could include bonus games along with the actual game, though the release itself is not considered a collection, either in separated medias (e.g. US version release of Bayonetta 2 including Bayonetta) and bonus games within the original games (e.g. Zork, a bonus game accessible by a specific method in Call of Duty: Black Ops). Games that fall under this case should be added as game releases under their respective generic game entries as long as the bonus game is distributed in a separated media, while bonus games within the original games (as unlockable bonus, easter eggs, etc.) should not be added as separated releases.
There are cases of collection releases which can't have some or any linked games because the games are not allowed to be entered in Glitchwave, either because those games are from platforms not supported by the database, or because the games were only released as part of a collection release. For these cases, the collection release should be entered normally, except those specific games (and only those games) must be entered in plain text rather than [GameXXX] shortcuts. If a game ended up being properly standalone released at a later date, then its respective [GameXXX] shortcut should be linked in the collections it appears, after the standalone entry is added to the database (e.g. RIP 3: The Last Hero from RIP - Trilogy)
It is possible for stores or distributors elaborate their own bundles or sale deals for either physical and digital games. Such bundles/sales deals are not eligible collections, since collections should be properly released as collections (developers/publishers decision) rather than being sold/distributed as a bundle by distributor channels.
Expansion
Expansions are entries regarding complementary content to a game. Every expansion entry must be linked to the respective game entry they are expansion of, using the [GameXXX] shortcut. Expansions have some additional requirements to be added in Glitchwave. Not all extra-base game content that exists for a certain game is eligible to be entered as an expansion entry. As a rule of thumb, an expansion should only be entered if it presents itself as a relatively significant addition to the game.
An update or DLC which is simply a standalone new weapon, cosmetic content such as skins and costumes, or a single fighter for a fighting game are not proper expansions by Glitchwave standards. Instead, the weapon, costumes or fighter should be part of a major content pack which could be considered an eligible expansion entry to be added. This heavily depends of how the developers/publishers choose to release, promote and market the extra content for the game, being presented or not as a proper expansion pack, most of times featuring an unique title and attributes.
When in doubt, refer to to check if the community verifies the entry eligibility before adding it to the database.
Is this an expansion?
Releases which complement or add new content for an existing game can be considered expansions. Usually, expansions need the base game to be playable, however there are cases of expansions that can be played without their base games. Some examples of stand-alone playable expansions are Half-Life: Blue Shift, Far Cry 3: Blood Dragon and New Super Luigi U. Nevertheless, such releases should still be added as expansions, and linked to their respective base games.
Adding game releases
A game entry can have several game releases, with each game release entry representing a different version or edition of a game. To add a new release, click on the link found in the bottom right of the release list for the game. As a general guideline, if the release you want to add have particularities that differ from the Primary release or the other releases present in the release list (such as barcodes, medias, platforms, released locations, titles, edition names, etc.), then it's eligible to be entered. Below are some points that should help identifying whether a release is eligible or not to be added.
Acceptable
- Multi-platform games
A single game can be released in several platforms. Each platform version should be added as a different release under the generic game entry, with its respective platform selected. Multiple-platform games should not have all the platforms it's available in a single release, see Platform for more info. - Region specific versions
Region specific physical releases should be all added separately. Usually, the same game could have different barcodes, box art, release dates, etc. for each different location where it was released. However, do not add multiple location flags in a single release in rare cases where there is no difference between releases except the location it was produced. Also remember that 'available' is not the same as 'released', so take that into consideration before adding or correcting a release. - Editions
Games often get new releases in a form of editions, such as Definitive, Collector's, Greatest Hits, Complete, GOTY, etc. Each edition should be added as a different release. In some cases new editions include bundled expansions of the game. Remember that the release dates can and most certainly will be different from the primary releases. - Updated/enhanced versions
Some games can get new releases in the form of updated or enhanced versions. This is commonly found for games that are ported for other platforms, such as Dark Souls II: Scholar of the First Sin and Sonic Adventure DX. These should be added as releases under the original Game entry. In exceptional cases, check here for more info. - Downloadable versions
If a game was released in both downloadable and physical medias in the same platform, it is allowed to add both versions as different releases. Ideally, games will have one single downloadable release for a platform. However, if the downloadable game is available under different titles on that same platform, even if the developers/publishers are the same, then those alternate titles can be added as separate downloadable releases. This is the only condition allowing additional downloadable releases for the same platform. For example, Persona 4 Arena Ultimax was released in both DL and physical formats for the PS3 in North America. In Japan, the game is titled ペルソナ4 ジ・アルティマックス ウルトラス―プレックスホールド (Persona 4: The Ultimax Ultra Suplex Hold), also released in both DL and physical formats for the PS3. The game was published by Atlus in both regions. Considering only these two regions, the game entry would have a total of four releases: the NA downloadable, the NA physical, the JP downloadable and the JP physical. Since the downloadable versions titles differ for each region the game was released, then they are allowed to be added as separated releases, with their release dates being applied accordingly. Do not add additional downloadable releases if the release dates differ while the title is the same. Since there are several digital distributors/stores services for different regions of the world, release dates may differ between them. However, Glitchwave will not support the addition of dozen of downloadable versions for each regional service. If the titles and the rest of the info are the same, only one downloadable release should be added, with the release date being set to whenever it first appeared as a download on a store/distributor.
The same rule applies to games only available in downloadable format in the same platform (no physical releases). Additional releases may be added if their titles differ. For example, ファイナルファンタジーレコードキーパー was released in Japan for the iOS, with the worldwide iOS version Final Fantasy Record Keeper being released later. In this case, the worldwide iOS Final Fantasy Record Keeper is allowed to be added as a release, with its respective release date.
Unacceptable
- Different arcade cabinets
As long as there are no gameplay, publishing, developing or location differences, like number of players or new updated editions, arcade games should be entered in a single release, even if there are several other models of arcade cabinets/machines for it. - Multiple availability of browser games
As long as there are no gameplay/publishing/developing differences, browser games should have a single release, not mattering if the game is available in several websites with their own release dates for it. Apply the first original release date for the browser game release. - Multiple digital game distributors for the same platform
Digital game distribution services for the same platform (Steam, Origin, GOG, etc.) often use their own release dates (or availability dates) in their catalog. As seen in Downloadable releases, a game should have only one downloadable/digital release in the same platform, unless titles differ. Do not add additional digital releases based on the release/availability dates from different distributors. Always use the earliest release date the game was made available.
Should I add this as a release or a completely new entry?
Sometimes it is not fully clear if a certain game should be entered as a release from another existing game entry, or as a new and separated entry. This doubt usually comes up when dealing with enhanced versions, remakes, ports, reboots, console-to-handheld versions and vice-versa, games with the same names or from the same licensee brand, etc. It's not possible to decide on a specific rule regarding the remake and port terms, given their recurrent erroneous usage by the general game industry. Ultimately, games should be grouped in a single entry as long as the core game is maintained between them.
It is important to remember that Glitchwave files game releases under a container entry named "generic entry". The generic entry will carry info that is mostly applied to all releases under it. That info regards to entry type, genres, characters, franchises, soundtracks, cast and credits. All that info should be majorly compatible with all the releases under the generic entry, to avoid incorrect documentation.
Games in this situation should be decided on a case-by-case basis. Below are presented aspects favoring a game to be either filed as a release or as a separated stand-alone entry, serving as a helpful guide for verification for existence of the same core game between versions. The decision should lean in the direction of the category with the most compatible verified aspects when comparing the game in question with the existing game tree.
Aspects favoring the game to be added as a release under an existing game
- The game has the same genres from the original game
- The game is part of the same franchises
- Game credits/cast can be applied to both games
- The game's graphics are upgraded/downgraded/alternative, while maintaining the same design (HD treatment, remastering, port, etc.)
- Gameplay and game mechanics are very or completely similar between games
- The main perspectives are still maintained (first-person, third-person, 3D, 2D, isometric, etc.)
- Story and plot are mainly the same between games, with none or minor differences
- Game progression is very or completely similar between games (rounds, levels, worlds, maps, etc.)
- Game includes/excludes minor game modes, such as minigames, difficulty setting, time trials, skirmishes, etc.
- Game features the same major characters/protagonists/playable characters
- Few minor characters, like NPCs, enemies, bosses or other minor party members are excluded or included in the game
- Level and character design are majorly similar or exactly the same between games
- Game includes/excludes none or few levels, phases, sections, areas, regions, worlds, maps, etc.
- Some ingame content like collectables, weapons, vehicles, items, etc. are included/excluded
- Menus, navigation, commands and action management are completely or very similar between games
- The individual game's legacy is not relevant enough to be separated from the existing game tree
Aspects favoring the game to be added as a separated stand-alone entry
- The game has different genres from the original game
- The game is part of another franchises, or part of an extra franchise in which the original game can't be included
- Game credits/cast cannot be applied to both games
- The game's graphics are upgraded/downgraded/alternative, and the design differs greatly from the original game
- Gameplay and game mechanics differ heavily between games
- The main perspectives are different or not present in the original game (first-person, third-person, 3D, 2D, isometric, etc.). Extra perspectives, as long as the original perspective is still present, are not considered
- Story and plot are not alike between games, with major differences. Cases of stories being "reimagined" fall under this.
- Game progression is completely different between games (rounds, levels, worlds, maps, etc.)
- Game includes/excludes several game modes
- Game features different major characters/protagonists/playable characters
- Several minor characters, like NPCs, enemies, bosses or other types of party members are included/excluded in the game
- Level and character design are very or completely different from the original game
- Game includes/excludes several levels, phases, sections, areas, regions, worlds, maps, etc.
- Several ingame content like collectables, weapons, vehicles, items, etc. are included/excluded
- Menus, navigation, commands and action management are completely or very different
- The individual game's legacy is relevant enough to be separated from the existing game tree
It is possible to quantify the compatible aspects from each category for a more precise decision. However, remember that some aspects are very relative, so common sense should be applied as best as possible according to the type of the game. If there are still uncertainties on how to proceed, see for community support. Remember that the legacy and relevance (the last aspect in both lists), could weight more than all the others aspects, depending of the situation.
These standards are made so that games can be carefully documented and tagged in the way that most makes sense for the Glitchwave userbase. Below are some generic cases and how to proceed with them.
Alternate versions
Some games can be released in two or more alternative versions of itself, being the same core game with little difference between them. Such games releases should be grouped, with the generic entry title being modified to the generic name of the game series (see Game title for more info). For example, the Pokémon handhelds games Pokémon Red and Pokémon Blue would be grouped, with the generic game entry titled Pokémon Red & Blue for the English language.
Multiple part/chapter games
Similar to alternate version and episodic games, some games are released in two or more parts (each one with its distinct and unique release), which complete the full game (e.g. Shin Onigashima, Higurashi When They Cry). These games should be all under the same Game tree, since they are essentially parts of the same game, with each part/chapter release being added with their own respective GameRelease.
Distribution services
Some online distribution services (PSN, Nintendo eShop, XBLA, GoG, Steam, etc.) release direct ports of games from other platforms for the platforms those services are available. All these games should be added as releases of the original game, with their respective platforms. These games tend to be exactly the same as the originals, sometimes featuring upscaled resolution and bug fixes.
Fighting game iterations
There are fighting games which had a specific release model in which multiple re-worked editions were developed and re-released, under new and distinct labels from the previous game versions. For the purposes of these standards, such editions will be addressed as iterations. Each game iteration is a re-worked (either in minor or major scale) game version with updates, enhancements, revisions, adjusted balancing, physics and mechanics, addition/removal of features and characters, etc. Basically, the developers/publishers are responsible for defining new iterations through new release cycles, either to address game issues or to continue support and interest of their games through the years. These cases were even more common before the popularization of game patches and additional downloadable content support through online services. Known figthing game franchises with game entries with multiple iterations are Street Fighter, Guilty Gear, Dead or Alive, Mortal Kombat and Tekken.
The presentation and promotion of each new iteration allow those games to be considered semi-sequels or sister games of their previous iterations. Note that new iterations are very commonly released for the same platforms of their previous iterations, this is something which seems unimportant at first but in reality they affect a lot functionalities like platform-specific charts, depending on the manner they are handled. For accurate documentation, cataloguing and rating purposes, these iterations should be entered on Glitchwave as their own stand-alone entries. Those games need sources to prove their ability to be identified as distinct iterations before being added to the database. Note that most ports are not considered new iterations, but rather different versions of a specific iteration that should be entered as a Release under their specific iteration's Game entry.
Rebranding and repurpose
There are rare cases where a game was entirely rebranded or redesigned while maintaining the same core gameplay, before being released in a different region. In these cases, it does not make sense to group releases, since they are most likely completely different and feature different characters/frachises/credits. The most famous case of rebranding regards to Yume Kōjō: Doki Doki Panic vs. Super Mario Bros. 2. Both games should be added as separated stand-alone entries. Other notable cases of rebranding are Panel de Pon vs. Tetris Attack, Asterix vs. Taz Atari 2600 games, and Wonder Boy in Monsterland vs. Mônica no castelo do dragão.
Special cases of game distribution
Built-in games
Built-in games refer to software that is installed or integrated by default on the platform. These games should have the media field set to "built-in", and the same release dates of the platform model/version they were included with. See Built-in releases images for the specific image standards for this type of game release.
Episodic games
Episodic games are released and available in parts, called episodes. These types of games should be added in their full format, as a season or series. Episodes should not be added as game releases separately. For example, only The Walking Dead: Season 1 would be added as a game entry, with all of its individual episodes not being entered in the database. Under the generic entry, retail releases and complete season packs can be added as release entries. Complete season packs are usually available from the start, together with the first episode availability, so those should be set as the primary release of the game entry. The release date for season packs should be the same as the release date of the first episode (For example, Life Is Strange game entry would have January 30, 2015 as release date). Retail releases (if existant) should be entered with their own release dates, which most of the time will differ from the individual episodes release dates. Remember that certain games are marketed as episodic games, though they are not released in actual parts, seasons or series. Such games should have its "episodes" added as separated, normal games entries (e.g. Sonic the Hedgehog 4: Episode I and Sonic the Hedgehog 4: Episode II)