8,438
edits
User:Rman41/Sandbox7: Difference between revisions
Jump to navigation
Jump to search
→Proposal of Preferences
| Line 18: | Line 18: | ||
This contains many changes from the current system, but may be more applicable broadly. | This contains many changes from the current system, but may be more applicable broadly. | ||
*'''Introductory Row''': Largely unchanged for almost every template. | *'''Introductory Row''': Largely unchanged for almost every template. | ||
*'''Compendium Row''': Currently, this is the Location on most templates, with some exceptions. Instead, it will now be what the third row is, with some changes. This is what I will call the "Compendium Row", and contains information that is related to the non-statistical aspects of a Demon outside of Battle, such as its Compendium Cost (which currently is on only a few templates), whether or not it appears in Random Encounters (or Shuffle Time for ''Persona''), its fusion condition if applicable, and its location. For the Location parameter, I am suggesting a significant change; instead of listing every location outright in the multitude of different ways we currently do this, I suggest limiting to only the first location and putting the rest in an Exp tooltip. I believe that this is a cleaner solution, as some of these lists can get very long. | *'''Compendium Row''': Currently, this is the Location on most templates, with some exceptions. Instead, it will now be what the third row is, with some changes. This is what I will call the "Compendium Row", and contains information that is related to the non-statistical aspects of a Demon outside of Battle, such as its Compendium Cost (which currently is on only a few templates), whether or not it appears in Random Encounters (or Shuffle Time for ''Persona''), its fusion condition if applicable, and its location. For the Location parameter, I am suggesting a significant change; instead of listing every location outright in the multitude of different ways we currently do this, I suggest limiting to only the first location and putting the rest in an Exp tooltip. I believe that this is a cleaner solution, as some of these lists can get very long. Both Fusion Condition and Location should be optional parameters on every template where they are present, only appearing if they have an input. | ||
*'''Stat Row''': The function of this row currently varies wildly depending on the template. It sometimes has a mishmash of random miscellaneous stats, and so I have decided to appropriate it entirely to that purpose. In this, I have also moved HP and MP/SP to the start of this row. I have also put the Drop on this row, though necessarily the Drop may need to become its own row depending on the game. That row, if it is necessary, should be placed below the Stat Row. The Stat Row itself may be combined with the Compendium Row if the amount of information would be too little to justify its own existence, but in doing this, Cost, Random Encounter, Fusion Condition, and Location should all remain to the very right. | *'''Stat Row''': The function of this row currently varies wildly depending on the template. It sometimes has a mishmash of random miscellaneous stats, and so I have decided to appropriate it entirely to that purpose. In this, I have also moved HP and MP/SP to the start of this row. I have also put the Drop on this row, though necessarily the Drop may need to become its own row depending on the game. That row, if it is necessary, should be placed below the Stat Row. The Stat Row itself may be combined with the Compendium Row if the amount of information would be too little to justify its own existence, but in doing this, Cost, Random Encounter, Fusion Condition, and Location should all remain to the very right. | ||
*'''Resistance Row''': This row actually describes what would likely be a multitude of rows for information with many entries. If they exist, Resistances should be at the top, with Ailment Resistances, Moon Cycles, Skill Potential, Inheritance, or any type of type of similarly structured data following. If there exists a Type system for that type of structured information, such as Inheritance Types, that should be allocated to the bottom right corner of its row. | *'''Resistance Row''': This row actually describes what would likely be a multitude of rows for information with many entries. If they exist, Resistances should be at the top, with Ailment Resistances, Moon Cycles, Skill Potential, Inheritance, or any type of type of similarly structured data following. If there exists a Type system for that type of structured information, such as Inheritance Types, that should be allocated to the bottom right corner of its row. | ||