User:Mistiryshak/sandbox2
THIS IS A DRAFT AND SHOULD NOT BE CONSIDERED FINAL GUIDELINES
When describing the location of a subject on a stat table, the location row follows a set of guidelines on how to handle a variety of potential situations.
Locations should follow this general order, with a new line for each category using a line break (<br/>
):
- Mandatory locations in chronological order
- For titles with multiple routes, such as Megami Ibunroku Persona and Shin Megami Tensei V: Vengeance; each route will be placed on a new line only if the encounters between routes are mutually exclusive. Otherwise, for locations which share identical encounters across all routes, there is no need to specify route.
- For titles without a proper chronological order, the expected level range for encounters will be used as a last resort.
- Optional locations in access order
- For titles with optional locations and multiple routes that feature mutually exclusive locations, optional locations will be placed on the route's line following all mandatory locations, with the same ordering otherwise applied.
- Fusion-based locations only if the subject is exclusive to fusion (other than one-time events such as directly joining the party)
- Sidequests
- Events (prioritizing story events, then optional events, then gameplay-related events such as demons exclusive to evolution)
An example of a theoretical list that uses all kinds of locations follows:
|
Note that a location row is not intended as an exhaustive list of every possible way to encounter a subject. For example, outside of special fusions that require a specific combination, fusion combinations will not be listed. Additionally, locations should match the kind of stat table being used and the subject of a table, i.e. if the stat table is specifically about a boss fight, there is no need to specify the special fusion details for that boss demon, and if the stat table is for that same demon as an ally, there is no need to specify where the boss fight takes place. In practice, most stat tables should require at most two lines; though some titles or situations may require more.
For fusions of any kind that require an unlock condition, the parameter fusioncondition=
is used rather than placing the unlock condition directly into the location.