Template:BTD6 changes/doc: Difference between revisions

From Blooncyclopedia, the independent Bloons knowledge base
Jump to navigation Jump to search
m clarifications
Pymonkibot (talk | contribs)
 
(One intermediate revision by one other user not shown)
Line 15: Line 15:
"required": true
"required": true
},
},
"changes": {
"hide quote": {
"label": "Changes",
"label": "Hide quote?",
"description": "A list of changes. This text is copied and transcluded verbatim when using Cargo queries, so you have to format it as an unordered list and use the appropriate buff/nerf/change templates as needed.",
"description": "If enabled, the quote will not be displayed on this page, but will still be stored and used for cargo queries.",
"example": "*{{nerf|Base movement speed ramping level endures persistently\n*{{change|Max level goggle tightness loosened|Max|Sam}}",
"type": "content",
"required": true
},
"names": {
"aliases": [
"name"
],
"label": "Names",
"description": "A list of names of subjects, separated by semicolons. This is the \"key\" used to list changes using Cargo; for example, creating a list of changes with the name \"Dark Castle\" and querying a list of changes with the name \"Dark Castle\" will only display changes under the name \"Dark Castle\". If using multiple names, separate them with commas with one space. NOTE: Previously, the separator was a comma with one space. If a page still uses this, it needs to be edited to use a semicolon with no space for it to work properly.",
"example": "Dreadbloon;Dreadrock Bloon",
"type": "string",
"required": true
},
"show quote": {
"label": "Show quote?",
"description": "If set to \"0\", the quote will not be displayed on this page, but will still be stored and used for cargo queries.",
"type": "boolean"
"type": "boolean"
},
},
Line 48: Line 31:
"type": "number"
"type": "number"
},
},
"changes store": {
"changes 1 names": {
"label": "Changes store",
"aliases": [
"names",
"name",
"names 1",
"name 1"
],
"label": "Changes 1 names",
"description": "A list of names of subjects, separated by semicolons. This is the \"key\" used to list changes using Cargo; for example, creating a list of changes with the name \"Dark Castle\" and querying a list of changes with the name \"Dark Castle\" will only display changes under the name \"Dark Castle\". If using multiple names, separate them with commas with one space. NOTE: Previously, the separator was a comma with one space. If a page still uses this, it needs to be edited to use a semicolon with no space for it to work properly.",
"example": "Dreadbloon;Dreadrock Bloon",
"type": "string",
"required": true
},
"changes 1": {
"aliases": [
"changes"
],
"label": "Changes 1",
"description": "A list of changes. This text is copied and transcluded verbatim when using Cargo queries, so you have to format it as an unordered list and use the appropriate buff/nerf/change templates as needed.",
"example": "*{{nerf|Base movement speed ramping level endures persistently *{{change|Max level goggle tightness loosened|Max|Sam}}",
"type": "string",
"required": true
},
"changes 1 store": {
"aliases": [
"changes store"
],
"label": "Changes 1 store",
"description": "The value in this parameter will be stored in the cargo table instead of the value of the \"changes\" parameter if this is set to anything. This can be used to display a different value on the page this template is used on than on the pages that use cargo queries.",
"description": "The value in this parameter will be stored in the cargo table instead of the value of the \"changes\" parameter if this is set to anything. This can be used to display a different value on the page this template is used on than on the pages that use cargo queries.",
"type": "string"
"type": "string"
}
},
"changes 2 names": {
"aliases": [
"changes 2 name"
],
"label": "Changes 2 names",
"description": "The same thing as \"Changes 1 names\", but for \"Changes 2\".",
"type": "string"
},
"changes 2": {
"description": "A second list of changes, for if you want to display changes that apply to different subjects in a single list.",
"type": "string"
},
"changes 2 store": {
"label": "Changes 2 store",
"description": "The same thing as \"Changes 1 store\", but for \"Changes 2\".",
"type": "string"
},
"changes 3 names": {
"aliases": [
"changes 3 name"
]
},
"changes 3": {},
"changes 3 store": {},
"changes 4 names": {
"aliases": [
"changes 4 name"
]
},
"changes 4": {},
"changes 4 store": {},
"changes 5 names": {
"aliases": [
"changes 5 name"
]
},
"changes 5": {},
"changes 5 store": {},
"changes 6 names": {
"aliases": [
"changes 6 name"
]
},
"changes 6": {},
"changes 6 store": {},
"changes 7 names": {
"aliases": [
"changes 7 name"
]
},
"changes 7": {},
"changes 7 store": {},
"changes 8 names": {
"aliases": [
"changes 8 name"
]
},
"changes 8": {},
"changes 8 store": {},
"changes 9 names": {
"aliases": [
"changes 9 name"
]
},
"changes 9": {},
"changes 9 store": {},
"changes 10 names": {
"aliases": [
"changes 10 name"
]
},
"changes 10": {},
"changes 10 store": {}
},
},
"description": "This template formats a list of changes and stores it using Cargo. This is a generic template for listing changes to most gameplay features (maps, powers, knowledge, etc). Changes to towers and heroes should use their dedicated changes template instead.",
"description": "This template formats a list of changes and stores it using Cargo. This is a generic template for listing changes to most gameplay features (maps, powers, knowledge, etc). Changes to towers and heroes should use their dedicated changes template instead.",
"paramOrder": [
"version",
"version note",
"quote",
"show quote",
"changes",
"changes store",
"names",
"priority"
],
"format": "block"
"format": "block"
}
}
</templatedata>
</templatedata>
<includeonly>[[Category:BTD6 templates]][[Category:Changelog templates]]</includeonly><noinclude>[[Category:Documentation]]</noinclude>
<includeonly>[[Category:BTD6 templates]][[Category:Update history templates]]</includeonly><noinclude>[[Category:Documentation]]</noinclude>

