Template:Infobox video game/doc/syntax guide

General fields

 * The full name of the game including punctuation and style (e.g. "Super Mario RPG: Legend of the Seven Stars" instead of "Super Mario RPG" or "Legend of the Seven Stars"). Do not wikilink the name of the game.
 * The full name of the game including punctuation and style (e.g. "Super Mario RPG: Legend of the Seven Stars" instead of "Super Mario RPG" or "Legend of the Seven Stars"). Do not wikilink the name of the game.


 * Set =yes to make the box collapsible.
 * Set =yes to make the box collapsible.


 * Determines the initial collapsed state of the infobox. Set =collapsed to put the box in collapsed state initially. Set =expanded to put the box in expanded state initially. Set =autocollapse to have the box's initial collapsed state be determined automatically based on the number of other templates in the article that also have the "collapsible" attribute. (Has no effect if collapsible is not used)
 * Determines the initial collapsed state of the infobox. Set =collapsed to put the box in collapsed state initially. Set =expanded to put the box in expanded state initially. Set =autocollapse</tt> to have the box's initial collapsed state be determined automatically based on the number of other templates in the article that also have the "collapsible" attribute. (Has no effect if collapsible</tt> is not used)


 * Set =yes</tt> to make the image show even when collapsed. (Has no effect if collapsible</tt> is not used)
 * Set =yes</tt> to make the image show even when collapsed. (Has no effect if collapsible</tt> is not used)

For image sizing, use the "frameless" and the "upright" flag. This takes into account user preferences, and sizes the image to fit the infobox at default settings. Wiki:  </tt>
 * Ideally, an English-language cover or a promotional flier, in the case of an arcade game. Failing that, a logo or foreign-language cover can suffice. Where different cover designs are available for different regions, the one from the region in which the game has been developed should be used. If the game is not developed in an English-language region use the cover from the region in which the game receives its first English language release, unless another English language version has been uploaded first, in which case you should not change it. Where a game is released on multiple platforms, the PC cover is preferred over console covers to avoid bias towards a certain console. However, if possible, artwork should not use any platform indicator at all. Avoid screenshots (per consensus) and multiple images (per WP:FUC #3). Multiple images may be acceptable if the article is covering multiple games (such as with Pokémon Ruby and Sapphire).
 * Ideally, an English-language cover or a promotional flier, in the case of an arcade game. Failing that, a logo or foreign-language cover can suffice. Where different cover designs are available for different regions, the one from the region in which the game has been developed should be used. If the game is not developed in an English-language region use the cover from the region in which the game receives its first English language release, unless another English language version has been uploaded first, in which case you should not change it. Where a game is released on multiple platforms, the PC cover is preferred over console covers to avoid bias towards a certain console. However, if possible, artwork should not use any platform indicator at all. Avoid screenshots (per consensus) and multiple images (per WP:FUC #3). Multiple images may be acceptable if the article is covering multiple games (such as with Pokémon Ruby and Sapphire).


 * A short description of the image. Is it a flyer, a game cover, or something else? (See above for what an image should consist of.) This is used as the alternate text that will be displayed below the image. (Does not show if image</tt> is not used)
 * A short description of the image. Is it a flyer, a game cover, or something else? (See above for what an image should consist of.) This is used as the alternate text that will be displayed below the image. (Does not show if image</tt> is not used)


 * The popular name(s) of the game developer(s). This field is for the game development company (e.g. Nintendo) or, if confirmed by primary sources, the name of the team that developed the game (e.g. Nintendo EAD). In the case of a game made entirely by one person, use the designer field instead. The name(s) can be wikilinked. Individual development tasks handled by different companies (e.g. scenario, programming) should not be mentioned in the infobox but in the article text instead. For port developers, use the collapsible list template, fill the field title=</tt> with the developer of the original version, and also include the field titlestyle=font-weight:normal;font-size:12px;background:transparent;text-align:left</tt>. Platforms can be abbreviated to fit in one line, and should be listed as bolded section titles without colons, separated with commas (e.g. PS2, GCN, Xbox).
 * The popular name(s) of the game developer(s). This field is for the game development company (e.g. Nintendo) or, if confirmed by primary sources, the name of the team that developed the game (e.g. Nintendo EAD). In the case of a game made entirely by one person, use the designer field instead. The name(s) can be wikilinked. Individual development tasks handled by different companies (e.g. scenario, programming) should not be mentioned in the infobox but in the article text instead. For port developers, use the collapsible list template, fill the field title=</tt> with the developer of the original version, and also include the field titlestyle=font-weight:normal;font-size:12px;background:transparent;text-align:left</tt>. Platforms can be abbreviated to fit in one line, and should be listed as bolded section titles without colons, separated with commas (e.g. PS2, GCN, Xbox).


 * : The popular name(s) of the video game publisher(s). The name(s) can be wikilinked. Use the video game release template for regional publishers. If there are many publishers or if the list grows too long, use the collapsible list template, fill the field title=</tt> with the primary publisher, and also include the field titlestyle=font-weight:normal;font-size:12px;background:transparent;text-align:left</tt>. Platforms can be abbreviated to fit in one line, and should be listed as bolded section titles without colons, separated with commas (e.g. PS2, GCN, Xbox).
 * The popular name(s) of the game's distributor(s). Only use this field if it is a different company from the publisher. The name(s) can be wikilinked.
 * The popular name(s) of the game's distributor(s). Only use this field if it is a different company from the publisher. The name(s) can be wikilinked.


 * The video game series the game is associated with. Only use this field if there is an article for the series. Wikilink and italicize the name(s) (such as  Halo </tt>).
 * The video game series the game is associated with. Only use this field if there is an article for the series. Wikilink and italicize the name(s) (such as <tt> Halo </tt>).


 * The game's engine. Only use this field for game engines with an established, independent article and wikilink its name (such as <tt> id Tech 3 </tt>).
 * The game's engine. Only use this field for game engines with an established, independent article and wikilink its name (such as <tt> id Tech 3 </tt>).


 * The latest official version number of the game. This field typically applies to PC games, though some console and arcade games have several numbered revisions too.
 * The latest official version number of the game. This field typically applies to PC games, though some console and arcade games have several numbered revisions too.


 * The console or operating system the game was released for. The names should not be abbreviated in this field to avoid confusion for readers unfamiliar with the subject.
 * The console or operating system the game was released for. The names should not be abbreviated in this field to avoid confusion for readers unfamiliar with the subject.


 * If possible, use the game's exact release date. ("August 27, 2024") Use the first public non-festival release in the game's country of origin, as well as any English-language release dates available. Use the video game release template: <tt>
 * If possible, use the game's exact release date. ("August 27, 2024") Use the first public non-festival release in the game's country of origin, as well as any English-language release dates available. Use the video game release template: <tt>

</tt>. If there are many release dates, enclose them all with the collapsible list template, fill the field <tt>title=</tt> with the earliest release date, and also include the field <tt>titlestyle=font-weight:normal;font-size:12px;background:transparent;text-align:left</tt>. Platforms can be abbreviated to fit in one line, and should be listed as bolded section titles without colons, separated with commas (e.g. PS2, GCN, Xbox).


 * The gameplay genre(s) (such as first-person shooter, adventure, etc.) the game is categorized in by its developers and publishers, or by reliable sources. This should not include thematic genres (like science fiction, horror, etc.) as video games are more difficult to categorize in such a way. Verifiable thematic genres can be mentioned in the article's body.
 * The gameplay genre(s) (such as first-person shooter, adventure, etc.) the game is categorized in by its developers and publishers, or by reliable sources. This should not include thematic genres (like science fiction, horror, etc.) as video games are more difficult to categorize in such a way. Verifiable thematic genres can be mentioned in the article's body.


 * Playing modes the game offers. The only values possible are single-player and multiplayer (or both).
 * Playing modes the game offers. The only values possible are single-player and multiplayer (or both).


 * Use this field for games where at least one of the platforms it was released on uses several types of media (e.g. Windows, MSX), or leaves the method of distribution ambiguous. The only values possible are "floppy disk", "cartridge", "memory card", "optical disc", "download", and "cloud computing" (and combinations thereof).
 * Use this field for games where at least one of the platforms it was released on uses several types of media (e.g. Windows, MSX), or leaves the method of distribution ambiguous. The only values possible are "floppy disk", "cartridge", "memory card", "optical disc", "download", and "cloud computing" (and combinations thereof).


 * The hardware specifications or equipment required to run the game. These should only be listed for the original version of the game, and asterisks ( * ) should be used to list individual requirements if there is more than one. For PC games, the requirements are:
 * processor frequency (e.g. "200 MHz processor")
 * system memory (e.g. "32 MB RAM")
 * video card or video card memory (e.g. "4 MB video card")
 * required HDD space (e.g. "300 MB HDD space)
 * (optionally) an operating system specific value (e.g. "DirectX version 6.1")
 * For console games, the equipment that is mandatory to run the game should be listed (e.g. "Expansion Pak" for Donkey Kong 64). Memory space and additional compatible equipment are not considered system requirements for these games.
 * For console games, the equipment that is mandatory to run the game should be listed (e.g. "Expansion Pak" for Donkey Kong 64). Memory space and additional compatible equipment are not considered system requirements for these games.


 * The type of arcade cabinet the game uses, e.g. upright, sit-down, cocktail, custom.
 * The type of arcade cabinet the game uses, e.g. upright, sit-down, cocktail, custom.


 * The characteristics of the arcade hardware's video output, such as graphical technique, display resolution and monitor orientation. Wiki: <tt> Raster, 256 x 224, horizontal orientation </tt>
 * The characteristics of the arcade hardware's video output, such as graphical technique, display resolution and monitor orientation. Wiki: <tt> Raster, 256 x 224, horizontal orientation </tt>


 * The name of the arcade system board hardware. Wikilink the name(s).
 * The name of the arcade system board hardware. Wikilink the name(s).


 * In case of unique arcade hardware, leave the <tt>arcade system</tt> field empty and fill in the fields listed below.
 * In case of unique arcade hardware, leave the <tt>arcade system</tt> field empty and fill in the fields listed below.


 * The names and number of central processing units present. Wikilink the names if available.
 * The names and number of central processing units present. Wikilink the names if available.


 * The names and number of hardware present. Wikilink the names if available.
 * The names and number of hardware present. Wikilink the names if available.

Credit fields
As with the developer field, individual development tasks for one field (e.g. who of the artists did the character design and who the concept art, or who of the writers created the story and who the script) should not be mentioned in the infobox but in the article text instead. Individual tasks should be generally kept to prose and the field should only list key people. For example, the distinction between story and script writers of The Legend of Zelda: Twilight Princess is mentioned in the article's development section.


 * : The popular name(s) of the game director(s) or creative director(s), who had an overseeing role in the creative development of the game. The name(s) can be wikilinked.


 * : The popular name(s) of the game producer(s), who were in charge of the overall production of the game. The name(s) can be wikilinked. Only the actual producer should be used, as executive and assist producers are not generally involved as intimately in a game's development.


 * : The popular name(s) of the game designer(s). This field is for people that worked on the game system. The name(s) can be wikilinked.


 * : The popular name(s) of the game programmer(s). The name(s) can be wikilinked.


 * : The popular name(s) of the game's artist(s). The name(s) can be wikilinked.


 * : The popular name(s) of the game's writer(s). The names can wikilinked. The writers should be listed in the order of their contribution, with the writer(s) who wrote the actual game scenario/script coming before the story writer(s).


 * : The popular name(s) of the composer(s) who worked on the game's music.