Filter list → Sum or count
Filter list takes a list from the sheet (attributes, skills, cards, fields…) and keeps only the items that answer yes to a question. Inside that question, $item is the item being looked at.
Example: name the filter Equipped, choose Resources and use the question $item.equipped == true (“is this card equipped?”). Then, in Sum or count, use $("Equipped") as the list. Count says how many cards passed; Sum with field quantity adds up their quantities.
A rule cannot go backwards: do not connect a step back to an earlier one. To go through several items, use Filter list and Sum or count.
Filter on Resources:
$item.equipped == true
List for Sum or count:
$("Equipped")
Operation: Sum
Field: quantity
Store value: just now or for later uses
Store value gives a name to a result so later steps can use it. If it is a number, they can read it as @name; other kinds of value are read with $("Step name"). With Local scope, the value lasts only while the rule runs and does not appear in any sheet field. In a card's passive effects, numbers and yes/no values are available as @name across the whole sheet while the effect is active. Removing the card or deactivating the effect removes its publication.
With Sheet memory scope, the value is kept for the next time the rule runs. Read it with $sheet.memory.name. This only works in rules that begin at Trigger; in rules that begin at Start, nothing is stored.
Usage counter example: store coalesce($sheet.memory.usos, 0) + 1 in the memory usos. Memory is invisible to the player; to change a number shown on the sheet, use Change value.
Name: usos
Scope: Sheet memory
Value in expression mode:
coalesce($sheet.memory.usos, 0) + 1
When the list is empty
For an empty list, Count and Sum give 0. Min, Max, Average, First and Last are empty (null). If you need a number in those cases, use coalesce($("Sum or count"), 0).
To sum, say which field to add up, such as quantity or total. Without the field, the sum does not use the numbers you expect.