TibiaWiki:Standards/Items

Prior notice
If you cannot conform exactly to a standard, please don't. The standards are what are expected of completed articles, they are not like policies which you MUST follow at all times. Put another way: if a standard prevents you from contributing in some way (like adding a new article), do not feel pressured to follow it religiously.

Template

 * All items should use Template:Infobox Item. This page will describe the parameters and standards used for them.

Sprites

 * Item sprite should be designated on a per-item basis.
 * Item sprites should have the same name as the item's pagename, followed by the extension.
 * Item sprites should be in GIF format to allow lossless animations.
 * Item sprites should be as close to the original sprites.
 * If items animate (change frames over time) then the GIFs should also. Be as close to the in-game delay in the GIF animation.

Name

 * Required parameter. [name] should always be the same as [PAGENAME], which should be the same as the item's in-game name.
 * If the item name is shared with other items, parentheses should be appended to the name with a descriptive alternative text to distinguish the two items.
 * If the item name is shared with an object/creature/NPC, the item should get precedence over all else and accept the raw name form.

Flavortext
It can only be wielded properly by players of level 80 or higher. It weighs 42.00 oz. It's the Sword of Valor. It weighs 2.90 oz. This potion can only be consumed by knights and paladins of level 50 or higher.
 * Here are a few examples of what the flavortext part of an item's "look" message is.
 * You see a magic sword (Atk:48, Def:35 +3).
 * You see a strong health potion.
 * Although there seems to be a description, this is NOT the flavortext. Use levelrequired for this.
 * Flavortext should be the exact description as it is in-game.
 * If no flavortext is available it should be on the page but blank (|flavortext=). (no real reason for this but that it became common practice)

Item class

 * Required parameter. This is a TibiaWiki categorization of the item. It is very broad and takes an item from a defined list:
 * Body Equipment
 * Weapons
 * Household Items
 * Plants, Animal Products, Food and Drink
 * Tools and other Equipment
 * Other Items

Primary type

 * Required parameter. The [primarytype] parameter is a low level category of an item.
 * It should be a subclass of the itemclass's category. For instance, Snakebite Rod is a rod, and rods are weapons; itemclass should be weapons, primarytype should be rods.

Secondary type

 * Optional parameter. The [secondarytype] parameter functions similar to primarytype.
 * Unlike the primary type the secondarytype need not be a subclass of the itemclass.

Weight

 * Required parameter. The [weight] parameter is the weight (in oz) of the item.
 * The "oz." should be omitted as the template adds this automatically.
 * The number should be to two decimal places (e.g. 0.20, 250.00, but not 1.2).

Value

 * Required parameter. The [value] parameter is the approximate range at which the item will sell for ("street value").
 * If the item is rubbish (nobody would really buy it), the value should be 0.
 * If the item is worth hugely varying amounts, the value should be 'negotiable'.
 * Take into account that the value is an approximation on ALL game servers. Values may vary from server to server.

NPC value and NPC price

 * Required parameter. The [npcvalue] and [npcprice] are parameters for the best value to sell and to buy, respectively, from any NPC.
 * This parameter does NOT consider quests required. In other words, it assumes the best value at any point of any quest.
 * These parameters take a numerical value. It should be the value per piece.
 * Rookgaard NPCs are not considered, nor is the island of destiny.
 * Template:Price to Sell and ... Buy need to contain a list of items and their NPC values. It can only be edited by administraotrs. These templates work to prevent scam vandalism. If it's not up-to-date there are two possible issues:
 * If the item existed before it was last updated, the npcvalue will not accept a new npcvalue. This is a feature, it prevents editors from falsely changing values. In this case you should ask an administrator to update the list. Or you can add an exception in [buyfrom] / [sellto] which will
 * If the item did not exist before the update, the [npcvalue] / [npcprice] given will be assumed on good faith and added inside trades tables.

Example 1: Blueberry to Lily - she buys 5 at once for 0.2gp each; so the npcvalue should be 0.2 (1gp / 5 blueberries = 0.2)

Example 2: Parcel to Benjamin - he buys for 15gp or 10gp, depending on the quests completed. The npcvalue should be 10.

Rookgaard NPC value and price

 * Optional parameter. This is the same as npcvalue and npcprice above, but applied to Rookgaard NPCs. Do not use this parameter unless the item can be found on Rookgaard.

Dropped by

 * Required parameter. The [droppedby] parameter should be a list of creatures that drop the item.
 * List items should be separated with a comma and space (", ") and end in a full-stop.
 * Creatures should not be lowercase.
 * All creatures should be listed, not classes of creatures.

Buy from, sell to

 * Required parameter. The [buyfrom] and [sellto] parameters takes a list of NPCs this sells to.
 * If [newtradesystem=yes]:
 * [buyfrom], [sellto] should take a non-linked list of NPCs. If no such NPC exists, the sellto and buyfrom should be [--].
 * If there are value exceptions (e.g. [npcvalue] is not equal to NPC's buying value), use [NPC]: [exception value]
 * If there are notes, use [NPC]; [notes ID]. Notes ID can be found on Template:NPC Trades/Notes. If not, the notes can be supplied directly.
 * Notes need to be concise because there's a limit of 1,000 characters in the [sellto] and [buyfrom] values. It is highly recommended to put all notes on the notes template.
 * If the NPC buys the item for the npcvalue it should take no exception.
 * The trades system works closely with [npcvalue] and [npcprice], as well as Template:Price to Buy and Template:Price to Sell (these templates are the NPC counterparts: buys/sells). These need to be as accurate as possible.

Implemented

 * Required parameter. The [implemented] parameter is the version at which the item was added to the client files.
 * If known, this parameter should be a float number of the version at which an item was added to the client files.
 * Zero padding: version numbers should have at least one decimal place, and all zeroes after should be truncated. Use "8.0" and not "8", and "7.9" not "7.90".
 * This is not necessarily the version at which it became accessible to players.

Spoilers
Note: in this section "quest" refers to: world changes, mini world changes, quests except for "exchange quests".
 * The spoiler tag is specifically designed for use in the notes. It should not be used anywhere else. The following describes when a spoiler may be used on an item page. Note that the spoiler tags should encapsulate only spoiling content and nothing else.
 * If a quest is linked, it should be encapsulated in spoiler tags.
 * Quests should be linked in item pages when:
 * They are rewards of the quest.
 * They are consumed (lost) in completing a quest or part of a quest.
 * They have a specific use for a quest that are not used as general tools (e.g. Prepared Bucket but not Shovel unless the use of a shovel is different than the normal hole digging function).