<p>Not much text, mostly ability descriptions, but TL;DR at bottom.
</p><p>Furthering from my
previous post, I've come to notice as of late further inconsistencies in ability descriptions, mainly involving the usage of Keywords. Keywords are things such as, but not limited to, ability specific mechanics, and ability specific buffs. For example, here is a copy of Ekko's current passive.
</p><p><i>Note the uses of
Resonance,
Stolen Time, and
Stabilized.</i>
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p><span class="inline-image label-after ability-icon" data-param="" data-champion="Ekko" data-ability="Z-Drive Resonance" style="display:inline;white-space:pre;"><span data-width="20" class="border" style="display:inline-block;position:relative;">

</span> <span style="white-space:normal;">
Z-Drive Resonance</span></span>
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p>Now compare that to a more classical format which still does use Keywords.
</p><p><i>Note the uses of
Ravenous and
Flock, and how they're both preceded by
Innate.</i>
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p><span class="inline-image label-after ability-icon" data-param="" data-champion="Swain" data-ability="Ravenous Flock" style="display:inline;white-space:pre;"><span data-width="20" class="border" style="display:inline-block;position:relative;">

</span> <span style="white-space:normal;">
Ravenous Flock</span></span>
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p>Furthering on from this is the uses of Keywords in the
Active statement of abilities, such as the following.
</p><p><i>Note the use of
Broken Timeline after
Active.</i> To my knowledge, this is the only ability to utilize this format, but it wouldn't surprise me at this point if there are more.
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p><span class="inline-image label-after ability-icon" data-param="" data-champion="Ekko" data-ability="Chronobreak" style="display:inline;white-space:pre;"><span data-width="20" class="border" style="display:inline-block;position:relative;">

</span> <span style="white-space:normal;">
Chronobreak</span></span>
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p>An alternative utilization of Keywords is also for the simplification of (writing) ability descriptions. However sometimes this method can become rater counterproductive, specifically in cases where the uses of Keywords are either redundant or harmful.
</p><p>Note the differences between the two ability descriptions below, primarily on how
Demon Shade is a Keyword meant to describe a buff given post-condition, versus how
Primed is a Keyword that is not very conditional, but rather sequential to the first part of Phase Dive.
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p><span class="inline-image label-after ability-icon" data-param="" data-champion="Evelynn" data-ability="Demon Shade" style="display:inline;white-space:pre;"><span data-width="20" class="border" style="display:inline-block;position:relative;">

</span> <span style="white-space:normal;">
Demon Shade</span></span>
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p><span class="inline-image label-after ability-icon" data-param="" data-champion="Ekko" data-ability="Phase Dive" style="display:inline;white-space:pre;"><span data-width="20" class="border" style="display:inline-block;position:relative;">

</span> <span style="white-space:normal;">
Phase Dive</span></span>
</p>
<div style=";border-top:1px solid #3a4652"></div>
<p>Originally, Ekko's Phase Dive used to describe how he would gain the secondary effects of the ability proceeding the dash, rather than listing
Primed Keyword. I believe this to be a case of redundancy, whereas
Demon Shade is not in contrast, due to it being conditional.
</p><p><i>Both of these Keywords are buffs with the corresponding in-game names as far as I know, so the question here is how should we proceed with the use of Keywords?</i>
</p><p>My proposal is that for Keywords (and TL;DR):
</p>
- For champion passives we utilize the <i>classical format</i> (Keywords preceded by Innate, like Swain's Ravenous Flock; every separate effect is to be preceded by Innate, which isn't the case for some multi-effect passives at the moment, like Senna's)
- For Active statements we do <i>not</i> utilize them (Keywords are never to be used proceeding <span style="font-weight:bold; font-size:89%; text-transform:uppercase;">Active:</span> like how it is done with Ekko's Chronobreak).
- For conditional buffs we <i>do</i> utilize them. For sequential buffs we do <i>not</i> utilize them (damage dealt, no damage taken, sweet spot, etc conditional, vs. sequential or flavour). For iffy instances, we are to be sensible, understanding, and willing to compromise with each other's edits. <i>An ability striking something is not conditional, it is how abilities are able to even begin interacting with an entity.</i>
<p>Cons of my proposals for each of my points above respectively:
</p>
- Can get wordy with the multiple uses of Innate.
- Deprives flavour.
- Requires maintenance and peer review for consistency.
<p>Personally I don't see the point in the use of Keywords at all other than flavour (which should be second to efficient delivery of information), but by now there's probably been too much work put into this by many people to wipe it all out. Sunk cost fallacy, whatever. Maybe it could even be argued that putting names on them makes them more identifiable/recognizable (probably bs).
</p>
<div>
{{Question}}
Question —
</div>
<div>
{{Support}}
Support —
</div>
<div>
{{Neutral}}
Neutral —
</div>
<div>
{{Oppose}}
Oppose —</div>