Latest revision as of 21:28, 5 December 2025

This template formats a list of changes and stores it using Cargo. This is a generic template for listing changes to most gameplay features (maps, powers, knowledge, etc). Changes to towers and heroes should use their dedicated changes template instead.

Template parameters

This template prefers block formatting of parameters.

ParameterDescriptionTypeStatus
Quotequote

A quote from official patch notes accompanying these changes. The text is formatted as a quotation from "Version <x> update notes".

Example
Glue Rat pet has been overperforming in all game modes for a while now without any apparent weakness or strategic downsides.
Stringoptional
Version numberversion

The version number of these changes. This determines which version header to list these changes under in a Cargo query.

Example
2.0
Numberrequired
Hide quote?hide quote

If enabled, the quote will not be displayed on this page, but will still be stored and used for cargo queries.

Booleanoptional
Version noteversion note

Adds text in parentheses after the version number in cargo queries. For example, if this change is from a future update, this can be used to specify that the change is "upcoming".

Example
upcoming
Stringoptional
Prioritypriority

Determines the order that changes within each version will be displayed in cargo queries. Greater numbers are placed higher.

Numberoptional
Changes 1 nameschanges 1 names names name names 1 name 1

A list of names of subjects, separated by semicolons. This is the "key" used to list changes using Cargo; for example, creating a list of changes with the name "Dark Castle" and querying a list of changes with the name "Dark Castle" will only display changes under the name "Dark Castle". If using multiple names, separate them with commas with one space. NOTE: Previously, the separator was a comma with one space. If a page still uses this, it needs to be edited to use a semicolon with no space for it to work properly.

Example
Dreadbloon;Dreadrock Bloon
Stringrequired
Changes 1changes 1 changes

A list of changes. This text is copied and transcluded verbatim when using Cargo queries, so you have to format it as an unordered list and use the appropriate buff/nerf/change templates as needed.

Example
*{{nerf|Base movement speed ramping level endures persistently *{{change|Max level goggle tightness loosened|Max|Sam}}
Stringrequired
Changes 1 storechanges 1 store changes store

The value in this parameter will be stored in the cargo table instead of the value of the "changes" parameter if this is set to anything. This can be used to display a different value on the page this template is used on than on the pages that use cargo queries.

Stringoptional
Changes 2 nameschanges 2 names changes 2 name

The same thing as "Changes 1 names", but for "Changes 2".

Stringoptional
changes 2changes 2

A second list of changes, for if you want to display changes that apply to different subjects in a single list.

Stringoptional
Changes 2 storechanges 2 store

The same thing as "Changes 1 store", but for "Changes 2".

Stringoptional
changes 3 nameschanges 3 names changes 3 name

no description

Unknownoptional
changes 3changes 3

no description

Unknownoptional
changes 3 storechanges 3 store

no description

Unknownoptional
changes 4 nameschanges 4 names changes 4 name

no description

Unknownoptional
changes 4changes 4

no description

Unknownoptional
changes 4 storechanges 4 store

no description

Unknownoptional
changes 5 nameschanges 5 names changes 5 name

no description

Unknownoptional
changes 5changes 5

no description

Unknownoptional
changes 5 storechanges 5 store

no description

Unknownoptional
changes 6 nameschanges 6 names changes 6 name

no description

Unknownoptional
changes 6changes 6

no description

Unknownoptional
changes 6 storechanges 6 store

no description

Unknownoptional
changes 7 nameschanges 7 names changes 7 name

no description

Unknownoptional
changes 7changes 7

no description

Unknownoptional
changes 7 storechanges 7 store

no description

Unknownoptional
changes 8 nameschanges 8 names changes 8 name

no description

Unknownoptional
changes 8changes 8

no description

Unknownoptional
changes 8 storechanges 8 store

no description

Unknownoptional
changes 9 nameschanges 9 names changes 9 name

no description

Unknownoptional
changes 9changes 9

no description

Unknownoptional
changes 9 storechanges 9 store

no description

Unknownoptional
changes 10 nameschanges 10 names changes 10 name

no description

Unknownoptional
changes 10changes 10

no description

Unknownoptional
changes 10 storechanges 10 store

no description

Unknownoptional