9,090
edits
no edit summary
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
However, for characters who only appear in one series, the series sections are not necessary and the game sections may be formatted as Level 2 subsections <code><nowiki>==Level 2==</nowiki></code> instead. | However, for characters who only appear in one series, the series sections are not necessary and the game sections may be formatted as Level 2 subsections <code><nowiki>==Level 2==</nowiki></code> instead. | ||
Characters with [[Social Link]] information in the {{Link|Series|P-}} should be given their own Gameplay pages due to the highly comprehensive nature of this mechanic. See the [[#Social Links]] section for more information. | Characters with [[Social Link]] information in the {{Link|Series|P-}} should be given their own Gameplay pages due to the highly comprehensive nature of this mechanic. See the [[#Social Links|Social Links]] section for more information. | ||
==Listings== | ==Listings== | ||
| Line 55: | Line 55: | ||
==Stat Tables== | ==Stat Tables== | ||
Stat tables are specialized templates used to display statistical information about playable characters, Demons, Personas, etc. This can include stat | Stat tables are specialized templates used to display statistical information about playable characters, Demons, Personas, etc. This can include stat values, weaknesses and resistances, skills, passive traits, victory spoils, location information, and whatever else that is pertinent to the game and subject. Because of the specified nature of stat tables as well that games across the ''Megami Tensei'' franchise can vary greatly with their mechanics, each game has their own dedicated stat tables. A game may have separate stat tables used specifically for allies, enemies, bosses, and others depending on its individual needs. | ||
[[:Category:Stat Table Templates]] has a full list of available stat tables. | [[:Category:Stat Table Templates]] has a full list of available stat tables. | ||
| Line 61: | Line 61: | ||
Stat tables have a range of information parameters that will display formatted data when filled. Any information added should be sourced from the games wherever possible, such as from a stat screen or from data-mining. Information can also be sourced from official guide publications as well; however, be aware that even some official guides have also been known to contain errors and may not always be 100% accurate. It is therefore recommended to cross-reference any sources used. | Stat tables have a range of information parameters that will display formatted data when filled. Any information added should be sourced from the games wherever possible, such as from a stat screen or from data-mining. Information can also be sourced from official guide publications as well; however, be aware that even some official guides have also been known to contain errors and may not always be 100% accurate. It is therefore recommended to cross-reference any sources used. | ||
Skill information are stored in data modules, which can then be called into the stat table and automatically adds the appropriate data. See the [[#Skills|skills]] and [[#Skill Data Modules|skill data modules]] sections for more information. | |||
Information added to stat tables should be kept concise wherever possible, being no more than a sentence long. At times, there may be complicated information that would otherwise become too lengthy to explain within a stat table. In such cases, the information should instead be presented outside of the stat table as a short sentence or paragraph. For example: In ''Shin Megami Tensei'', Fiends have a 1 in 256 chance of spawning on specific tile coordinates in dungeons. Because of this complexity, their encounter location should be explained as a paragraph before the stat table and not within it. | Information added to stat tables should be kept concise wherever possible, being no more than a sentence long. At times, there may be complicated information that would otherwise become too lengthy to explain within a stat table. In such cases, the information should instead be presented outside of the stat table as a short sentence or paragraph. For example: In ''Shin Megami Tensei'', Fiends have a 1 in 256 chance of spawning on specific tile coordinates in dungeons. Because of this complexity, their encounter location should be explained as a paragraph before the stat table and not within it. | ||
| Line 71: | Line 71: | ||
For quick ease of use, most stat tables are automated where they will automatically fill in the name of the subject based on the article's title. It is possible, however, to override this and input a different name by using the <code>name=</code> parameter. This should be used if the subject's name differs in-game from the article's title, or if the article title has a discriminator in it. | For quick ease of use, most stat tables are automated where they will automatically fill in the name of the subject based on the article's title. It is possible, however, to override this and input a different name by using the <code>name=</code> parameter. This should be used if the subject's name differs in-game from the article's title, or if the article title has a discriminator in it. | ||
The name of the subject should reflect the name used in the game's localization. I.e. Jack-o'-Lantern should be referred to as "Pyro Jack" in games that use this name. The exceptions to this are {{Link|Game|MIP}}, {{Link|Game|LB1}}, and {{Link|Game|DCLD}}, which should instead prioritize the original names of characters and enemies, as opposed to their ''Revelations'' and ''DemiKids'' localization names (as per our [[Guidelines:Canon#Localization versus Japanese Canon|canon policy]]). However, these games also have additional parameters to list their localization names separately as well. | The name of the subject should reflect the name used in the game's localization. I.e. Jack-o'-Lantern should be referred to as "Pyro Jack" in games that use this name. The exceptions to this are {{Link|Game|MIP}}, {{Link|Game|LB1}}, and {{Link|Game|DCLD}}, which should instead prioritize the original names of characters and enemies, as opposed to their ''Revelations'' and ''DemiKids'' localization names (as per our [[Guidelines:Canon#Localization versus Japanese Canon|canon policy]]). However, stat tables for these games also have additional parameters to list their localization names separately as well. | ||
====Image==== | ====Image==== | ||
| Line 83: | Line 83: | ||
In this context, "stats" refer to the inherent data with each character that are often used for battle. This can include the common array of stat values: Level, HP, MP, Strength, Dexterity, Vitality, Magic, Agility, Luck, etc. This also includes miscellaneous data such as Race, behavioral types such as [[Speech Pattern]] or [[Moon Phase]], associative summoning costs, and so on. | In this context, "stats" refer to the inherent data with each character that are often used for battle. This can include the common array of stat values: Level, HP, MP, Strength, Dexterity, Vitality, Magic, Agility, Luck, etc. This also includes miscellaneous data such as Race, behavioral types such as [[Speech Pattern]] or [[Moon Phase]], associative summoning costs, and so on. | ||
Stat data are added simply by entering them into their appropriate parameters. Stats that have a visual gauge in-game will also have these rendered automatically. Some stat parameters in stat tables are optional; if a particular stat is not applicable to a subject, its parameter should be omitted from usage. This will either hide the parameter or otherwise add an em dash to denote as non-applicable. | Stat data are added simply by entering them into their appropriate parameters. Stats that have a visual gauge in-game will also have these rendered automatically. Some stat parameters in stat tables are optional; if a particular stat is not applicable to a subject, its parameter should be omitted from usage. This will either hide the parameter's cell or otherwise add an em dash to denote as non-applicable. | ||
Stats that can grow or change should only reflect the base / default value inherent to the subject. | Stats that can grow or change should only reflect the base / default value inherent to the subject. | ||
| Line 96: | Line 96: | ||
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. | ||
If a subject appears in more than one location, the earliest appearance should be added to the parameter. Subsequent locations can be added | If a subject appears in more than one location, the earliest appearance should be added to the parameter. Subsequent locations can be added as an [[Template:Exp|Exp tooltip]] after the initial appearance with a line break for each location. For example: <code><nowiki>{{Exp|Location 2F-3F<br/>Location 5F, 7F}}</nowiki></code>. | ||
====Resistances==== | ====Resistances==== | ||
| Line 127: | Line 127: | ||
}, | }, | ||
</pre> | </pre> | ||
<code><nowiki>},</nowiki></code> is used to separate each additional skill. 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 backlash should 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. | ||
| Line 352: | Line 352: | ||
==Specific Gameplay Coverage== | ==Specific Gameplay Coverage== | ||
===Persona User Stats=== | |||
In {{Link|Game|MIP}} and the ''[[Persona 2]]'' duology, party members have their own distinct stats that are either changed or augmented by their currently equipped [[Persona (Concept)|Persona]]. Party members in these games should therefore be given their own stat tables. "Signature Persona" stats (i.e. Personas that can only be equipped by certain characters) may also be included on the character's page in their own [[#Tabs|tab]]. | |||
In {{Link|Game|P3}}, {{Link|Game|P4}}, and {{Link|Game|P5}}, all characters' stats mirror their current Persona, with the exception of their HP and SP stats. Party members should have their own stat table documenting their base HP and SP values along with any starting equipment, while their inherent Persona(s) should be documented in separate tabs. | |||
Stat table tabs should be named after the character or Persona they apply to. For spoilery "ultimate Personas", is it acceptable to label the tab as <code>Ultimate Persona</code> to avoid immediate spoilers. | |||
===Social Links=== | ===Social Links=== | ||
Due to the highly comprehensive nature of [[Social Link]] mechanics in the {{Link|Series|P-}} (known as Confidants in ''Persona 5''), any character with Social Link information needs to be given their own [[#Gameplay Pages|Gameplay page]]. | Due to the highly comprehensive nature of [[Social Link]] mechanics in the {{Link|Series|P-}} (known as Confidants in ''Persona 5''), any character with Social Link information needs to be given their own [[#Gameplay Pages|Gameplay page]]. | ||
| Line 369: | Line 376: | ||
</pre> | </pre> | ||
For page brevity, Rank Up Events should each be placed into a [[#Tabs|tab]]. | For page brevity, Rank Up Events should each be placed into a [[#Tabs|tab]]. The tabs should be labeled after the rank number. I.e. <code>Rank 1</code>. | ||
For party members who are also Social Links, battle stats should be prioritized first, following this outline: | For party members who are also Social Links, battle stats should be prioritized first, following this outline: | ||
| Line 381: | Line 386: | ||
===Rank Up Events=== | ===Rank Up Events=== | ||
</pre> | </pre> | ||