User:Joenuts/Item enchantment template policy

Item property template names shall match exactly ( case sensitive ) the item property as it exists in the game, with the following exceptions :


 * When an item property contains a number which describes the degree of the modification
 * The template shall be defined to allow for a variable to be passed in to reference the degree of the modification
 * The value of the degree passed in should match exactly what is displayed in the item modification title ( 20% / -3 / +13 / IX )


 * When an item property exists with the same name, but exhibits different behaviour
 * The property template name shall match the item property title ( referred to as the parent template )
 * The parent template shall be defined to require a variable named "type" to be passed in to determine which child template should be transcluded
 * In the case where a type variable is not sent to a parent template, parent template should display output directing caller to usage page for template
 * A child template shall be created for each behaviour associated with the item modification
 * Child template shall be named in the format "[Item property] [type]"


 * Where multiple item properties share common descriptions, a meta template should be created to output the common description
 * The meta template shall be designed to be passed as many variables as is necessary to prevent any logic ( if or switch statements ) from having to exist in the meta template
 * Meta templates created for item property descriptions shall be named in the format "[Item property] Description"

Examples :
 * Basic item property that requires no variable


 * Item property that requires a single variable to reference magnitude


 * Item property that requires a "type" variable to reference type and more variables based on child template to be transcluded

Template shall be created with four chapters ( Usage, Examples, Categorization, Coding )
 * The first three chapters ( Usage, Examples, Categorization) shall be contained within tags
 * The last chapter ( Coding ) shall be contained within tags
 * Usage shall list each variable allowed by the template, and give up to three examples of values that should be used for that variable
 * Examples shall give up to three examples of how the template may be called
 * Categorization shall document the categories that are injected by the template
 * Template shall be added to the "Item description templates" inside the Categorization chapter
 * Coding shall store any code that is transcluded in to other pages
 * Coding shall store a category injection statement which verifies that page is in "Item" namespace before injecting category