Help:Update history

Blooncyclopedia uses 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:

Platform	Method	Example(s)
Steam	SteamDB	Bloons TD 6 (Windows) Bloons TD 6 (macOS)
Epic Games Store	Epic Games Database	Bloons TD 6 (Windows) Bloons TD 6 (Android) Bloons TD 6 (iOS)

Using Cargo to display changes

These examples use {{BTD6 changes}}, which is for listing changes pertaining to 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).

Game	Store template	Query template	Database
Bloons TD 6	{{BTD6 changes}}	{{BTD6 change list by name}}	btd6_changes
Bloons TD Battles 2	{{BTDB2 changes}}	{{BTDB2 change list by name}}	btdb2_changes
Bloons Card Storm	{{BCS changes}}	{{BCS change list by name}}	bcs_changes

Storing changes

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:

{{BTD6 changes
| version = 48.0
| names   = Polyphemus
| 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.
| changes = *{{buff|The Bloons now will do one lap over the eye}}
}}

On the update history page, it will output this:

“

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

”

•  The Bloons now will do one lap over the eye

Yes, you could accomplish the same thing without using this template by using {{quote}}, but the reason you use this template is so you can use Cargo queries.

Querying changes

By using the {{BTD6 changes}} template, you can now use a Cargo query to display that same content on the page for Polyphemus. This is done by simply using the {{BTD6 change list by name}} template with the name "Polyphemus".

{{BTD6 change list by name|Polyphemus}}

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

Version 48.0

“

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

”

•  The Bloons now will do one lap over the eye

Other options

You can specify multiple names in a single {{BTD6 changes}} by separating the names with a semicolon. This is useful if you want to display a list of changes on multiple pages.

{{BTD6 changes
| version = 43.0
| names   = Dreadbloon;Dreadrock Bloon
| quote   = Rock Bloons in the higher tiers of Normal Dreadbloon are very outscaled, and so their health values are being increased.
| changes =
*{{nerf|Dreadrock Bloon health increased|5,000|9,000|name=Normal tier 4}}
*{{nerf|Dreadrock Bloon health increased|12,000|22,500|name=Normal tier 5}}
}}

This list of changes will now appear when using either {{BTD6 change list by name|Dreadbloon}} or {{BTD6 change list by name|Dreadrock Bloon}}, which is good in this case because this change affects both Dreadbloon and Dreadrock Bloons.

You can also use the version note parameter to mark if a change is upcoming.

{{BTD6 changes
| version = 48.0
| version note = upcoming
| names   = Polyphemus
| 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.
| changes = *{{buff|The Bloons now will do one lap over the eye}}
}}

On the Polyphemus page, it will display this:

Version 48.0 (upcoming)

“

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

”

•  The Bloons now will do one lap over the eye

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 changes store parameter. The text in changes is displayed on the update page, while changes store is displayed in queries.

{{BTD6 changes
| name    = Biggest Beacon
| version = 48.2
| 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
}}

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

•  Biggest Beacon: Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village (bug fix)

On the Biggest Beacon page, it will display this:

Version 48.2

•  Regrow Blocker of X-1-X Villages will now be applied to the entire range of the Village (bug fix)

This is useful if you want to give additional context on the update page that isn't necessary on pages that query the list of changes. In this example, the update page specifies that this is for the "Biggest Beacon Artifact", but that context isn't necessary on the Biggest Beacon page.

Formatting

This wiki uses these templates to notate changes on each bullet point. They all have the same syntax; the only difference is the icon they display.

Template	Icon	Purpose
{{buff}}		Changes that affect gameplay that favor the player
{{nerf}}		Changes that affect gameplay that disfavor the player
{{neutral}}		Changes that affect gameplay that do not exclusively favor or disfavor the player (i.e. it has pros and cons)
{{change}}		Changes that do not affect gameplay, like visual and text changes

The basic usage of these templates is to use the first parameter to list information about the change.

Wikitext	Result
*{{nerf|Geraldo's Moustache will no longer contain hidden Glue Rats}}	Geraldo's Moustache will no longer contain hidden Glue Rats

The second and third parameters specify the difference before and after the change, if it makes sense to express the change in that way.

Wikitext	Result
*{{nerf|Max level goggle tightness loosened|Max|Sam}}	Max level goggle tightness loosened ― Max → Sam

Additional named parameters are for adding additional information or context to a change. You can use any combination of these parameters.

Parameter	Purpose	Wikitext	Result
bug	Change is the result of a bug	*{{nerf|name=MOAB Hex|Can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}	MOAB Hex: Can only be used if at least one non-MOAB-Class Bloon is on-screen (bug)
fix	Change is the result of a bug fix	*{{nerf|name=Mini Sun Avatar|Can no longer attack through walls|fix=y}}	Mini Sun Avatar: Can no longer attack through walls (bug fix)
undoc	Change was not documented in official resources (e.g. patch notes)	*{{neutral|name=Enhanced Laser|Now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}	Enhanced Laser: Now counts shots from attacking during Flight Boost when grenades are selected (undocumented)
note	Inserts additional notes or context about the change on a second, indented line	*{{neutral|Damage type changed|Sharp|Shatter|note=This means it can no longer be buffed by the [[Sharpening Stone]]}}	Damage type changed ― Sharp → Shatter Note: This means it can no longer be buffed by the Sharpening Stone

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

Wikitext	Result
*{{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}}	Main Gun: Now deals +3 damage to Lead Note: Still requires a Black-popping buff to apply to DDTs  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 {{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).

Game	Store template	Database
Bloons TD 6	{{BTD6 tower changes}}	btd6_changes
Bloons TD Battles (mobile)	{{BTDBM tower changes}}	btdbm_changes
Bloons TD Battles 2	{{BTDB2 tower 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.)

| 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}}

Tiers	Changes
X-2-X Wall of Fire and further upgrades	Wall of Fire: Now saves the time remaining on its attack cooldown  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.)

| 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}}

Tiers	Changes
0-1-1 Fireball + Intense Magic and further upgrades	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'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.

| 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}}

Tiers	Changes
X-X-2 Caltrops and all crosspaths X-X-3 Flash Bomb and further upgrades	Caltrop: Lifespan reduced ― 70s → 25s

Manually adding changes

Behind the scenes, these templates use the same system as {{BTD6 changes}}, but with special code to automate the formatting and storing. It is possible to use {{BTD6 changes}} 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 Biker Bones, Monkey Ace (for Update history:Monkey Ace (Battles 2)), Monkey Ace 2 3 (for Bomber Ace (Battles 2)#Update history), Monkey Ace 2 4 (for Ground Zero (Battles 2)#Update history), and Monkey Ace 2 5 (for Tsar Bomba (Battles 2)#Update history).

{{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}}
}}