Template:Hero Changelogs/doc

Formatting notes for Hero Changelogs.

Hero Added/Reworked

 * Bold Reworked Hero ID, you may merge Added and reworked together in a sentence.
 * Insert attributes and other mechanics reworked in the middle.
 * Add hero's new basic abilities and new ultimate ability in a sentence.
 * Format new abilities according to New reworked abilities.

. (other attributes and mechanics changes in the middle) .
 * Reworked . (To see the previous Hero, see here).
 * Hero now has, , as their basic ability and  as their ultimate ability.

Hero Mechanics

 * 1st level bullet list for all Hero Mechanics changes.
 * Prioritize other mechanics first (health/mana/base attack time etc.), then Hero attributes.
 * Base attributes ( / / ) and attribute gain should be separated, state base attributes value changes first, attribute gain value changes next.
 * Use ability trait names and avoid using short-form or slangs for changelogs.
 * For example, HP ➜ health, regen ➜ regeneration, etc.
 * Only exception is for Talents: Talent wordings should follow accordingly to how it is displayed in client.


 * Increased mechanics from x to y.
 * Increased base from x to y.
 * Reduced base from x to y.

Miscellaneous

 * This section is for components that are quality of life changes/additions, do not bold any of the tags (eg.,  ,  ,  ,  ).
 * The only exception is for Heroes removed from game  .
 * Use 2nd level definition list for  if needed.

Hero Created/Removed

 * Use  to indicate hero created and available in game. Use Patch history if no patch version available (eg. ).
 * Bold Removed Hero ID. to indicate hero removed from game.


 * Removed .
 * Created.

Added/Updated

 * Simple descriptions of what was added or updated.
 * Innate ability added that are cosmetic changes do not need formatting because they are considered as quality of life changes.

Change/Recoded/Restored/Renamed

 * 1st level bullet list with simple descriptions of what is / /.
 * 2nd level bullet list with more information if needed.
 * 1st level bullet list for  and link.
 * 2nd level bullet list with more information of Recoded ability if needed.


 * Recoded Ability ID.

Restrictions

 * Use  and   for disabled/enabled items on Heroes.
 * Use definition list on the same level for.


 * is restricted from buying.


 * is no longer restricted from buying.
 * Notes: Description and explanation.

Abilities

 * Only use one Hero ID per version.
 * Arrange hero Ability ID according to sequence in client.
 * Summoned units goes below the ability.
 * upgrade comes next after hero abilities, and hero talents last.[?]

Capitalization
 * Capitalize the first letter of  to better clarify abilities that have give bonuses based from other ability levels.
 * No capitalization for the first letter of level needed if the bonuses are based on current level.

Units

 * 1st level bullet list for summoned units Unit ID, summoned units goes below their hero abilities respectively.
 * 1st level bullet list if there are only one type of ability trait or one value change to summoned unit.
 * 2nd level bullet list for the first trait or value change.
 * Same level bullet list for more traits and value changes.
 * 3rd level bullet list for summoned units ability trait or value changes.
 * Same level bullet list for more summoned units ability trait or value changes.


 * Rescaled Ability Trait1 from x to y.
 * Source
 * Reduced Ability Trait3 from x to y.
 * Reduced Ability Trait3 from x to y.

Values Increased/Reduced

 * Use 1st level bullet list if there are only one type of ability trait or one value change in the same ability.
 * If there are more than one type of ability trait or value change, use 1st level bullet list and link Ability ID. Do not use full-stop.
 * 2nd level bullet list for the first trait or value change.
 * 2nd level bullet list for the second trait or value change.
 * Use more 2nd level bullet list for more changes.
 * Add % to all % based values.
 * Use  or   for increased/reduced values.
 * is used when values are increased/reduced from multiple values  to one value.


 * Increased Trait1 from x1/x2/x3/x4 to y on each level.
 * Increased duration from x1/x2/x3/x4 to y1/y2/y3/y4.
 * Increased Trait2 from x to y.
 * Increased Trait2 from x to y.

Moved

 * Use  when the ability slots are changed. No formatting needed.
 * Ability ID should be placed before any ability value changes.


 * Moved to the first/second/third ability.
 * Moved to the fourth ability slot. This is now 's ultimate ability.

Added/Removed Abilities
Added abilities
 * 1st level bullet list, bold  . Replace  with   if needed.
 * 1st level definition list and italicize  .
 * 2nd level definition list for ability traits and values.
 * Add another same level definition list for more ability traits and values.
 * Same level definition list for  if needed.


 * Added the Ability ID ability.
 * Ability ID
 * New ability description here.
 * Ability trait1: value1
 * Ability trait2: value2
 * Notes:

