An infobox is the first element of an article. It provides basic information on a game (ex. release dates, developers, publishers, etc.), along with the box art/logo and links to major databases with relevant info (currently Wikipedia, SteamDB, Co-Optimus, StrategyWiki and WineHQ).

There are two main types of infoboxes (and two niche types) available.

The most common infobox available, it is mainly used for game articles.

General rules

For release dates, list the earliest official platform release first (ex. if the game was released on OS X first, list the OS X release date at the top)

In the case that multiple releases share the same date, organize the dates in the following order (for all the platforms that apply):

PC booter

DOS

Windows 3.x

Windows

Mac OS

macOS/OS X

Linux

For games with unannounced release date, use TBA as the date. Only replace the date when the game has official release date.

For games in Early Access, use EA as the date. Only replace the date when the game has officially left Early Access.

For games that are still available to public via Early Access or public beta test, but remain incomplete and it is not known whether the game will ever be finished, use Unknown as the date.

For games that used to be available to public via Early Access or public beta test and are no longer available with no official announcement of their cancellation, use LC (Likely cancelled) as the date.

For games that used to be available in some form and were officially cancelled, use Cancelled as the date.

Field breakdown

Section

Definition

Notes

title

The name of the game.

An optional field, it is automatically set to the page name if left blank. It is only required for games with "optional" title modifiers (see SimFarm). Otherwise, it should be left alone.

cover

The cover/logo of the game.

The full name of the image file (including extensions) must be provided. See The Cover subsection for details.

developers

A list of the name(s) of the game developer(s).

List all the developers involved in the PC releases of the game. The main developer should always be listed first, regardless of involvement.

publishers

A list of the name(s) of the game publisher(s).

List all the publishers involved in the PC releases of the game. The main publisher should always be listed first, regardless of involvement. If the publisher is the same as the developer, leave the field blank. If the publisher was only regional (e.g. only published the game in Europe), list the region or country as a second argument.

engines

A list of name(s) of the game engine(s) used.

Leave the section empty if the engine used is unnamed or in-house. Do not list game engine middleware (ex. Havok Physics) under the Engines section. See the Middleware table for details.

release dates

A list of the earliest public release date of the game for different operating system.

All dates are to be written down in the following format: mm dd, yyyy (where mm is the full name of the month). See the General rules section above for further details.

reception

Average critical reception of the game.

List those aggregators that have an aggregated review score for the game. If the PC platform is handled separately from other platforms, use the PC page.

For Metacritic, use the Metascore.

For OpenCritic, use the Top Critic Average score.

For IDGB, use the critic ratings score. This is the smaller (in size of the element, not in units) score to the right. The larger score to the left is the average IGDB user rating and should not be used.

The field is meant for games that do not have a native Linux version available. Leave it blank otherwise. See Database IDs for details.

license

The license the game is available under

Should be set to one of the following: commercial, former commercial (paid games that have been re-released for free), freeware, or free-to-play. This information is not shown on the game page but is used to populate other pages such as the List of Freeware Games.

Database IDs

This is a list of the database ID formats for all the databases the infobox supports

A niche infobox, it is meant for game controllers. A game controller can be:

Gamepads

Joysticks

Steering wheels/racing controllers

Flight controllers

Haptic-centric controllers

Motion-based controllers

"Exotic" controllers (gaming keypads, dance pads, anything that does not fit in the above categories)

Note that it is far more sparse then the game infobox in terms of information provided to the reader.

Field breakdown

Section

Definition

Notes

Title

The name of the controller.

An optional field, it is automatically set to the page name if left blank. It should be left alone in most cases.

Cover

A picture of the controller.

The full name of the image file (including extensions) must be provided. See The Cover subsection for details.

XInput

Support for the XInput controller API.

Use true, false, or hackable to denote support level (see Section Table legend for details). A majority of the controllers released past December 2005 (particularly ones that are Xbox 360 and/or Xbox One-focused) have native support. Earlier than that, it should be assumed that the controller is using DirectInput.

Predecessor

The controller that was released prior to the current one (if the controllers are part of a series).

Linking needs to be done in the following fashion: [[Controller:<CONTROLLER NAME>|<CONTROLLER NAME>]]

Leave blank if there is no prior release.

Successor

The controller that was released after to the current one (if the controllers are part of a series).

Linking needs to be done in the following fashion:

[[Controller:<CONTROLLER NAME>|<CONTROLLER NAME>]]
Leave blank if there is no succeeding release.