RuneScape:Granularity

This page in a nutshell: Pretty much anything notable, excluding players, may have its own article.

Many articles on this wiki are about relatively minor things, from hay bales to needles. We encourage gathering information on even the minutest scale. All items, non-player characters (NPCs), quests, whatever, are worthy of their own article, except in special cases where it is decided to combine or delete an article by consensus.

Consensus has shown that "NPC" in this context is defined to be any character whose control is automated by the RuneScape software (as opposed to human players and macros). Whilst most NPCs have common features (such as their name appearing as yellow text in-game) and interactivity options (for example, players are usually able to attack or talk to NPCs as a minimum), characters who do not have these features, i.e. non-interactive, can still be worthy of their own article if they are sufficiently notable; otherwise, non-interactive scenery should be aggregated on Non-interactive scenery..

Item granularity

In most cases, non-dummy items with separate item IDs should be split. Here are some examples:

1. Items with different appearances and colours should have separate articles.
2. Helmets and their charged variants should have separate articles.
3. Flatpacked items of furniture should have their own articles.
4. Heraldic armour should have separate articles.
5. Items found in dungeoneering should have separate articles to their normal equivalent.
6. Summoning scrolls and pouches should be split from the summoning familiar article.
7. Experience lamps should have separate articles.
8. Dungeoneering keys should have separate articles.
9. Strange and Golden rocks should have separate articles.
10. Capes of accomplishment should have separate articles.

There are some exceptions, where switch infoboxes are better suited to the task.

1. Multi-levelled equipment should not be split.
2. Degraded and broken equipment should not be split from their main article.
3. Potions, charged jewellery, and food bites should not be split into their individual items.
4. Items that are indistinguishable other than their IDs (certain book pages, clue scrolls) should not be split.

Cosmetic overrides

Cosmetic overrides that are part of the same set should be listed on the same page. Items and packages for overrides should be listed on a single page, containing only what is obtained from that purchase. Any item obtained from a different purchase, even if it is meant to be part of the set, should have its own article.

All overrides have dummy items in the game's code. While normally not seen, any glitches involving these items should be included as trivia on the override article rather than its own page.

NPC granularity

NPCs with attackable counterparts or confirmed to be the same person should not be split - instead there should be a switch infobox used to show the different varieties unless there are extreme differences, such as Amascut: The Amascut case is extreme in that Amascut is a god and she also plays major roles in multiple quests through multiple characters. NPCs with attackable counterparts can make use of strategy subpages to prevent page cluttering.

Pet granularity

Pets that are substantively different, such as having different requirements or different methods to obtain, should be split. Pets that are fundamentally the same, such as Cat, should not be split.

Monster granularity

Monsters should have separate articles in the following circumstances:

1. Daemonheim variations have their own articles
2. Different named monsters must have different articles
3. Monsters of different combat levels must have different articles unless:
   • They have very similar or identical drop tables AND
   • They are found in the same location and all variants can attack and be attacked
4. If a monster variant needs to be differentiated from other monsters with the same name:
   • If the variant is located in only one location, and is the only such variant to appear in that location, the location name appears in parenthesis after the name
   • If the variant is located in multiple locations, or if is found in one location with other variants that are not applicable for merging under rule #3, (level XX) or another easily distinguishable characteristic appears in parenthesis after the name.

Image granularity

When items and NPCs which look identical in-game have separate articles, they should link to separate images. For example, the inventory icons for Ashes and Ground bat bones currently look identical, but the icons' image files (File:Ashes.png and File:Ground bat bones.png) should be (and are) separate.

Keeping separate images for separate items (or NPCs), even when they look identical, is less confusing, promotes organisation, and reduces the work required if the images diverge.

JMod granularity

See also: RS:BLP

Use common sense to determine if a Jagex employee should have an article. For example, articles about people who work in human resources or corporate teams of Jagex should not be created. An article about a content developer, artist, community manager or highly notable individual (such as the CEO) should be created. The general idea is that if they contribute in some way towards the development of RuneScape and there is sufficient information available, an article should be created on them. Former employees deserve articles under the same conditions.

Exceptions

• Actual players - per RS:PLAYERS
• Transcripts of quests, miniquests, events, items, and conversations with NPCs should be moved onto a separate page in the Transcript namespace, called Transcript:PAGENAME. A summary of item transcripts can be added on the article if the transcript is particularly lengthy.