Removed abilities
 * 1st level bullet list, bold  . No other descriptions needed.


 * Removed Ability ID.

Ability Component

 * Bold Added and Removed word for new components added/removed in abilities.
 * 1st level definition list, and italicize  .
 * 1st level definition list for ability descriptions.
 * 2nd level definition list for ability traits and values.
 * Use the same level definition list for more ability traits and values.
 * Use the same level definition list for  if needed.


 * Added an active component to Ability ID.
 * New Ability ID
 * Ability Trait1: Value1
 * Ability Trait2: Value2


 * Removed the active component from Ability ID.

Sub-ability
Added sub-ability
 * 1st level bullet list, bold  .
 * 2nd level bullet list for more details about the sub-ability.
 * 1st level definition list link to Ability ID. Do not use full-stop.
 * 1st level definition list to  , italicize description.
 * 2nd level definition list to add more ability values if necessary.
 * 2nd level definition list for.


 * Added the sub-ability.
 * Ability description if needed.
 * Notes:

Removed sub-ability
 * 1st level bullet list, only bold the   word following by . No other descriptions needed.


 * Removed sub-ability Ability ID.

Innate Ability

 * Bold  
 * 1st level definition list and do not italicize new added abilities or sub-abilities.
 * Same level definition list and italicize 
 * Innate ability that are cosmetic changes do not need formatting because they are considered as quality of life changes.
 * 2nd level definition list for the newly added ability values.
 * Same level definition list for more ability values.
 * Same level definition list for  if needed.
 * If the innate ability is removed, bold  


 * Added the innate ability for .
 * Ability description.
 * Cast range:
 * Duration:
 * Notes::
 * Notes::


 * Removed the innate ability for .

Reworked/Replaced Abilities

 * Reworked and Replaced abilities have similar formatting.
 * Use only official ability traits and values.
 * 1st level definition list and italicizing the  .
 * 2nd level of definition and italicize the  .
 * Use the same level for ability values, only capitalize the first letter of each line.
 * Use the same level for.
 * Add a blank line in between.
 * 1st level definition list and italicizing the  .
 * 2nd level of definition and italicize the  .
 * Use the same level for ability values, only capitalize the first letter of each line.
 * Use the same level for.

Reworked

 * Bold only the Reworked word and link previous Ability ID.
 * Do not use full-stop for Reworked abilities.


 * Reworked
 * Old 
 * Ability description.
 * Ability trait1: Value1
 * Ability trait2: Value2


 * New 
 * Ability description.
 * Ability trait1: Value1
 * Ability trait2: Value2
 * Notes:


 * In some cases, you may use the  /   format similar to a reworked Aghanim's Scepter upgrade for reworked abilities if there isn't too much of a change.


 * Reworked
 * Old: Old values and traits here.
 * New: New values and traits here.


 * In some cases where the reworked ability is very similar from the previous version, you may use 2nd level bullet form (similarly to the formatting of Increased/Reduced Values) to state the reworked traits and values.

Replaced

 * Bold only the Replace word and link previous Ability and link replaced Ability.


 * Replaced with.
 * Old 
 * Ability description.
 * Ability trait1: Value1
 * Ability trait2: Value2


 * New 
 * Ability description.
 * Ability trait1: Value1
 * Ability trait2: Value2
 * Notes:

Restored

 * Use Restored only when ability is replaced with previous patch version.
 * Restored has a similar formatting as Reworked and Replaced.
 * 1st level bullet point and bold only the Restored word and link previous.
 * 1st level definition list and italicizing the Old.
 * 2nd level of definition and italicize the  .
 * Use the same level for ability values, only capitalize the first letter of each line.
 * Use the same level for.


 * Restored the previous.
 * Now 
 * Ability description.
 * Ability trait1: Value1
 * Ability trait2: Value2
 * Notes:

