GSWiki:Maintenance/Update history

A guide to update history

Templates

The templates used on this project are {{Update history}} or {{UH}} and {{Update list}} or {{UL}}. Update history should only be added to the mainspace, Update history essentially creates the box where Update list items will be added.

Example:

{{UH|
* {{UL|update=Update:Game Update - Outlands}}
** Outlands was released
}}

Produces the following:

The update history project is a work-in-progress – not all updates to this topic may be covered below. See here for how to help out!

• update 30 April 2020 (Update):
  • Outlands was released

Update types

• There are 5 types of updates that can be listed in the |type= parameter:
  • update - Usually used on releases, also shows as default when the |type= parameter isn't used.
  • patch - The most used, usually on every change;
  • ninja - Used on ninja updates;
  • hotfix - Used on hotfixes;
  • hidden - Used for hidden updates.

hotfixes updates do not require an actual update to be added to the |update= parameter. If the change happens without an update post, |update= should be left empty and the |date= parameter should be added with the date in the following format DD Month YYYY.

The update history project is a work-in-progress – not all updates to this topic may be covered below. See here for how to help out!

• hotfix 12 February 2020:
  • Random Bug fix

How to start

On the OSWF project page, a list of patch notes can be found, these are what will be mainly used to grab the information about changes and fill in the articles.

1. To start, go to User:Banri/Update History and click on a patch.
2. Copy or rewrite each line on their respective page(s), you can also add wiki links to the UL.
   1. Changes are sometimes grouped and can be copied easily.
3. After finishing a patch, strike through its entry on the list with <s> </s> and sign your name afterwards with ~~~~.

Things to have in mind

• The Update history section should be located near the bottom of the article, above the Trivia section and all other sections.
• Make sure you're following the proper order (reverse chronological, this means that the most recent updates should be at the top).
• The first indented lines should have the update list template, and the second indented lines should have the actual patches (see the example code above).
• When different types of updates happen on the same patch, these can be put in order of priority: Update > Patch > Hotfix.
• When adding a recent update ensure that the article's content is updated accordingly or an appropriate tag such as Template:Incomplete is added.