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 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.
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 Bloons TD 6 v48.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:
“ 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”
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|Normal Tier 4: Dreadrock Bloon health increased|5,000|9,000}}
*{{nerf|Normal Tier 5: Dreadrock Bloon health increased|12,000|22,500}}
}}
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”
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 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|Biggest Beacon Artifact: 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 Bloons TD 6 v48.2 page, it will display this:
On the Biggest Beacon page, it will display this:
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}}
|
|
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}}
|
|
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|MOAB Hex: can only be used if at least one non-MOAB-Class Bloon is on-screen|bug=y}}
|
|
fix
|
Change is the result of a bug fix | *{{nerf|Mini Sun Avatar: can no longer attack through walls|fix=y}}
|
|
undoc
|
Change was not documented in official resources (e.g. patch notes) | *{{neutral|Enhanced Laser: now counts shots from attacking during Flight Boost when grenades are selected|undoc=y}}
|
|
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]]}}
|
|
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).
| Wikitext | Result |
|---|---|
*{{buff|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}}
|
|
Navigation
| Blooncyclopedia | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|