Merged/Split
Merged Abilities
 * Bold Merged word, following with Ability ID and Ability ID into Ability ID.
 * Use definition list on the 1st level and italicize Old Ability
 * Use definition list on the 1st level and italicize ability description.
 * Add 2nd level definition list for ability values.
 * Use the same level for.
 * In rare cases where abilities get Merged, ability details/information can be merged if both abilities have very similar functions (eg. and ).


 * '''Merged and  into.
 * Old 
 * Old ability description
 * Ability trait1: value 1
 * Ability trait2: value 2


 * New 
 * New ability description.
 * Ability trait1: value 1
 * Ability trait2: value 2


 * In some cases the purpose of Merged abilities is to simplify abilities, just include the  . Omit the previous abilities.

Split Abilities
 * Bold Split word, following with Ability ID into Ability ID and Ability ID.
 * 2nd level bullet list describing more details if there are no major changes.
 * 2nd level bullet list for increased/reduced ability traits and values.
 * Format it as a Reworked or Replaced ability if there are major changes to the ability.

Aghanim's Scepter Upgrade

 * Start the line with.
 * Group added upgrades according to ability, then increased/reduced value.
 * Use another level if there are more than one components to the upgrade.
 * Always link Ability ID.

Upgrade Values Increased/Reduced

 * Use simple past tense for increased/reduced upgrade values.
 * In this example below, another level is used because no longer increases duration.


 * upgrade:
 * values increased/reduced from value on each level to multiple values.

Upgrades Added/Removed/Moved

 * 1st level bullet list and bold  . End the sentence with a semi-column.
 * 1st level bullet list and bold  . End the sentence with a full-stop.
 * 2nd level bullet list describing the newly added upgrade.
 * Use another 2nd level bullet list if the upgrade affects more than one the ability traits, or the upgrade affects two different abilities/ability traits.
 * Use the same level for  if needed.
 * If an ability is replaced/reworked and upgrade is removed along with it, use the Undocumented feature if it's not mentioned in the patch notes.


 * Removed upgrade for .
 * No longer.


 * Added upgrade for :
 * 


 * Use another 2nd level bullet list if the upgrade affects more than one the ability traits, or the upgrade affects two different abilities/ability traits.
 * Use the same level for  if needed.


 * upgrade:
 * Ability Trait1 values now affect something to something.
 * Increased {{A|Ability ID}|Hero}} from x to y, reduced cooldown from x to y.

Reworked Upgrades

 * (definition of reworked upgrade here)
 * Bold only the Reworked word and link to Aghanim's Scepter page.
 * Old: Add another level for the Old upgrade.
 * New: Use the same level for the New upgrade.


 * Reworked upgrade:
 * Old:
 * New:

Granted Abilities

 * 1st level bullet list stating if it's Reworked or Added.
 * 1st level definition list for abilities or sub-abilities granted by . Do not italicize the newly granted/reworked/moved abilities.
 * 1st level definition for the ability descriptions and italicize them.
 * 2nd level definition list for some of the important ability values.
 * Use the same level for more ability values if needed.
 * Use the same level for  if needed.


 * upgrade:
 * Grants {H|Hero ID}} the ability and the  sub-ability.
 * Italicize newly granted ability descriptions here.
 * Cast range:
 * Mana cost:
 * Cooldown:
 * Cooldown:


 * Italicize newly granted sub-ability descriptions here.
 * Duration:
 * Mana cost:
 * Notes:
 * Notes:

Talents

 * Talent wordings should follow accordingly to how it is displayed in client.
 * 1st Level bullet list and bold the   or ''' word.
 * 2nd Level definition list for talent traits and talent values.
 * Bold the middle  .
 * Use and add links moderately for talents.
 * Abilities:, etc.
 * Attributies:, ,
 * Mechanics: regen, cooldown reduction etc.
 * Notes: Although Radius should be the correct term for the increased value, however it is displayed as AoE because it is shown as AoE in client. Same goes for talents displaying regen instead of regeneration.

New Talent Tree

 * Do not add full-stops for newly added talents.


 * Added Talents:
 * Level 10: left_talent or right_talent
 * Level 15: left_talent or right_talent
 * Level 20: left_talent or right_talent
 * Level 25: left_talent or right_talent

Values Increased/Reduced

 * Add full-stops for increased/reduced talent values.
 * Use two different 1st level bullet list for increased/reduced talent values for each sides, if there are changes to both sides.


 * Talents:
 * Level xx left talent: increased to.
 * Level xx right talent: reduced to.

Reworked/Replaced

 * Add full-stops for reworked/replaced talent.
 * Use two different 1st level bullet list for reworked/replaced talent traits and values for each sides, if there are changes to both sides.
 * Use ➜ (U+279C) arrow to indicate reworked/replaced talent.


 * Talents:
 * Level xx left/right talent changed: ➜.


 * Start a new bullet list for heavily  .
 * Include   /   talents for reference.
 * Do not add fullstops for reworked talents. Consider heavily reworked talents as new talent trees.


 * Reworked talents:
 * Old:
 * Level 10: left_talent or right_talent
 * Level 15: left_talent or right_talent
 * Level 20: left_talent or right_talent
 * Level 25: left_talent or right_talent
 * New:
 * Level 10: left_talent or right_talent
 * Level 15: left_talent or right_talent
 * Level 20: left_talent or right_talent
 * Level 25: left_talent or right_talent