9,090
edits
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[File:Megami Tensei Wiki.png|250px|right|class=white]] | [[File:Megami Tensei Wiki.png|250px|right|class=white]] | ||
The '''gameplay''' policy of [[Community:{{SITENAME}}|{{SITENAME}}]] outlines how gameplay information should be covered. This page also explains the usage of '''stat table templates''' and '''skill data modules'''. | The '''gameplay''' policy of [[Community:{{SITENAME}}|{{SITENAME}}]] outlines how gameplay information should be covered. This page also explains the usage of '''stat table templates''' and '''skill data modules'''. | ||
The guidelines presented here are meant to serve as a guiding example and are not indicative of how to handle every gameplay-related matter on the wiki. | |||
==General== | ==General== | ||
| Line 92: | Line 94: | ||
====Locations==== | ====Locations==== | ||
A subject's encounter location (or how it | A subject's encounter location (or how it can be obtained) can be added to the <code>location=</code> parameter. This should merely state the name of the location with a link to its page, immediately followed by any floor numbers. For example: <code><nowiki>location=[[Daedalus Tower]] 1F</nowiki></code>. For allied subjects who can only be obtained through certain means, the location parameter can also be used to briefly describe the method. Examples: <code><nowiki>location=[[Fusion]] only</nowiki></code> (for standard fusions), <code><nowiki>location=[[Fusion Accident]]</nowiki></code>, <code><nowiki>location=Event at [[Old Suidobashi]]</nowiki></code>, <code><nowiki>location=Clear "[[Osiris' Resurrection]]"</nowiki></code> (for sidequests). | ||
Otherwise, the location parameter must be kept concise and be no longer than a short sentence. Any locations that would require a lengthier explanation should be explained outside of and prior to the stat table. | Otherwise, the location parameter must be kept concise and be no longer than a short sentence. Any locations that would require a lengthier explanation should be explained outside of and prior to the stat table. | ||
| Line 129: | Line 131: | ||
<code><nowiki>},</nowiki></code> is used to separate each additional skill. Skills are given a label in lowercase on the first line, which is the name that the Skill template will call a skill by. This label should generally be identical to the skill's in-game name, including any accents. Some games, however, have multiple variants of a skill with the same name. In these cases, each variant should be given a differentiator in their label, such as a number, an attribute, or a character's name. This allows the Skill template to reliably call specific variants of a skill. The skill's display name should otherwise remain how it is titled in-game. | <code><nowiki>},</nowiki></code> is used to separate each additional skill. Skills are given a label in lowercase on the first line, which is the name that the Skill template will call a skill by. This label should generally be identical to the skill's in-game name, including any accents. Some games, however, have multiple variants of a skill with the same name. In these cases, each variant should be given a differentiator in their label, such as a number, an attribute, or a character's name. This allows the Skill template to reliably call specific variants of a skill. The skill's display name should otherwise remain how it is titled in-game. | ||
With the exception of numbers, data entered into parameters must be enclosed by apostrophes. All parameters must be closed with a comma. If any parameters are entered incorrectly, the editor will highlight the error and require this be fixed before the module can be saved. If there is a possessive case in a skill name or description (such as Impaler's Animus), a | With the exception of numbers, data entered into parameters must be enclosed by apostrophes. All parameters must be closed with a comma. If any parameters are entered incorrectly, the editor will highlight the error and require this be fixed before the module can be saved. If there is a possessive case in a skill name or description (such as Impaler's Animus), a backslash must be added before the apostrophe. For example: <code>Imapaler\'s Animus</code>. | ||
Because the Skill template and skill data modules are made to be universal, skill data parameters must be kept consistent with each module on the wiki. Inconsistently named parameters will cause Lua errors. Some common skill data parameters are listed below. | Because the Skill template and skill data modules are made to be universal, skill data parameters must be kept consistent with each module on the wiki. Inconsistently named parameters will cause Lua errors. Some common skill data parameters are listed below. | ||