RuneScape Wiki
No edit summary
Line 4: Line 4:
 
Many articles on this wiki are about relatively minor things, from [[hay bale]]s to [[needle]]s. We encourage gathering information on even the minutest scale. All [[:Category:Items|items]], [[non-player character]]s (NPCs), [[quests]], [[Special:Randompage|whatever]], are worthy of their own article, except in special cases where it is decided to combine or delete an article by consensus.
 
Many articles on this wiki are about relatively minor things, from [[hay bale]]s to [[needle]]s. We encourage gathering information on even the minutest scale. All [[:Category:Items|items]], [[non-player character]]s (NPCs), [[quests]], [[Special:Randompage|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 [[Account|human players]] and [[macro]]s). 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<ref>The [[Mountain goat]], [[Ardal]], [[Blacksmith working the bellows]], and [[Troll cook]] articles were nominated for possible deletion in August 2008, July 2009, October 2009, and March 2010 respectively. This was on the basis that they were not "true" NPCs, but the consensus in all four cases was to keep their articles.</ref>.
+
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 [[Account|human players]] and [[macro]]s). 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<ref>The [[Mountain goat]], [[Ardal]], [[Blacksmith working the bellows]], and [[Troll cook]] articles were nominated for possible deletion in August 2008, July 2009, October 2009, and March 2010 respectively. This was on the basis that they were not "true" NPCs, but the consensus in all four cases was to keep their articles.</ref>.
   
 
==To merge, or not to merge?==
 
==To merge, or not to merge?==
 
Follow these guidelines when deciding on keeping two articles separated or merged:
 
Follow these guidelines when deciding on keeping two articles separated or merged:
 
# Does item ''A'' have the same purpose/use as item ''B''?
 
# Does item ''A'' have the same purpose/use as item ''B''?
# Can item ''A'' be substituted with item ''B''?
+
# Can item ''A'' be substituted with item ''B''?
   
 
Common examples with answers to above questions:
 
Common examples with answers to above questions:
Line 25: Line 25:
 
** '''Decision:''' Merge
 
** '''Decision:''' Merge
 
* [[Achievement diary#Items/Accesses/XP|Diary reward items]]
 
* [[Achievement diary#Items/Accesses/XP|Diary reward items]]
*# No, higher level items have more abilities than lower level 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.
 
*# No, lower level items cannot be used in place for some higher level abilities.
 
** '''Decision:''' Keep separate
 
** '''Decision:''' Keep separate
Line 40: Line 40:
 
** '''Decision:''' If yes, merge. Otherwise, keep them separate.
 
** '''Decision:''' If yes, merge. Otherwise, keep them separate.
 
* [[Races|Different types of the same race]]
 
* [[Races|Different types of the same race]]
*# Either mostly yes, or no.
+
*# Either mostly yes, or no.
 
*# No. They might be the same race, but are different.
 
*# No. They might be the same race, but are different.
 
** '''Decision:''' Keep seperate for mostly yes and no at #1
 
** '''Decision:''' Keep seperate for mostly yes and no at #1
*Are the [[Solomon's General Store|reskins]] bought in the same purchase?
+
*[[Solomon's General Store]] reskins bought in the same purchase <ref>[[Forum:RS:G and Solomon]]</ref><br />*#Yes - Merge<br />*#No - Keep separate
*#Yes - Merge
 
*#No - Keep separate
 
   
 
==NPC granularity<ref>[[Forum:Changes to RS:G|Yew Grove: Changes to RS:G]] - NPC granularity</ref>==
 
==NPC granularity<ref>[[Forum:Changes to RS:G|Yew Grove: Changes to RS:G]] - NPC granularity</ref>==
Line 61: Line 59:
   
 
==Image granularity==
 
==Image granularity==
When items and NPCs which look identical in-game have separate articles, they should link to separate images<ref>[[Forum:Granularity for Files|Yew Grove: Granularity for Files]] - Separate images for separate items.</ref>. 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.
+
When items and NPCs which look identical in-game have separate articles, they should link to separate images<ref>[[Forum:Granularity for Files|Yew Grove: Granularity for Files]] - Separate images for separate items.</ref>. 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 organization, and reduces the work required if the images diverge.
 
Keeping separate images for separate items (or NPCs), even when they look identical, is less confusing, promotes organization, and reduces the work required if the images diverge.

Revision as of 21:41, 8 December 2012

Acorn 5
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 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:

  1. Does item A have the same purpose/use as item B?
  2. Can item A be substituted with item B?

Common examples with answers to above questions:

  • Potions
    1. Yes, all potions have the same effect when used.
    2. Yes, as 3-dose can be replaced with 4-dose.
    • Decision: Merge
  • Raw/cooked food
    1. 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.
    2. No.
    • Decision: Keep separate [2]
  • Food portions (eaten over multiple bites)
    1. Yes.
    2. Yes.
    • Decision: Merge
  • Diary reward items
    1. No, higher level items have more abilities than lower level items.
    2. No, lower level items cannot be used in place for some higher level abilities.
    • Decision: Keep separate
  • Items/Monsters with similar names
    1. No.
    2. No.
    • Decision: Keep separate
  • Charged items
    1. Yes, all charges essentially have the same purpose.
    2. Mostly yes, the charges can do the same thing at 1+ charges remaining.
    • Decision: Merge
  • Different/trimmed versions of armour/weapons
    1. 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
    1. Either mostly yes, or no.
    2. No. They might be the same race, but are different.
    • Decision: Keep seperate for mostly yes and no at #1
  • Solomon's General Store reskins bought in the same purchase [3]
    *#Yes - Merge
    *#No - Keep separate

NPC granularity[4]

NPCs with attackable counterparts or confirmed to be the same person should not be split unless there is a significant difference between the two incarnations.

Monster granularity[5]

  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[6]. 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 organization, and reduces the work required if the images diverge.

Exceptions

  • Actual players - per RS:PLAYERS
  • Summoning articles - A familiar and its respective pouch, scroll, and special attack, should be merged into one article, under the name of the familiar[7][8]
  • Longer dialogues, books and scrolls word-by word. Rephrasing is preferred.

Remember

Remember that as with any policy, use common sense instead of just blindly following the policy.

References

  1. ^ The Mountain goat, Ardal, Blacksmith working the bellows, and Troll cook articles were nominated for possible deletion in August 2008, July 2009, October 2009, and March 2010 respectively. This was on the basis that they were not "true" NPCs, but the consensus in all four cases was to keep their articles.
  2. ^ Forum:We need to enforce granularity Separate pages for raw/cooked food.
  3. ^ Forum:RS:G and Solomon
  4. ^ Yew Grove: Changes to RS:G - NPC granularity
  5. ^ Yew Grove: Monster granularity - Monster granularity
  6. ^ Yew Grove: Granularity for Files - Separate images for separate items.
  7. ^ Yew Grove: Familiar's Special Moves
  8. ^ Yew Grove: Archive 9 - Summoning Pouches