...
| id | key | text | Comment |
|---|---|---|---|
| 1 | Game | This is the standard case. It is used for new stand-alone releases that don't fall under the other types of this list, or when a new release of a previously released game breaks the different game criteria developed here. | |
| 2 | Compilation | This is the switch for game bundles. It shall only be used if two or more games are bundled together, or one game and at least one of its significant add-ons. This rule is to exclude minor compilations like included demos, or minor DLCs coming with the release. Furthermore, the compilation shall be marketed as just that, a bundle of games, and usually comes with its own title. This rule is to exclude re-releases of games with playable goodies included. The aforementioned "technical" compilations are dealt with elsewhere in the data model, at game release level. | |
| 3 | Add-on / Patch / Mod (significant) | This is the case for important add-ons. As it seems hardly possible to sanely separate the classical add-on (additional content) from patches / mods / etc., we just don't do it and treat every such non-stand-alone release the same. This case shall only be used when the release can't be played without the base game, and when it meets Oregami's significance criteria. Basically, significant add-ons will later be handled just like a normal game, i. e. will show up in default searches and game lists. | |
| 4 | Add-on / Patch / Mod (insignificant) | Releases which can't be played without a base game and do not meet the significance criteria are flagged here. These releases will be more hidden than the significant add-ons, i. e. the user will have to opt-in to see this stuff in searches and data lists. And as we kind of open up the flood gates for user created content and the mod community with accepting insignificant add-ons, we will have more switches elsewhere in the data model to further separate the wheat from the chaff, and give the users more opportunities to customize their data displays. | |
| 5 | Episodic Game | This is for umbrella entries for games that are released in episodes. Examples would be Tales of Monkey Island, or Siege of Avalon. The "mother game" gets an entry at game level with the game type set to "Episodic game", all episodes get their own entry of type "Episode". Then they're connected using the usual add-on mechanisms, enabling us to either show the whole mother game, or every episode itself to the user. This way, we can even add releases of the whole episodic game to the "mother game" entry. | |
| 6 | Episode | see above |
Data List 32: Game Relationship Type
| id | key | text | Comment |
|---|---|---|---|
| 1 | is sequel | The game continues the story of the previous game. | |
| 2 | is prequel | The game explains what happened before the previously released game, story-wise. | |
| 3 | is side story | The game tells a story that the previous game just mentioned in some way, but didn't explore deeper. | |
| 4 | is successor | The game is a follow-up release to the related game within a game series. | |
| 5 | is add-on | The game entry is an add-on / patch / mod to the previous game. | |
| 6 | is episode of | Episodic games get a "mother" entry at game level, and separate "child" entries for all the episodes. The connection between children and mother is done with this relationship. | |
| 7 | is based on | The game is a clone / remake of a previously released game, but is so different that it broke the different game criteria. |
Open issues
References