Docs Format Expressions
Expressions: Templates
text and path fields are templates: literal text with {expression} holes.
"text": "Level {level} {upper(card_type)}"
"src": "assets/images/attributes/attribute-{attribute}.png"
{{and}}produce literal braces:"{{not a hole}}".- A hole holds any expression, including names, operators and function calls:
{fmt(price, 2)},{foil ? 'FOIL' : ''},{stats.Speed}. - A newline character forces a line break in
textfields, whether it is written in the template or comes from a param value.
Line breaks in values
In JSON, \n inside a string is a newline character. So a text param whose default or card value is "one\ntwo" breaks the line, just like a template "text": "one\ntwo". A double-escaped "one\\ntwo" is a backslash followed by n, and is drawn literally as one\ntwo. In a CSV cell, type a real line break inside a quoted cell.
How values are converted
| Value | Becomes |
|---|---|
| number | At most 12 significant digits, trailing zeros removed: 5, 0.5, 0.3 for 0.1 + 0.2, 0.333333333333 for 1/3. Plain digits from 1e-7 up to 1e21, exponent form outside (1.5e-8). The expression's own value is not rounded |
| bool | true or false |
| text | unchanged |
| color | #RRGGBBAA (8-bit) |
| list or list item | error 3003; use a field or an index |
Use fmt(number, decimals) when you need a fixed number of digits.
path fields
A path field is a template whose result must be a project path or an https:// URL: image src. Because the path is built at render time, the check "does the file exist" also happens at render time, per card (error 4001).
When you rename or move a file in the editor, templates that build paths from params cannot be rewritten automatically; the Files tab lists them first so you can fix them by hand. See Builder: Files.
No concatenation operator
There is no + for text. Combine pieces with a template: "{first} {last}".