Wiki contribution guide

The wiki doesn't currently have a strictly enforced style guide or set of rules, so this page is mostly a list of useful templates and some tips on how to use them. If you're not sure how to write an article, check others on the wiki. Even setting up a basis for a more fleshed out article is a good contribution!
==Categories==
Don't forget to add each page you make to proper categories. Start with the very basic like :Category:Characters, :Category:Locations etc. and then use more specific categories like :Category:Sejan locations. Make sure to check if the categories you're adding to the page actually exist!
==Infoboxes==
Infoboxes are important for short, simple and elegant list of information on various types of subjects. Add them to the beginning of articles with their attributes filled in, like this:
{{Template|
| name = John
| death_metal = Not Dead.
}}
===Character information===
Use the template InfoCharacter on any page about a sapient, talkable person in the game. The title of it is automatically taken from the page title. It has the following attributes:
Name 	Description
image 	Fits an image to the template.
caption 	A short description underneath the image. Can point at the character's current situation in the picture.
gender 	The character's sex. Due to the nature of the game, there don't have to only be males and females but androgynous or other characters as well, eg. Breirb.
species 	Some characters' species are known, mostly by a mention in dialogue. If not, use "Unknown".
bodytype 	A short, general description of the character's body. Humanoid, quadruped, lizard, furred, insectoid, eldritch, you name it. Try to keep it simple.
location 	The character's locations. Usually it's just the default one, but some characters can change their default encounter places. For example, players first meet Shyni in the market before moving to her garden.
sexscenes	The displayed name is "Player romance", but it still mostly refers to yes/no for actual explicit scenes. Specify for what player character genders the romances are available (eg. Shyni is available for both sexes while Tornoth is only for female characters)
===Creature information===
Use the template InfoCreature on any page about a feral animal or creature in the game (usually encountered randomly, though there are some exceptions). The title of it is automatically taken from the page title. It has the following attributes:
Name 	Description
image 	Fits an image to the template.
caption 	A short description underneath the image. Can point at the creature's current situation in the picture.
bodytype 	A short, general description of the creature's body. Humanoid, quadruped, lizard, furred, insectoid, eldritch, you name it. Try to keep it simple.
danger 	How dangerous the animal is. Currently all creatures are non-lethal; they can attack the player and defeat them but not kill them.
location 	Where the creature can be encountered. Randomly encountered beasts can usually be found across multiple spots on the map but they're nonetheless of the same tile type.
sexscenes	Whether or not the player can engage in bestiality with the creature (usually upon victory in combat). Specify the creature and player sexes, too (eg. "females on male players; males on female players")
===Location information===
Use the template InfoLocation on any page about a large map location. Don't use it for small encounters like Sejan lake but for big areas like Sejan. The title of it is automatically taken from the page title. It has the following attributes:
Name 	Description
image 	Image of the area, usually taken from the game map. Use this attribute for non-interactive images.
image_map 	If you want to specify an image map (a picture with clickable link areas), use this instead of image.
map_data 	If using an image map, specify the location data here. The ImageMap extension is used here.
caption 	It's a caption. Just some short description or fluff.
place 	Where in the overall game world the location is situated in.
type 	Type of the location - a big island, a peninsula, a sea, a desert, etc.
climate 	The climate of the place. It can be anything from arctic to a scorching desert.
flora 	Specify whether or not the place has plants and the overall type (forests, meadows, etc.)
fauna 	Specify whether animals live here; if they do, are they dangerous?
settlements	List of the biggest sapient creature settlements.
hazards 	Most notable hazards; fauna can be added here but the section is mostly used for geological hazards, eg. toxic air, volcanoes, extreme weather etc.
===Settlement information===
Use the template InfoSettlement on any page about a localised habitated area like a village or a city. The title of it is automatically taken from the page title. It has the following attributes:
Name 	Description
image 	Image of the settlement, usually a map or an overhead view.
caption 	It's yet another caption!
place 	Location of the settlement, usually relative to a large-scale place it's in like Sejan.
type 	The type of the settlement; a village, town, camp, city, isolated prison, military base, whatever.
population	The overall population.
people 	Currently known and approachable characters.
hazards 	Dangers of the settlement (mugglers, corrupt leadership, industrial hazards, etc.)
===Inventory item information===
Use the template InfoInventory on any page about any inventory item, be it a weapon, clothing, armour, utility or quest item. Unlike the previous templates, this one doesn't take its header text from the page title and needs to be specified along with other attributes. It has the following attributes:
Name 	Description
name 	The item name.
image 	Optional image of the item. Weapons and clothing have this, utility and quest items do not.
caption 	The in-game description of the item. Don't make one of your own, use only what's in the game!
adats, krats 	Value of the item in adats and krats respectively.
slot 	Where the slot is equipped, depending on it being a weapon, a clothing article or an unequippable item. Use the following values: head, torso, legs, socks, shoes, hands (for clothes), main hand, offhand, sidearm (for weapons) or inventory (unequippable utility/quest items)
heat_res, cold_res, impact_res, slash_res, pierce_res, magic_res, bio_res	For clothing, respective resistances to heat, cold, impact, slash, piercing, magic, and biological attacks.
attacks 	Combat move cards given to the player when equipped. Specify their number, as well.
===Cards information===
Cards in the game are moves to be used during combat. Player has some melee moves from the get-go and can acquire more through finding weapons or learning moves. If an item page concerns a weapon that gives the player a card, use the InfoCards template. Just like InfoInventory, the title isn't automatically taken from the page name but has to be filled in manually. There are the following attributes:
Name 	Description
name 	The name.
caption 	The in-game description. Don't make up your own, use only what's in the game and transcribe it verbatim, typos included.
type 	Type of the card. Currently there are only melee and weapon attacks available but other, more defensive moves are planned for the future. The following types are available: unarmed attack, weapon attack, counter move, damage reduction, buff, debuff, escape, debug
cost 	How much the card costs to use during combat. Usually only takes some of the attributes but there can be also a hitpoint cost.
damage 	How much damage and of what kind the card does, if any. Specify the type of damage (the same types like in resistances).
special 	A currently unimplemented feature that's probably meant to make the card do special actions with a certain percentage chance. Known values are escape, evasion, reflect, damage reduction and interrupt card, followed by the percentage. As of now, do not use.
available	Who or what the card is available from. Since card templates are usually on the same page as their parent weapon, you can usually leave this one out, too.
==Infobox stacking==
If you want to have multiple infoboxes above each other, you can use the info_container table class. Otherwise, infoboxes will be displayed next to each other and to circumvent it, one would need a large amount of empty lines. Here's an example of how it works:
{| class="info_container"
|-
|{{InfoInventory|
| name = Bread knife
| image = weapon_bread_knife.png
| caption = A flat knife made for cutting bread. Its odd handle doesn't fit your hand properly.
| adats = 1
| krats = 0
| slot = Sidearm
| attacks = 2x knife slash
}}
{{InfoCards|
| name = Knife slash
| caption = A slashing attack with a small, bladed weapon.
| type = Weapon attack
| cost = AGI 2
| damage = Slash 2
}}
|}
All templates are in a single table cell. This makes a difference between the two example screenshots above.
==Warning banners==
There are two banners currently available that warn the readers of an article being either outdated (BannerOutdated) after a new version release, or not applicable to the game as its content is not in the game yet (BannerUnreleased).
BannerOutdated has one variable field - version (version) of the game the current article applies to. So, if a page was written during v1.13 of the game and v2.0 is released, you should add the banner template to it if the update affects it. 
BannerUnreleased automatically adds :Category:Unreleased content to the page, unless nocategory is specified. Under most circumstances, don't use this modifier.
==Navboxes==
There is currently only a single navbox available and that's the one for Sejan, Navbox Sejan:
==Table classes==
A table class was already mentioned above in infobox stacking, but there's one that's much more common and useful. Whenever you use a table in an article, use the tutable class for it. It uses its own formatting including automatically alternating row background colours.
{| class="tutable"
|-
!Header left
!Header right
|-
|Fruits
|Papaya, mango, banana, grapefruit
|-
|Furnaces
|Natural draft, forced-air, forced draft, condensing; single-stage, two-stage, modulating
|-
|Reactions to my death
|Ouch, oof, owie
|}
Header left 	Header right
Fruits 	Papaya, mango, banana, grapefruit
Furnaces 	Natural draft, forced-air, forced draft, condensing; single-stage, two-stage, modulating
Reactions to my death	Ouch, oof, owie
Of course, the table class is also compatible with HTML-style tables, which can be useful with complex tables.
Category:Modding and development