RuneScape:Style guide/Drop tables

This page outlines the proper way to format drops tables for monsters.

Organising
Drops should by organised by the drop slot they occupy. The tables should be organised in the following order, eliminating any tables that do no exist for a particular monster:


 * 100% drops
 * Charms
 * Main drop
 * Tertiary drops
 * Rare drop table
 * Universal drops

An explanation of each is outlined on the drops article.

DropsLine
The DropsLine template should be used to create drops tables. It has 4 necessary parameters every time it is used:


 * - The name of the item exactly as it appears in game
 * - The amount of the item dropped. Quantities should be separated by a comma, with ranges indicated by a hyphen (-). In display, these will be replaced with semicolons and endashes (–) respectively.
 * - The subjective rarity of the item's occurrence. Unfortunately, due to lack of information, there is no threshold on drop chance that can set an item into any category (with the obvious exception of 100% being always). Use your best judgement; ask yourself "How likely am I to see this drop in X kills?"
 * - Whether or not this item can be traded on the Grand Exchange. If an item can be traded, delete this parameter. If an item cannot be traded, set this parameter to "no".
 * Coins, while not tradeable on the Grand Exchange, are automatically handled by the module, and thus they can have this parameter eliminated.

Additional parameters

 * - Space for a reference regarding the item itself. This should be used with for indicating items that are always dropped together. For members only items that appear on non-members monsters' drops tables, use (m).
 * - Space for a reference regarding the quantity of an item dropped. If a certain quantity can only be obtained in a certain location, use this space to indicate such.
 * - Space for a reference regarding the rarity of an item or the order in which it is dropped. Examples of references to use here are:
 * Confirmed drop rates
 * X dropped before Y
 * Changes in rarity based on conditions, including one-off drops
 * - Direct change to the cost of an item. This should only be used if the item can be reliably exchanged by anyone for an invariable number of coins. The ancient artefacts (e.g., bandos scrimshaw) are examples of items with an appropriate alt value.
 * - The image of an item if the desired image does not match the item name directly, in the format Filename.png. Instances where this is not necessary:
 * Coins, which are handled by the module itself
 * Seeds and other stackable items that have a redirect for unnumbered file names

Format
Ideally, all drops tables should format their syntax in a consistent manner so that editing is easier (particularly automated editing).

Tables should begin with DropsTableHead and end with DropsTableBottom, each on their own line. No empty lines should separate any template between these two. Each DropsLine should be on its own line, and only that line, with the following parameter order (eliminating unused parameters):


 * Name
 * Namenotes
 * Quantity
 * Quantitynotes
 * Rarity
 * Raritynotes
 * gemw
 * AltValue
 * Image


 * Example syntax

Wrapped templates
Due to the nature of their drops, the following sets of items should be wrapped in separate templates in place of multiple DropsLines:


 * DropsLineSpiritGems - Spirit sapphire, Spirit emerald, Spirit ruby
 * DropsLineTriskelion - Crystal triskelion fragment 1, Crystal triskelion fragment 2, Crystal triskelion fragment 3

Rare drop table
The Rare drop table should be included as both an entry in "Main drop" and as a separate section to include the entire table itself. The "Rare drop table" section should appear after "Tertiary drops" and before "Universal drops". It should always be formatted under the same header and use Rare drop table.


 * Example

Main drop
... ...

Tertiary drops
... ...

Universal drops
The "Universal drops" section should be included on every monster that has access to these drops. Unlike the rare drop table, access to universal drops should not be included in any other table. It should always follow the same format: