Template:Video game reviews
From HandWiki
Template documentation | This template is used on approximately 10,000 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them.
Transclusion count updated automatically (see documentation). |
| Related pages |
|---|
 | This template uses Lua: |
{{Video game reviews}} is a template which presents review aggregator and individual publication review scores in a video game article. It supports a game's reception section, which for released titles is necessary for an article to be broad in its coverage.
Things to remember:
- This template is not required.
- This template supplements the reception section; it does not replace it.
- Only include reviews if they are cited within the text.
Guidelines
{{Video game reviews}}is not required- Traditional reviews, or those that provide some type of score, may be few and far between for some games. If you only have a couple of such reviews which could be used to fill the table, consider foregoing the table and instead simply state these in the body of reception text.
- All reviews must be referenced
- Individual reviews should cite their original publication, not the truncated aggregator summary. See also Wikipedia:WikiProject Video games/Sources.
- Every single-site review source should be used within the reception section
- The reviews table supports the text. It is not to replicate the function of external review aggregators.
- Stay with the "usual suspects"
- Aggregator scores
- Aggregators present readers with a quick gauge of the critical consensus.
- Metacritic − Industry standard
- GameRankings − Useful for older games
- Do not include GameRankings in articles about newer games. GameRankings is mainly useful for older games and it is mainly duplication in newer ones. Round aggregator scores to the nearest whole number (e.g., 83.46% → 83%).
- Review scores
- The following sources comprise the most popular and influential voices in the games industry. They provide a core selection of reviews to build a reception section:
- For older games, particularly fifth generation and earlier, web based publications lacked the reach and influence of print publications. Consider these sources:
- Computer and Video Games − UK magazine first published in 1981
- Computer Gaming World − US PC magazine first published in 1981
- Electronic Gaming Monthly − US magazine first published in 1989 (See below)
- GamePro − US magazine first published in 1989
- These publications and others may be available from the WikiProject's reference library.
- Single platform publications may offer specialist insight to platform-exclusive games, and allow readers to compare the reception across platforms of multiplatform games. Consider sources such as Nintendo Power, Official Xbox Magazine, PC Gamer, PlayStation Official Magazine – UK, and others.
- For niche genres, genre publications may offer specialist insight. Consider sources such as Adventure Gamers, RPGamer, PC Pilot, and others.
- Games which have strong cultural ties to their country of origin should have reception from that same country. Japanese games and Japanese ports of American games, for example, are best served with a Famitsu review (See below).
- Consider coverage from outside traditional video games media. High quality sources such as The New York Times, Wired, and the BBC do not cater to a "gamer" audience, but may on occasion cover video games. Wikipedia is both a generalist and specialist encyclopedia. Opinions from these sources may be more accessible to a non-gamer audience and place the subject in a greater cultural and societal context than is possible at a narrowly focused video gaming publication.
- Reviews without scores
- Some publications, such as Eurogamer, Kotaku, and Polygon, may not score their reviews. If, instead of a score, the publication presents the game with a badge or award in its review, this can be included in the table. This is not necessary.
- Consider the aggregate scoring breakdown
- The review aggregators used in the table are considered reliable sources and are trusted to provide the critical consensus. However, some games may divide opinion and there may be no true consensus. This division of opinion may already have been captured following the guidelines above, but if not - consider including further reviews expressing these "outlier" opinions.
- Publications such as Electronic Gaming Monthly and Famitsu review games among a group, with each reviewer offering their individual score. Using the average or cumulative score from these publications will result in the loss of that breakdown, so include the individual scores, either in the table itself or in a footnote.
- Numerical scores
- Make sure to include the maximum possible score for a review if the review uses a numerical value ("7/10", "86/100"). This is not required if the score is published as a percentage, as this presumes the maximum score of 100%.
- Letter grades
- Ratings that use a letter grade system should simply present the letter grade ("B-", "C+").
- Stars
- If a review uses a stars instead of numbers, you may use the {{rating}} template. This is not required. Examples:
Code Result {{Rating|3|5}}
{{Rating|3.5|5}}
{{Rating|7|10}}
General
Usage
All of the following fields are optional:
- title*
- Can be used to provide a custom title for the table; otherwise, it will default to "Reception".
- subtitle*
- Used to add additional text before the collapsible section. This is necessary to add if want a longer title, as long titles via the "title" parameter will not center correctly.
- state* [autocollapse, collapsed, expanded]
autocollapse– The table will start out collapsed if there are two or more tables on the same page that use other collapsible tables. Otherwise, the table will be expanded. For technical details, see MediaWiki:Common.js.collapsed– The table will be collapsed (hidden) by default. This is useful for very long tables.expanded– The table will be expanded (shown) by default. This is useful if autocollapse is not showing the table in a section that it wouldn't matter.- If undefined or set to blank, the table will not be collapsible. The table will also not be collapsible if the title parameter is not set.
- align*
right– Displays the table on the right. This is default.left– Displays the table on the left.inherit– Specifies that the value of the float property should be inherited from the parent element.none– The table is not aligned, and will be displayed just where it occurs in the text on the page.
Code
| Aggregator | Code | Rating system example |
|---|---|---|
| Metacritic | MC |
83/100 |
| GameRankings (See note above—only use for older games when Metacritic data is unavailable) |
GR |
84% |
