If the publisher and/or developer of a computer game version is the same as that of the "main game" (ie the /cvg/computer_videogame entry linked to a /cvg/game_version), should we
1) duplicatethepublisher/developer from the /cvg/computer_videogame entry, and then risk these not being updated if the /cvg/computer_videogame entry is updated?
2) leave them blank, forcing applications using this data to "default" the values themselves?
Cheers!
Discussions on Computer Game Version
-
-
-
-
What would people's opinion on adding a "name" field to /cvg/game_version be? The use I see for this is where one game was released under different names on different platforms. The example I'm thinking of here is that "Gradius" was released as "Nemesis" on the ZX Spectrum. I've added "Nemesis" to the "Also known as" field of the /cvg/computer_videogame entry for "Gradius", but a more explicit tie-in to the Spectrum release might be good. I'm sure many other examples of this exist as well.
-
Hi Pak -- The initial best practice (for now) is what you did -- to put it in the "also known as" field. If you can point to more examples, we could add in a "version specific name" property for the version.
-
Some ones I could find quickly (all ZX Spectrum-related, as that's where my expertise lies...):
* "Ajax" became "Typhoon"
* "Arabian" became "Tales of the Arabian Nights"
* "Bagman" became "Gilligan's Gold"
* "Butasan" became "Pyscho Pigs U.X.B."
* "Contra" became "Gryzor"
* "Gladiator" became "Great Gurianos"
* "Pipe Dream" became "Pipe Mania"
* "Rush'n Attack" became "Green Beret"
I'm sure there's many more! -
That's pretty impressive. I just added a new property "version-specific name" to the computer game version. Technically, this isn't the best way to do it -- I should be just using the name field, but this will at least allow you to enter the data.
-
