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 other attributes and 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 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.

Hero Attributes

 * Hero attributes in changelogs will follow the following sequence:
 * Attributes ( / / )
 * Base attributes and attribute gain should be separated.
 * Followed by other mechanics according to Template:MechanicsNav. (discuss with other admins)

Miscellaneous

 * No formatting for the following:
 * Replaced hero model.
 * Added visual effects.
 * Renamed hero.

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 abilities according to sequence in client.
 * Summoned units that belongs to hero goes one level below their hero abilities respectively.
 * Only exception is there are only value changes to summoned unit and not the ability itself.
 * upgrade comes next after hero abilities, and hero talents last.[?]

Moved

 * Moved ability should be placed before any ability value changes.
 * Only use moved when the ability slots are changed.


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

Values Increased/Reduced

 * Use only one level for one change in the same ability.
 * Add another level if there are more than one change to the same ability.
 * Add another level if ability have summons.
 * Add % to all % based values.

Added/Removed Abilities

 * Bold the first level.
 * Use Added the  ability to indicate new added ability.
 * Add another level to describe the ability.
 * Use the same level to add more description or notes if needed.
 * Use Removed Ability_ID to indicate removed ability.
 * No descriptions needed.

Added Sub-ability

 * Bold Added the Ability sub-ability.
 * Use another level to describe the ability if needed.
 * Use same level definition lists to add more ability values if necessary.
 * Add another level definition lists for notes.


 * Added the sub-ability.
 * Description.
 * Notes: Notes here.

Added/Removed Innate Ability

 * Bold the whole sentence for added or removed innate abilities from hero. Include hero minimap icon for this change.
 * Use definition lists and do not italicize new added abilities or sub-abilities.
 * Use the same level for the newly added ability descriptions and italicize them.
 * Add another level and list some of the newly added ability values.
 * (If the ability is removed, use bullet point at this level to describe what was removed.)?
 * Use the same level for more ability values.
 * Use the same level to add notes.


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


 * Removed the innate ability for .

Reworked/Replaced

 * Reworked and Replaced have similar formatting.

Reworked

 * Bold only the Reworked word and link previous Ability.
 * Do not use full-stop for Reworked abilities.
 * 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.
 * 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
 * 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.

Replaced

 * Bold only the Replace word and link previous Ability and link replaced Ability.
 * 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.
 * 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.


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


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

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.

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.

Merged

 * Bold Merged only 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 ).

Scepter Upgrades Added/Removed

 * Use another level if current version adds/removes a component from the upgrade, or the upgrade affects two different abilities.
 * Use the Undocumented feature if an ability is replaced and the Scepter upgrade is removed along with it, or if the upgrade is moved to the new replaced ability.
 * Use simple present tense for newly added upgrades.


 * upgrade:
 * Component A balanced values.
 * Increased {{A|Ability ID}|Hero}} values.


 * Bold the whole sentence for added or removed Scepter upgrades from hero. Include hero minimap icon for this change.
 * If an upgrade is newly added, end the sentence with a semi-column:
 * If the upgrade is removed, end the sentence with a full-stop.
 * Use another level to describe the added/remove upgrade.
 * Use the same level for notes if needed.


 * Removed upgrade for {{H|Hero}.
 * No longer.


 * Added upgrade for :
 * 

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

 * Start the line depending on whether it's reworked or added.
 * Use definition lists and do not italicize abilities or sub-abilities granted by Aghanim's Scepter.
 * Use the same level for the ability descriptions and italicize them.
 * Add another level and list some of the important ability values.
 * Use the same level for more ability values.
 * Use the same level to add notes.


 * upgrade:
 * Grants {H|Hero}} the ability and the {{A|Sub-Ability_Name|Hero} sub-ability.
 * Ability_Name
 * Italicize ability descriptions here.
 * Cast range:
 * Mana cost:
 * Cooldown:


 * Sub-Ability_Name
 * Italicize ability descriptions here.
 * Duration:
 * Mana cost:
 * Notes: Here are some 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