RuneScape:Maintenance/Update history
A guide to update history[edit source]
Templates[edit source]
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, e.g. Prifddinas. Update history essentially creates the box where Update list items will be added.
Example:
{{UH| * {{UL|update=Menaphos - The Gates are Open|date=5 June 2017}} ** Menaphos was released. }}
Produces the following:
Update types[edit source]
- There are 6 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.ninja
- Used on ninja updates;patch
- The most used, usually on every change;hotfix
,warmfix
andcoldfix
- Used on hot/warm/coldfixes;hidden
- Used for hidden updates.nxt
- Used for NXT update posts, excluding launcher changelogs, those should go here.
Coldfixes, hotfixes, hidden and nxt 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
. A citation should also be added (see below for an example). If adding a citation, make sure to also add the ==References==
header, with the content {{reflist}}
. This section should be placed after the rest of the page's content (if the page does not already have it).
How to start[edit source]
- To start, go to RuneScape:Maintenance/Update history/Updates and click on a patch.
- Copy or rewrite each line on their respective page(s), you can also add wiki links to the UL.
- Changes are sometimes grouped and can be copied easily, for example, changes under the Mobile header or Solak can be copied over in bulk to the respective pages.
- Changes do not need to be copied verbatim due to errors, or if you simply want to reword it better.
- After finishing a patch, strike through its entry on the list with
<s></s>
and sign your name afterwards with~~~~
(if you wish), so everyone knows that said patch is done.
Things to have in mind[edit source]
- 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.
- 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 > Ninja > Patch > Coldfix > Hotfix > Hidden - although this is not required, per Forum:Update History - Type ordering.
- 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.
- When adding a recent update ensure that the article's content is updated accordingly or an appropriate tag such as Template:Incomplete is added.
- A single change may impact more than one article. For example, the following change might be added to both Quest list and Shilo Village:
Policy[edit source]
Extra information[edit source]
If you need more details or just want to chat, head over to the #update-history
channel on the RuneScape Wiki discord.
This project was created and discussed on the forum threads: Forum:Listing update histories on articles and Forum:Listing update histories on articles v2. Feel free to check them if you want to suggest anything that has not been thought about.