Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Difference between revisions of "PCGamingWiki:Editing guide/Introduction"

From PCGamingWiki, the wiki about fixing PC games
(fixing the Wikipedia link)
(Guidelines adjusted)
Line 13: Line 13:
  
 
Guidelines:
 
Guidelines:
−
* This is the first free text area on PCGamingWiki and our aim is to describe the game in a factual and neutral way.  
+
* This is the first free text area on PCGamingWiki and our aim is to describe the game in a constrained, neutral manner constrained by facts and not driven by criticism, outrage or bias.  
 
* Every claim should be individually referenced, ideally with a snippet e.g. <code><nowiki><ref>{{Refurl|url=|title=|date=2020-05-09|snippet=}}</ref></nowiki></code>
 
* Every claim should be individually referenced, ideally with a snippet e.g. <code><nowiki><ref>{{Refurl|url=|title=|date=2020-05-09|snippet=}}</ref></nowiki></code>
−
* It is important to consider {{W|Wikipedia:Reliable sources and undue weight|'undue weight'}} and only include issues that affected/will affect a significant number of players.
+
* It is important to consider {{W|Wikipedia:Reliable sources and undue weight|'undue weight'}} and only include issues that has affected/will affect a significant number of players.
−
* Avoid platform exclusivity, instead refer to concrete release dates.  
+
* Any issues (e.g. platform issues) mentioned must be proven with multiple original sources otherwise they will be removed.
−
* Delays should be included but only if longer than one month. Multiple delays can be grouped together in a single sentence.
+
* Issues that are fixed within a 48 hour period after launch are not to be included.
 +
* Avoid platform 'exclusivity', instead refer to concrete release dates.  
 +
* Delays should be mentioned but only if longer than one month. Multiple delays can be grouped together in a single sentence.
 
* Avoid speculation about release dates, only use direct references from developers/publishers.
 
* Avoid speculation about release dates, only use direct references from developers/publishers.
  
 
==Introduction structure==
 
==Introduction structure==
−
'''Introduction''' - this section has no header, it is simply prose separated by paragraphs:
+
'''Introduction''' - this section has no header, it is simply prose separated by paragraphs in this {{T|Introduction}} template:
  
 
<pre>
 
<pre>
Line 35: Line 37:
 
* <code>game</code> is a <code>sequel/prequel</code> in the <code>series</code> or <code>related series</code> or is a <code>spiritual successor</code>.
 
* <code>game</code> is a <code>sequel/prequel</code> in the <code>series</code> or <code>related series</code> or is a <code>spiritual successor</code>.
 
* <code>game</code> uses <code>engine</code> plus any noteworthy engine information compared to other entries in the series.
 
* <code>game</code> uses <code>engine</code> plus any noteworthy engine information compared to other entries in the series.
−
* <code>game</code> is <code>important/noteworthy</code> because <code>reasons</code>.
+
* <code>game</code> is <code>important/noteworthy</code> for any other <code>reason</code>.
  
 
<code>release-history</code>
 
<code>release-history</code>
 
* <code>game</code> was first released on <code>platform</code> on <code>date</code>.
 
* <code>game</code> was first released on <code>platform</code> on <code>date</code>.
 
* <code>pre-release information</code> including early access, crowdfunding, closed beta, etc.
 
* <code>pre-release information</code> including early access, crowdfunding, closed beta, etc.
−
* <code>platform</code> changes with platform (Steam, EGS,GOG etc.) including delays, technical issues.
+
* <code>platform</code> changes with platform (Steam, EGS, GOG etc.) including delays, technical issues.
−
* <code>launch</code> was <code>successful/unsuccessful/criticised?</code> with player number milestones if noteworthy.
+
* <code>launch</code> was <code>successful/unsuccessful/criticised</code> with player number milestones if noteworthy.
 
* <code>history</code> with a focus on technical issues: e.g. major bugs, inability to access the game, DRM, missing advertised features, features missing from console counterpart, missing endings, etc.
 
* <code>history</code> with a focus on technical issues: e.g. major bugs, inability to access the game, DRM, missing advertised features, features missing from console counterpart, missing endings, etc.
  

Revision as of 10:44, 9 May 2020

This is a draft and work in progress and should not be implemented onto articles at this time.

The aim of a new 'Introduction' section is to incorporates changes discussed here:

The aim is to provide:

  • More relevant qualitative information for gamers researching a new PC game that is not constrained to single bullet points.
  • Information about the history and current state of the game.
  • Additional natural content for improving search engine ranking.

Guidelines:

  • This is the first free text area on PCGamingWiki and our aim is to describe the game in a constrained, neutral manner constrained by facts and not driven by criticism, outrage or bias.
  • Every claim should be individually referenced, ideally with a snippet e.g. <ref>{{Refurl|url=|title=|date=2020-05-09|snippet=}}</ref>
  • It is important to consider 'undue weight' and only include issues that has affected/will affect a significant number of players.
  • Any issues (e.g. platform issues) mentioned must be proven with multiple original sources otherwise they will be removed.
  • Issues that are fixed within a 48 hour period after launch are not to be included.
  • Avoid platform 'exclusivity', instead refer to concrete release dates.
  • Delays should be mentioned but only if longer than one month. Multiple delays can be grouped together in a single sentence.
  • Avoid speculation about release dates, only use direct references from developers/publishers.

Introduction structure

Introduction - this section has no header, it is simply prose separated by paragraphs in this {{Introduction}} template: 

{{Introduction
|intro-sentence    =
|release-history   =
|current-state     =
}}

intro-sentence

  • gamename is a taxonony/perspective/mode/genre etc. featuring key/unique gameplay features made by company published by company.
  • game is a sequel/prequel in the series or related series or is a spiritual successor.
  • game uses engine plus any noteworthy engine information compared to other entries in the series.
  • game is important/noteworthy for any other reason.

release-history

  • game was first released on platform on date.
  • pre-release information including early access, crowdfunding, closed beta, etc.
  • platform changes with platform (Steam, EGS, GOG etc.) including delays, technical issues.
  • launch was successful/unsuccessful/criticised with player number milestones if noteworthy.
  • history with a focus on technical issues: e.g. major bugs, inability to access the game, DRM, missing advertised features, features missing from console counterpart, missing endings, etc.

current-state

  • current major issues that have not been resolved yet.
  • updates/support is the game regularly updated technically (patches etc.) or content (DLC, expansions, microtransactions or free content updates).
  • multiplayer describe the scene, is it alive or dead, can players find games?
  • improvements link to anchors of essential mods or quality of life improvements further below.
  • major community additions ONLY INCLUDE if there are major communities outside of 'General information' links such as already linked Steam, GOG, fan forums, e.g. substantial modding communities, Discord communities, alternative servers, hacked multiplayer etc.

Examples

Editing guide

Editing Guide - Disambiguation.svg

The Disambiguation (Disambig) tag

Editing Guide - Availability.svg

Availability


References