Ideas & systems
Stats and tags
Everything in the Ledger has a measure. A stat says how much, a capability says whether, and both are written down once and shared by every page that needs them.
What it is
A tag is a named property that your whole game shares. You make it once, then attach it to components. It comes in a few kinds.
| Kind | What it holds | Example |
|---|---|---|
| Built-in stat | A number with a maximum. Ready made, and the same in every game. | Health, XP |
| Custom stat | A number with a maximum that you name yourself. | Pages |
| Capability | A yes-or-no ability. It is there or it is not. | Reaping |
| Slot | A named place on a character where gear sits. | A weapon slot |
People say "stat" and "attribute" loosely. In these pages a stat is a number that changes, such as Health. A capability is a fixed ability, and an action can ask for it. Both are kinds of tag.
How it works
- You attach a tag to a level. For a stat you give a value (where it starts) and a max (its top). A capability needs neither: having it is enough.
- Copies carry their own numbers. When a copy is made, it takes the stats of its level. Two sickles in a game each keep their own Health.
- Actions read and change stats. A requirement can ask for a capability or a stat. An effect can add to a stat or take from it. A change is kept between 0 and the max.
- Levels pass stats upward. A level lists only what is new. A stat set on level 1 still applies on level 2 and 3 until a higher level sets it again. Then the new numbers replace the old ones for that level and above.
- XP is the exception. XP never passes upward. A level that should level up needs its own XP row with a max. When XP reaches the max, the component moves up a level.
You set stats and capabilities in Edit Mode, in the Stats & capabilities card of the property window. Click Add a stat or capability… and type in Search stats and capabilities. If the name already exists, Edit Mode reuses it. A new stat starts at 0 of 100, Health at 100 of 100, XP at 0 of 100, and a capability at 1.
In Vespera
In Vespera: Health, Reaping and Pages Play it
- Health on the Heirloom Wheat. The Heirloom Wheat has a Health of 20 of 20. Each cut of the sickle takes 1 away, so a plant that has been cut keeps its own count.
- Reaping on the Rusty Sickle. The sickle has the capability Reaping, and also a Health of 12 of 12. The Heirloom Wheat's cut asks for a tool with Reaping, and each cut wears the sickle down by 1.
- Pages on the Ledger. The Ledger of Making carries a stat you named yourself, Pages, which starts at 0 of 7. It is shown in the top corner of the game.
Good to know
- Stats need a unique item. Edit Mode says "Only unique items have stats and attributes." for an item that is not unique, and offers a link to make it unique.
- Capabilities are yes or no. Check them with "has it", never with "at least 2".
- A value of 0 does not switch a stat off. A stat stays on every level above the one that names it. It only changes when a higher level sets it again.
- Use a built-in stat when one fits. Health, XP and Stamina come with behaviour. A stat of your own named "Hits" does not.
- A tag must exist before an action can use it. Make it first, then refer to it.
Under the hood
- XP, Health and Stamina are built in and are the same in every game. XP levels a component up when it fills its bar. Health at 0 can destroy a target, a tool or a place, but never the player's own character. Stamina refills when the player ends a turn.
- Capabilities and slots always hold the value 1, and a requirement checks only that they exist.
- A copy of a component gets its stats from its level when it is made. Copies made some other ways, such as a story reward, a pick-up or a transfer, may start without them.
- When a stat's value changes during an action, the result is kept between 0 and the stat's maximum.
- A stat that belongs to a place is fed only by the place the player is in.