Illerai:Granularity
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 are still worthy of their own article, even though they are not interactive[1].
To merge, or not to merge?
Follow these guidelines when deciding on keeping two articles separated or merged:
- Does item A have the same purpose/use as item B?
- Can item A be substituted with item B?
Common examples from the main RuneScape Wiki with answers to above questions:
- Potions
- Yes, all potions have the same effect when used.
- Yes, as 3-dose can be replaced with 4-dose.
- Decision: Merge
- Raw/cooked food
- No, raw food is for cooking and may contain details about acquiring it (fishing locations / experience points etc.). Cooked food is for eating and may include details of hitpoints healed and cooking methods.
- No.
- Decision: Keep separate [2]
- Food portions (eaten over multiple bites; such as pizza)
- Yes.
- Yes.
- Decision: Merge
- Diary reward items
- No, higher level items have more abilities than lower level items.
- No, lower level items cannot be used in place for some higher level abilities.
- Decision: Keep separate
- Items/Monsters with similar names
- No.
- No.
- Decision: Keep separate
- Charged items (such as the amulet of glory)
- Yes, all charges essentially have the same purpose.
- Mostly yes, the charges can do the same thing at 1+ charges remaining.
- Decision: Merge
- Different/trimmed versions of armour/weapons
- and 2. Depends, use this question, "Do they look the same when worn/equipped?"
- Decision: If yes, merge. Otherwise, keep them separate.
- Different types of the same race
- Either mostly yes, or no.
- No. They might be the same race, but are different.
- Decision: Keep separate for mostly yes and no at #1
NPC granularity[3][4]
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.
Monster granularity[5]
- Different named monsters must have different articles
- 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
- 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[6]. For example, the inventory icons for Ashes and Pile of salt currently look identical, but the icons' image files (File:Ashes.png and File:Pile of salt.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.
Exceptions
- Actual players - per RS:PLAYERS
- Transcripts should be moved to the Transcript: namespace and titled Transcript:PAGENAME. Book transcripts, including texts that can be read, but not picked up, should have their respective transcripts on their own page under a header labelled transcript. A summary of the included transcript can be added as well, if the transcript is particularly lengthy.
Remember
As with any policy, use common sense instead of just blindly following the policy.
References
Policies |
| ||||||
---|---|---|---|---|---|---|---|
Guidelines | |||||||
Essays |