RuneScape:Historical information policy

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Acorn 5.png
This page in a nutshell:
Content articles should contain a list of updates as well as other relevant historical information.

The historical information policy describes the various types of historical information which should be included in content articles as the as the preferred format and placement of this information. The project was approved in Forum:Listing update histories on articles and discussed further in Forum:Listing update histories on articles v2.

Summary[edit source]

RuneScape changes over time, and these changes are released in various forms: game updates, patch notes, hidden updates, hotfixes, coldfixes, promotions, etc. These changes can introduce new content and impact existing content both directly and indirectly. While the primary goal of any article is to document the subject's current state within the game, the wiki also has an interest in recording relevant historical information.

Classifying historical information[edit source]

Historical information can be classified into several categories. The table below describes these categories as well as the preferred treatment for each within content articles.

Type Example Section
Notable price changes The price of Rune boots fell from 200,000 coins to below 100,000 coins within a week following the release of Dragon boots. ==Price history==
Direct updates patch 8 May 2017 (Update): Bladed Dive can now be used for movement from the quinary action bar. ==Update history==
Promotional releases Rainbow cape was re-released as part of Update:Treasure Hunter - Rainbow's End (2017) on 12 April 2017. ==Release history==
Metagame history The popularity and potential experience rates of Abyssal demons increased considerably following the release of aggression potions on 8 August 2016. ==Trivia==

Historical information should be limited to these sections. Where there is existing historical information scattered throughout article text or placed in a dedicated ==History== section, it should be reorganised into the sections described here.

Direct updates[edit source]

Direct changes to a piece of content should be documented on the relevant article(s) as follows:

  • Each change should be listed using the {{Update list}} template, including the initial release and any hidden updates.
  • List items should be in reverse chronological order, with the most recent updates being added at the top.
    • When different types of updates happen on the same patch, these can be put in order of priority: Update > Ninja > Patch > Coldfix > Warmfix > Hotfix > Hidden - although unnecessary, per Forum:Update History - Type ordering.
  • UL line items should be nested within the {{Update history}} container template, which should be placed underneath an ==Update history== section header.
  • The Update history section should be located near the bottom of the article, above the Trivia and References sections but below the Gallery section (if applicable) and all other sections.
  • Update text need not be copied verbatim from news posts or patch notes - it should be wikified, typos should be corrected and it may be reworded for conciseness.
  • The first indented lines should have the update list template, and the second indented lines should have the actual patches (see below for an example).

When the date of a hotfix is known, the date parameter should be used and the update should be left empty, a citation should also be added.

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 2019:
    • Onyx are now around 4 times rarer from Prifddinas gem rocks, as they appeared to be coming into game a bit too often.[d 1]
  1. ^ Jagex. RuneScape's Twitter account. 12 Feb 2019. (Archived from the original on 12 Feb 2019.) RuneScape: "Onyx are now around 4 times rarer from Prifddinas gem rocks, as they appeared to be coming into game a bit too often."

A single change may impact more than one article. For example, the following change might be added to both Quest list and Shilo Village:

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!
  • patch 1 October 2018 (Update):
    • The quest log now correctly updates when the player starts the Shilo Village quest.

Some updates affect a truly massive number of items, such as the release of Invention. Please use common sense when deciding which articles should receive UL entries for a given update or patch note.

Promotional releases[edit source]

Many promotional items such as the Rainbow cape are released and removed frequently. These updates should not be placed under an Update history section. Instead, they should be listed under a Release history section header, which should be located near the bottom of the article above the Update history, Trivia, and References sections (where applicable).

Templates should be used to replicate the release history of a given promotion across multiple pages. A list of available templates can be found under Category:Treasure Hunter release tables.

Price history[edit source]

It is natural for Grand Exchange prices of tradeable items to fluctuate in response to game updates or changes in supply and demand. In most cases, these price changes are not notable and should not be documented (and it is also infeasible to do so for all items in the game). However in a select few cases where the changes are particularly drastic or significantly impact the game economy, it is appropriate to include them in the article.

Price histories should be placed under a ==Price history== section header, which should be placed above the Release history, Update history, Trivia, and References sections (where applicable).

Metagame history[edit source]

Many updates which do not directly affect a given piece of content can have a major impact on its popularity or place within the metagame. This information should be placed under the Trivia section. Some examples include: