Template talk:Related skills

Minion skills

I'd like to propose the addition of a new section for summoned allies showing certain monster skills, possibly those tagged with new NPC and NPC source parameters, which would preferably show the source NPC and what summons the NPC respectively, using properties [[Property:Is for NPC]] and [[Property:Has NPC summon method]]. Alternatively, NPC source could be listed in the NPC infobox. Sunlion (talk) 00:00, 4 November 2021 (UTC)

This is about skills used by NPCs/objects documented on Summons. The questions are which parameters do we need and how do we label the internally, i.e. Has skill supertype and Has skill context.

Questions:

1. How do we want to label skills used by summons? For example:
   • Illusionary Berserker is summoned by the mesmer skill Phantasmal Berserker and uses the skill Phantasmal Berserker (phantasm).
     • So should this be either labelled as skill supertype "Monster" (that's how we currently document NPC skills) and skill context "Summon" or should it inherit the skill supertype from the parent summon skill, namely it's only usable by Mesmers and thus the skill used by the NPC still has the skill supertype "Profession" (again with the skill context "Summon")? Note that this is independent from using the parameter profession as the supertype could be set to "Monster" while at the same time the parameter profession could be set to "Mesmer" (to document the profession relation and get the profession related colour scheme).
   • Snow Wurm is summoned by the norn skill Call Wurm and uses the skill Wurm Spit.
     • Again, does it make sense to inherit "Racial" as the skill supertype or set it to "Monster"?
   • Jade Armor is summoned by the consumable Pocket Jade Armor and uses the skill Punch.
     • Once more, what should be the skill supertype? Should it be "Common", i.e. the skill supertype that is used for skills that are usable by any player (does not require any specific profession/race), or should it be "Monster"?
   • Recap: for me there are two possible methods:
     1. Method 1: Label these skills by their inherited supertype. This method makes sense for "profession" and "racial" related skills, might get a bit awkward for consumable skills though. However it allows easier tracking as we can directly access a certain group of skills used by summons. For example we could directly ask for all skills used by summons that have the skill supertype "Profession" and get phantasm used skills (related to mesmer), minion used skills (related to necromancer), elemental used skills (related to elementalist), here we would have to add an additional section summons (calling Skill list with the skill supertype "Profession" and the skill context "Summon"). Furthermore, skills used by summons related to racial skills would directly show up in the current section "Racial" on this template. Overall this approach would treat skills used by summons as an extension of the player.
     2. Method 2: Label these skills as "Monster" skills (or whatever we want to rename this supertype). This approach treats the skills used by summons as pure NPC skills, independent from their summon origin. Thus it would be harder to ask for them as profession-related, racial-related and common-related skills since they have all the skill supertype "Monster". Unlike the previous approach this would require also two new sections for racial and common and yet it might not be possible at all (how to even query for non-profession-related and non-racial-related skills?). We probably have to heavily extend the skill sort properties and put all three into one section, mixing profession-related, racial-related and common-related skills used by summons (not really a fan of this, as this for example would require a new racial number sort property).
2. Currently we are documenting NPCs skills with skill supertype "Monster" which are set with the infobox parameter monster and stored in the property Is for monster.
   • Should we keep this or should we switch the skill supertype from "Monster" to the more common term "NPC". Furthermore, should we rename the parameter monster to NPC and store it in the suggested property Is for NPC?
   • Note that this also depends on how we answer the previous questions.
3. The NPC summon method is a pure NPC infobox parameter/property, that should be quite straigth forward, so leaving it aside for now.

So far I haven't decided for a label method yet (see question 1), but method 1 seems easier to implement while method 2 might be more technical correct but is definitely harder to deal with. -Tolkyria (talk) 09:37, 4 November 2021 (UTC)