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
Line 26: Line 26:
 
<code>intro-sentence</code>
 
<code>intro-sentence</code>
 
* <code>gamename</code> is a <code>taxonony/perspective/mode/genre etc.</code> featuring <code>key/unique gameplay features</code> made by <code>company</code> published by <code>company</code>.
 
* <code>gamename</code> is a <code>taxonony/perspective/mode/genre etc.</code> featuring <code>key/unique gameplay features</code> made by <code>company</code> published by <code>company</code>.
* <code>game</code> is a <code>sequel/prequel</code> in the <code>series</code> or <code>related series</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.
 
* <code>game</code> uses <code>engine</code> plus any noteworthy engine information.
 
* <code>game</code> is <code>important/noteworthy</code> because <code>reasons</code>.
 
* <code>game</code> is <code>important/noteworthy</code> because <code>reasons</code>.
  
 
<code>release-history</code>
 
<code>release-history</code>
 +
* <code>pre-release information</code> including early access, crowdfunding, closed beta, etc.
 
* <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>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> including: e.g. platform changes, platform exclusivity, crowdfunding, major technical issues, major bugs, inability to access the game, DRM, missing advertised features, features missing from console counterpart, missing endings, etc.
+
* <code>history</code> including: e.g. platform changes, platform exclusivity, major technical issues, major bugs, inability to access the game, DRM, missing advertised features, features missing from console counterpart, missing endings, etc.
  
 
<code>current-state</code>
 
<code>current-state</code>

Revision as of 17:03, 8 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.

Introduction structure

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

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

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.
  • game is important/noteworthy because reasons.

release-history

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

current-state

  • current major issues/controversies 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).
  • improvements link to anchors of essential mods or quality of life improvements further below.
  • multiplayer describe the scene, is it alive or dead, can players find games?

community

  • 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

Notes

  • Limitations for each section.
  • Inclusion criteria: 1) activity 2) size 3) uniqueness.
  • Ideally, every claim should be referenced.


References