Help:Update history

(10 intermediate revisions by 3 users not shown)

Line 1:

Blooncyclopedia uses [[Help:Cargo|Cargo]] to manage its update history system. This allows editors to document changes on a page for a game update, such as [[Bloons TD 6 ~~v48~~.0]], and then use a "query" to list those same changes on other pages that those changes are relevant to, without having to manually copy that documentation onto every page. This also means that if any additions or corrections need to be made, one can simply update the documentation on the update page, and any other pages that query that documentation will automatically update.

Blooncyclopedia uses [[Help:Cargo|Cargo]] to manage its update history system. This allows editors to document changes on a page for a game update, such as [[Update history:Bloons TD 6/Version 48.0]], and then use a "query" to list those same changes on other pages that those changes are relevant to, without having to manually copy that documentation onto every page. This also means that if any additions or corrections need to be made, one can simply update the documentation on the update page, and any other pages that query that documentation will automatically update.

==Release dates==

Update infoboxes should use timestamps instead of dates, if possible, to avoid ambiguity when it comes to time zones. Use the following methods to find update timestamps:

{|class="wikitable"

!Platform

!Method

!Example(s)

|-

|Steam

|SteamDB

|[https://steamdb.info/depot/960091/history/ ''Bloons TD 6'' (Windows)]<br>[https://steamdb.info/depot/960093/history/ ''Bloons TD 6'' (macOS)]

|-

|Epic Games Store

|Epic Games Database

|[https://egdata.app/items/49c4bf5c6fd24259b87d0bcc96b6009f/changelog ''Bloons TD 6'' (Windows)]<br>[https://egdata.app/items/88ee3d1fd8e1491f83de3a577a103d65/changelog ''Bloons TD 6'' (Android)]<br>[https://egdata.app/items/26a2a672768640749e68e7af238a9fb8/changelog ''Bloons TD 6'' (iOS)]

|}

==Using Cargo to display changes==

Line 26:

Line 42:

===Storing changes===

For example, on the [[Bloons TD 6 ~~v48~~.0]] page, if you want to list the change made to [[Polyphemus]] in that update, you would use this syntax:

For example, on the [[Update history:Bloons TD 6/Version 48.0]] page, if you want to list the change made to [[Polyphemus]] in that update, you would use this syntax:

<pre>{{BTD6 changes

| version = 48.0

Line 46:

Line 62:

When you preview the page for Polyphemus, this template will display all changes that have been assigned the name <code>Polyphemus</code> in <code>BTD6 changes</code> templates. By using <code>BTD6 changes</code> with the name <code>Polyphemus</code> and version <code>48.0</code>, you've automatically added this to the list of changes it displays:

<blockquote><big>'''[[Bloons TD 6 ~~v48~~.0|Version 48.0]]'''</big>

<blockquote><big>'''[[Update history:Bloons TD 6/Version 48.0|Version 48.0]]'''</big>

{{quote|Polyphemus annoyed me in Rogue one time too many; so now Bloons will loop once around The Eye before exiting the track. This is purely to give them more time to think about what they have done and does not mean they are forgiven.|Update notes}}

*{{buff|The Bloons now will do one lap over the eye}}</blockquote>

Line 57:

Line 73:

| quote = Rock Bloons in the higher tiers of Normal Dreadbloon are very outscaled, and so their health values are being increased.

| changes =

*{{nerf|~~Normal Tier 4:~~ Dreadrock Bloon health increased|5,000|9,000}}

*{{nerf|Dreadrock Bloon health increased|5,000|9,000|name=Normal tier 4}}

*{{nerf|~~Normal Tier 5:~~ Dreadrock Bloon health increased|12,000|22,500}}

*{{nerf|Dreadrock Bloon health increased|12,000|22,500|name=Normal tier 5}}

}}</pre>

This list of changes will now appear when using either <code><nowiki>{{BTD6 change list by name|Dreadbloon}}</nowiki></code> or <code><nowiki>{{BTD6 change list by name|Dreadrock Bloon}}</nowiki></code>, which is good in this case because this change affects both [[Dreadbloon (BTD6)|Dreadbloon]] and [[Dreadrock Bloon]]s.

Line 72:

Line 88:

On the Polyphemus page, it will display this:

<blockquote><big>'''[[Bloons TD 6 ~~v48~~.0|Version 48.0]] (upcoming)'''</big>

<blockquote><big>'''[[Update history:Bloons TD 6/Version 48.0|Version 48.0]] (upcoming)'''</big>

{{quote|Polyphemus annoyed me in Rogue one time too many; so now Bloons will loop once around The Eye before exiting the track. This is purely to give them more time to think about what they have done and does not mean they are forgiven.|Update notes}}

*{{buff|The Bloons now will do one lap over the eye}}</blockquote>

If you want to display different text on the update's page (say, [[Bloons TD 6 ~~v48~~.2]]) than on pages that query it, you can use the <code>changes store</code> parameter. The text in <code>changes</code> is displayed on the update page, while <code>changes store</code> is displayed in queries.

If you want to display different text on the update's page (say, [[Update history:Bloons TD 6/Version 48.2]]) than on pages that query it, you can use the <code>changes store</code> parameter. The text in <code>changes</code> is displayed on the update page, while <code>changes store</code> is displayed in queries.

<pre>{{BTD6 changes

| name = Biggest Beacon

| version = 48.2

| changes = *{{buff|Biggest Beacon ~~Artifact:~~ Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}

| changes = *{{buff|name=Biggest Beacon|Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}

| changes store = *{{buff|Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}

| names = Biggest Beacon

}}</pre>

On the [[Bloons TD 6 ~~v48~~.2]] page, it will display this:

On the [[Update history:Bloons TD 6/Version 48.2]] page, it will display this:

*{{buff|Biggest Beacon ~~Artifact~~: Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}</blockquote>

*{{buff|'''Biggest Beacon''': Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}</blockquote>

On the [[Biggest Beacon]] page, it will display this:

<blockquote><big>'''[[Bloons TD 6 ~~v48~~.2|Version 48.2]]'''</big>

<blockquote><big>'''[[Update history:Bloons TD 6/Version 48.2|Version 48.2]]'''</big>

*{{buff|Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}</blockquote>

Line 112:

Line 128:

|{{temp|neutral}}

|{{neutral}}

|Changes that affect gameplay that do not ~~universally~~ favor or disfavor the player (i.e. it has pros and cons)

|Changes that affect gameplay that do not exclusively favor or disfavor the player (i.e. it has pros and cons)

|-

|{{temp|change}}

Line 148:

Line 164:

|<code>bug</code>

|Change is the result of a bug

|<pre>*{{nerf|MOAB Hex~~: can~~ only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}</pre>

|<pre>*{{nerf|name=MOAB Hex|Can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}</pre>

|

*{{nerf|MOAB Hex~~: can~~ only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}

*{{nerf|name=MOAB Hex|Can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}

|-

|<code>fix</code>

|Change is the result of a bug fix

|<pre>*{{nerf|Mini Sun Avatar~~: can~~ no longer attack through walls|fix=y}}</pre>

|<pre>*{{nerf|name=Mini Sun Avatar|Can no longer attack through walls|fix=y}}</pre>

|

*{{nerf|Mini Sun Avatar~~: can~~ no longer attack through walls|fix=y}}

*{{nerf|name=Mini Sun Avatar|Can no longer attack through walls|fix=y}}

|-

|<code>undoc</code>

|Change was not documented in official resources (e.g. patch notes)

|<pre>*{{neutral|Enhanced Laser~~: now~~ counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}</pre>

|<pre>*{{neutral|name=Enhanced Laser|Now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}</pre>

|

*{{neutral|Enhanced Laser~~: now~~ counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}

*{{neutral|name=Enhanced Laser|Now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}

|-

|<code>note</code>

Line 171:

Line 187:

|}

If the subject has multiple attacks or mechanics, it's a good idea to use ~~colons~~ to ~~notate~~ which changes apply to which mechanic(s).

If the subject has multiple attacks or mechanics, it's a good idea to use the <code>name</code> parameter to label which changes apply to which mechanic(s).

{|class="wikitable"

!Wikitext

!Result

|-

|<pre>*{{buff|Main Gun~~: now~~ deals +3 damage to Lead|note=Still requires a Black-popping buff to apply to DDTs}}

|<pre>*{{buff|name=Main Gun|Now deals +3 damage to Lead|note=Still requires a Black-popping buff to apply to DDTs}}

*{{buff|Machine Gun~~: now~~ deals +2 damage to Lead|note=Still requires a Lead-popping buff to damage Leads and DDTs}}</pre>

*{{buff|name=Machine Gun|Now deals +2 damage to Lead|note=Still requires a Lead-popping buff to damage Leads and DDTs}}</pre>

|

*{{buff|name=Main Gun|Now deals +3 damage to Lead|note=Still requires a Black-popping buff to apply to DDTs}}

*{{buff|name=Machine Gun|Now deals +2 damage to Lead|note=Still requires a Lead-popping buff to damage Leads and DDTs}}

|}

==Tower changes==

This wiki uses special templates for formatting changes to towers, due to their upgrade system. These examples use {{temp|BTD6 tower changes}}, which is for listing changes to towers in ''[[Bloons TD 6]]''. There are equivalent templates for other games, which use the exact same syntax. The only difference is that each game has a separate Cargo database (so changes in one game don't display in queries for another).

{|class="wikitable"

!Game

!Store template

!Database

|-

!''[[Bloons TD 6]]''

|{{temp|BTD6 tower changes}}

|[[Special:CargoTables/btd6_changes|btd6_changes]]

|-

!''[[Bloons TD Battles (multiplatform)|Bloons TD Battles]]'' (mobile)

|{{temp|BTDBM tower changes}}

|[[Special:CargoTables/btdbm_changes|btdbm_changes]]

|-

!''[[Bloons TD Battles 2]]''

|{{temp|BTDB2 tower changes}}

|[[Special:CargoTables/btdb2_changes|btdb2_changes]]

|}

===Tier notations===

If a change affects ''all'' subsequent upgrade tiers, add a "+" after the tier notation to indicate this. (Please only use this if a change applies to 3 or more upgrades on the same path.)

<pre>| changes 1 tiers = X2X+

| changes 1 =

*{{nerf|name=Wall of Fire|Now saves the time remaining on its attack cooldown}}

*{{nerf|name=Wall of Fire|Now disappears instantly when the tower is sold}}</pre>

{|class="wikitable"

!Tiers

!Changes

|-

|X-2-X [[Wall of Fire (BTD6)|Wall of Fire]] and further upgrades

|

*{{~~buff~~|~~Main Gun: now deals +3 damage to Lead~~|~~note=Still requires a Black-popping buff to apply to DDTs~~}}

*{{nerf|name=Wall of Fire|Now saves the time remaining on its attack cooldown}}

*{{~~buff~~|~~Machine Gun: now deals +2 damage to Lead~~|~~note=Still requires a Lead-popping buff to damage Leads and DDTs~~}}

*{{nerf|name=Wall of Fire|Now disappears instantly when the tower is sold}}

|}

If a crosspath-specific change carries over into higher tiers, use this to indicate that all further tiers of both upgrade paths benefit from it. (Please only use this if a change is specifically to a crosspathing interaction, not any change to a tier 1 or tier 2 upgrade that affects crosspaths normally.)

<pre>| changes 1 tiers = 011+

| changes 1 =

*{{buff|Fireball: pierce increased|15|20}}</pre>

{|class="wikitable"

!Tiers

!Changes

|-

|0-1-1 [[Fireball (BTD6)|Fireball]] + [[Intense Magic (BTD6)|Intense Magic]] and further upgrades

|

*{{buff|name=Fireball|Pierce increased|15|20}}

|}

If a change made to a tier 1 or tier 2 upgrade affects all its crosspaths, but not in a way unique to a crosspath, then add a "c" after the tier notation to indicate this. In this example, a change to [[Caltrops (BTD6)|Caltrops]]'s caltrop lifespan technically affects path 1 and path 2 upgrades, but only because they have the same caltrop attack with this crosspath, not because of a special crosspath interaction.

<pre>| changes 1 tiers = xx2c;xx3+

| changes 1 =

*{{nerf|name=Caltrop|Lifespan reduced|70s|25s}}</pre>

{|class="wikitable"

!Tiers

!Changes

|-

|X-X-2 [[Caltrops (BTD6)|Caltrops]] and all crosspaths<br>X-X-3 [[Flash Bomb (BTD6)|Flash Bomb]] and further upgrades

|

*{{nerf|name=Caltrop|Lifespan reduced|70s|25s}}

|}

===Manually adding changes===

Behind the scenes, these templates use the same system as {{temp|BTD6 changes}}, but with special code to automate the formatting and storing. It is possible to use <code><nowiki>{{BTD6 changes}}</nowiki></code> to manually store changes for towers and upgrades. This is done by using these names:

*Changes that apply to the base tower only use the name "[tower name] 00" (ex. "Dart Monkey 00" for the update history section on [[Dart Monkey (BTD6)]])

*Changes that apply to all tiers, including the base tower, use the name "[tower name] *" (ex. "Dart Monkey *")

*Changes that apply to an upgrade use the scheme "[tower name] [path number] [tier number]" (ex. "Dart Monkey 2 4" for the update history section of [[Super Monkey Fan Club (BTD6)]])

*Changes that display on a towers' update history page simply use the name of the tower (ex. "Dart Monkey" for [[Update history:Dart Monkey (BTD6)]])

If you need to manually store a change to a base tower and/or an upgrade, you should also store it to the update history page. For example, this change (from [[Update history:Bloons TD Battles 2/Version 4.7]]) needs to be stored for Biker Bones, Bomber Ace (path 2 tier 3), Ground Zero (path 2 tier 4), and Tsar Bomba (path 2 tier 5), so it uses the names <code>Biker Bones</code>, <code>Monkey Ace</code> (for [[Update history:Monkey Ace (Battles 2)]]), <code>Monkey Ace 2 3</code> (for [[Bomber Ace (Battles 2)#Update history]]), <code>Monkey Ace 2 4</code> (for [[Ground Zero (Battles 2)#Update history]]), and <code>Monkey Ace 2 5</code> (for [[Tsar Bomba (Battles 2)#Update history]]).

<pre>{{BTDB2 changes

|version = 4.7

|version note = OTA update 1

|names = Biker Bones;Monkey Ace;Monkey Ace 2 3;Monkey Ace 2 4;Monkey Ace 2 5

|changes = *{{nerf|Biker Bones no longer causes Bomber Ace to drop too many bombs|fix=y}}

}}</pre>

==Navigation==

[[Category:Wiki help]]

@@ Line 1: / Line 1: @@
-Blooncyclopedia uses [[Help:Cargo|Cargo]] to manage its update history system. This allows editors to document changes on a page for a game update, such as [[Bloons TD 6 v48.0]], and then use a "query" to list those same changes on other pages that those changes are relevant to, without having to manually copy that documentation onto every page. This also means that if any additions or corrections need to be made, one can simply update the documentation on the update page, and any other pages that query that documentation will automatically update.
+Blooncyclopedia uses [[Help:Cargo|Cargo]] to manage its update history system. This allows editors to document changes on a page for a game update, such as [[Update history:Bloons TD 6/Version 48.0]], and then use a "query" to list those same changes on other pages that those changes are relevant to, without having to manually copy that documentation onto every page. This also means that if any additions or corrections need to be made, one can simply update the documentation on the update page, and any other pages that query that documentation will automatically update.
+==Release dates==
+Update infoboxes should use timestamps instead of dates, if possible, to avoid ambiguity when it comes to time zones. Use the following methods to find update timestamps:
+{|class="wikitable"
+!Platform
+!Method
+!Example(s)
+|-
+|Steam
+|SteamDB
+|[https://steamdb.info/depot/960091/history/ ''Bloons TD 6'' (Windows)]<br>[https://steamdb.info/depot/960093/history/ ''Bloons TD 6'' (macOS)]
+|-
+|Epic Games Store
+|Epic Games Database
+|[https://egdata.app/items/49c4bf5c6fd24259b87d0bcc96b6009f/changelog ''Bloons TD 6'' (Windows)]<br>[https://egdata.app/items/88ee3d1fd8e1491f83de3a577a103d65/changelog ''Bloons TD 6'' (Android)]<br>[https://egdata.app/items/26a2a672768640749e68e7af238a9fb8/changelog ''Bloons TD 6'' (iOS)]
+|}
 ==Using Cargo to display changes==
@@ Line 26: / Line 42: @@
 ===Storing changes===
-For example, on the [[Bloons TD 6 v48.0]] page, if you want to list the change made to [[Polyphemus]] in that update, you would use this syntax:
+For example, on the [[Update history:Bloons TD 6/Version 48.0]] page, if you want to list the change made to [[Polyphemus]] in that update, you would use this syntax:
 <pre>{{BTD6 changes
 | version = 48.0
@@ Line 46: / Line 62: @@
 When you preview the page for Polyphemus, this template will display all changes that have been assigned the name <code>Polyphemus</code> in <code>BTD6 changes</code> templates. By using <code>BTD6 changes</code> with the name <code>Polyphemus</code> and version <code>48.0</code>, you've automatically added this to the list of changes it displays:
-<blockquote><big>'''[[Bloons TD 6 v48.0|Version 48.0]]'''</big>
+<blockquote><big>'''[[Update history:Bloons TD 6/Version 48.0|Version 48.0]]'''</big>
 {{quote|Polyphemus annoyed me in Rogue one time too many; so now Bloons will loop once around The Eye before exiting the track. This is purely to give them more time to think about what they have done and does not mean they are forgiven.|Update notes}}
 *{{buff|The Bloons now will do one lap over the eye}}</blockquote>
@@ Line 57: / Line 73: @@
 | quote   = Rock Bloons in the higher tiers of Normal Dreadbloon are very outscaled, and so their health values are being increased.
 | changes =
-*{{nerf|Normal Tier 4: Dreadrock Bloon health increased|5,000|9,000}}
+*{{nerf|Dreadrock Bloon health increased|5,000|9,000|name=Normal tier 4}}
-*{{nerf|Normal Tier 5: Dreadrock Bloon health increased|12,000|22,500}}
+*{{nerf|Dreadrock Bloon health increased|12,000|22,500|name=Normal tier 5}}
 }}</pre>
 This list of changes will now appear when using either <code><nowiki>{{BTD6 change list by name|Dreadbloon}}</nowiki></code> or <code><nowiki>{{BTD6 change list by name|Dreadrock Bloon}}</nowiki></code>, which is good in this case because this change affects both [[Dreadbloon (BTD6)|Dreadbloon]] and [[Dreadrock Bloon]]s.
@@ Line 72: / Line 88: @@
 On the Polyphemus page, it will display this:
-<blockquote><big>'''[[Bloons TD 6 v48.0|Version 48.0]] (upcoming)'''</big>
+<blockquote><big>'''[[Update history:Bloons TD 6/Version 48.0|Version 48.0]] (upcoming)'''</big>
 {{quote|Polyphemus annoyed me in Rogue one time too many; so now Bloons will loop once around The Eye before exiting the track. This is purely to give them more time to think about what they have done and does not mean they are forgiven.|Update notes}}
 *{{buff|The Bloons now will do one lap over the eye}}</blockquote>
-If you want to display different text on the update's page (say, [[Bloons TD 6 v48.2]]) than on pages that query it, you can use the <code>changes store</code> parameter. The text in <code>changes</code> is displayed on the update page, while <code>changes store</code> is displayed in queries.
+If you want to display different text on the update's page (say, [[Update history:Bloons TD 6/Version 48.2]]) than on pages that query it, you can use the <code>changes store</code> parameter. The text in <code>changes</code> is displayed on the update page, while <code>changes store</code> is displayed in queries.
 <pre>{{BTD6 changes
 | name    = Biggest Beacon
 | version = 48.2
-| changes = *{{buff|Biggest Beacon Artifact: Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}
+| changes = *{{buff|name=Biggest Beacon|Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}
 | changes store = *{{buff|Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}
 | names = Biggest Beacon
 }}</pre>
-On the [[Bloons TD 6 v48.2]] page, it will display this:
+On the [[Update history:Bloons TD 6/Version 48.2]] page, it will display this:
 <blockquote>
-*{{buff|Biggest Beacon Artifact: Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}</blockquote>
+*{{buff|'''Biggest Beacon''': Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}</blockquote>
 On the [[Biggest Beacon]] page, it will display this:
-<blockquote><big>'''[[Bloons TD 6 v48.2|Version 48.2]]'''</big>
+<blockquote><big>'''[[Update history:Bloons TD 6/Version 48.2|Version 48.2]]'''</big>
 *{{buff|Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village|fix=y}}</blockquote>
@@ Line 112: / Line 128: @@
 |{{temp|neutral}}
 |{{neutral}}
-|Changes that affect gameplay that do not universally favor or disfavor the player (i.e. it has pros and cons)
+|Changes that affect gameplay that do not exclusively favor or disfavor the player (i.e. it has pros and cons)
 |-
 |{{temp|change}}
@@ Line 148: / Line 164: @@
 |<code>bug</code>
 |Change is the result of a bug
-|<pre>*{{nerf|MOAB Hex: can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}</pre>
+|<pre>*{{nerf|name=MOAB Hex|Can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}</pre>
 |
-*{{nerf|MOAB Hex: can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}
+*{{nerf|name=MOAB Hex|Can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}
 |-
 |<code>fix</code>
 |Change is the result of a bug fix
-|<pre>*{{nerf|Mini Sun Avatar: can no longer attack through walls|fix=y}}</pre>
+|<pre>*{{nerf|name=Mini Sun Avatar|Can no longer attack through walls|fix=y}}</pre>
 |
-*{{nerf|Mini Sun Avatar: can no longer attack through walls|fix=y}}
+*{{nerf|name=Mini Sun Avatar|Can no longer attack through walls|fix=y}}
 |-
 |<code>undoc</code>
 |Change was not documented in official resources (e.g. patch notes)
-|<pre>*{{neutral|Enhanced Laser: now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}</pre>
+|<pre>*{{neutral|name=Enhanced Laser|Now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}</pre>
 |
-*{{neutral|Enhanced Laser: now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}
+*{{neutral|name=Enhanced Laser|Now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}
 |-
 |<code>note</code>
@@ Line 171: / Line 187: @@
 |}
-If the subject has multiple attacks or mechanics, it's a good idea to use colons to notate which changes apply to which mechanic(s).
+If the subject has multiple attacks or mechanics, it's a good idea to use the <code>name</code> parameter to label which changes apply to which mechanic(s).
 {|class="wikitable"
 !Wikitext
 !Result
 |-
-|<pre>*{{buff|Main Gun: now deals +3 damage to Lead|note=Still requires a Black-popping buff to apply to DDTs}}
+|<pre>*{{buff|name=Main Gun|Now deals +3 damage to Lead|note=Still requires a Black-popping buff to apply to DDTs}}
-*{{buff|Machine Gun: now deals +2 damage to Lead|note=Still requires a Lead-popping buff to damage Leads and DDTs}}</pre>
+*{{buff|name=Machine Gun|Now deals +2 damage to Lead|note=Still requires a Lead-popping buff to damage Leads and DDTs}}</pre>
+|
+*{{buff|name=Main Gun|Now deals +3 damage to Lead|note=Still requires a Black-popping buff to apply to DDTs}}
+*{{buff|name=Machine Gun|Now deals +2 damage to Lead|note=Still requires a Lead-popping buff to damage Leads and DDTs}}
+|}
+==Tower changes==
+This wiki uses special templates for formatting changes to towers, due to their upgrade system. These examples use {{temp|BTD6 tower changes}}, which is for listing changes to towers in ''[[Bloons TD 6]]''. There are equivalent templates for other games, which use the exact same syntax. The only difference is that each game has a separate Cargo database (so changes in one game don't display in queries for another).
+{|class="wikitable"
+!Game
+!Store template
+!Database
+|-
+!''[[Bloons TD 6]]''
+|{{temp|BTD6 tower changes}}
+|[[Special:CargoTables/btd6_changes|btd6_changes]]
+|-
+!''[[Bloons TD Battles (multiplatform)|Bloons TD Battles]]'' (mobile)
+|{{temp|BTDBM tower changes}}
+|[[Special:CargoTables/btdbm_changes|btdbm_changes]]
+|-
+!''[[Bloons TD Battles 2]]''
+|{{temp|BTDB2 tower changes}}
+|[[Special:CargoTables/btdb2_changes|btdb2_changes]]
+|}
+===Tier notations===
+If a change affects ''all'' subsequent upgrade tiers, add a "+" after the tier notation to indicate this. (Please only use this if a change applies to 3 or more upgrades on the same path.)
+<pre>| changes 1 tiers = X2X+
+| changes 1 =
+*{{nerf|name=Wall of Fire|Now saves the time remaining on its attack cooldown}}
+*{{nerf|name=Wall of Fire|Now disappears instantly when the tower is sold}}</pre>
+{|class="wikitable"
+!Tiers
+!Changes
+|-
+|X-2-X [[Wall of Fire (BTD6)|Wall of Fire]] and further upgrades
 |
-*{{buff|Main Gun: now deals +3 damage to Lead|note=Still requires a Black-popping buff to apply to DDTs}}
+*{{nerf|name=Wall of Fire|Now saves the time remaining on its attack cooldown}}
-*{{buff|Machine Gun: now deals +2 damage to Lead|note=Still requires a Lead-popping buff to damage Leads and DDTs}}
+*{{nerf|name=Wall of Fire|Now disappears instantly when the tower is sold}}
 |}
+If a crosspath-specific change carries over into higher tiers, use this to indicate that all further tiers of both upgrade paths benefit from it. (Please only use this if a change is specifically to a crosspathing interaction, not any change to a tier 1 or tier 2 upgrade that affects crosspaths normally.)
+<pre>| changes 1 tiers = 011+ <!-- equivalent to 011;021;031;041;051;012;022;032;042;052;012;013;014;015;023;024;025 -->
+| changes 1 =
+*{{buff|Fireball: pierce increased|15|20}}</pre>
+{|class="wikitable"
+!Tiers
+!Changes
+|-
+|0-1-1 [[Fireball (BTD6)|Fireball]] + [[Intense Magic (BTD6)|Intense Magic]] and further upgrades
+|
+*{{buff|name=Fireball|Pierce increased|15|20}}
+|}
+If a change made to a tier 1 or tier 2 upgrade affects all its crosspaths, but not in a way unique to a crosspath, then add a "c" after the tier notation to indicate this. In this example, a change to [[Caltrops (BTD6)|Caltrops]]'s caltrop lifespan technically affects path 1 and path 2 upgrades, but only because they have the same caltrop attack with this crosspath, not because of a special crosspath interaction.
+<pre>| changes 1 tiers = xx2c;xx3+ <!-- equivalent to 102;202;302;402;502;012;022;032;042;052;xx3;xx4;xx5 -->
+| changes 1 =
+*{{nerf|name=Caltrop|Lifespan reduced|70s|25s}}</pre>
+{|class="wikitable"
+!Tiers
+!Changes
+|-
+|X-X-2 [[Caltrops (BTD6)|Caltrops]] and all crosspaths<br>X-X-3 [[Flash Bomb (BTD6)|Flash Bomb]] and further upgrades
+|
+*{{nerf|name=Caltrop|Lifespan reduced|70s|25s}}
+|}
+===Manually adding changes===
+Behind the scenes, these templates use the same system as {{temp|BTD6 changes}}, but with special code to automate the formatting and storing. It is possible to use <code><nowiki>{{BTD6 changes}}</nowiki></code> to manually store changes for towers and upgrades. This is done by using these names:
+*Changes that apply to the base tower only use the name "[tower name] 00" (ex. "Dart Monkey 00" for the update history section on [[Dart Monkey (BTD6)]])
+*Changes that apply to all tiers, including the base tower, use the name "[tower name] *" (ex. "Dart Monkey *")
+*Changes that apply to an upgrade use the scheme "[tower name] [path number] [tier number]" (ex. "Dart Monkey 2 4" for the update history section of [[Super Monkey Fan Club (BTD6)]])
+*Changes that display on a towers' update history page simply use the name of the tower (ex. "Dart Monkey" for [[Update history:Dart Monkey (BTD6)]])
+If you need to manually store a change to a base tower and/or an upgrade, you should also store it to the update history page. For example, this change (from [[Update history:Bloons TD Battles 2/Version 4.7]]) needs to be stored for Biker Bones, Bomber Ace (path 2 tier 3), Ground Zero (path 2 tier 4), and Tsar Bomba (path 2 tier 5), so it uses the names <code>Biker Bones</code>, <code>Monkey Ace</code> (for [[Update history:Monkey Ace (Battles 2)]]), <code>Monkey Ace 2 3</code> (for [[Bomber Ace (Battles 2)#Update history]]), <code>Monkey Ace 2 4</code> (for [[Ground Zero (Battles 2)#Update history]]), and <code>Monkey Ace 2 5</code> (for [[Tsar Bomba (Battles 2)#Update history]]).
+<pre>{{BTDB2 changes
+|version      = 4.7
+|version note = OTA update 1
+|names        = Biker Bones;Monkey Ace;Monkey Ace 2 3;Monkey Ace 2 4;Monkey Ace 2 5
+|changes      = *{{nerf|Biker Bones no longer causes Bomber Ace to drop too many bombs|fix=y}}
+}}</pre>
 ==Navigation==
 {{blooncyclopedia nav}}
 [[Category:Wiki help]]

Help:Update history: Difference between revisions