Token types, explained.
One collection can hold more than one kind of token. Here's how token types group tokens, control which attributes apply, and keep scoring and rarity fair.
A token type is a group of tokens that share the same set of attributes. Every collection has at least one, and every token belongs to exactly one type. If your set is uniform — all characters, say — you'll never think about it. But the moment a collection mixes kinds of token, types are what keep them tidy.
Why more than one type?
Imagine a collection with Characters and Items. A character has Strength and an Element; an item has a Material. They shouldn't share one flat list of attributes — a character has no Material, an item has no Strength. Token types let both live in the same collection while each carries only the attributes that make sense for it.
One schema, assigned per type
Attributes are defined once in the collection's master schema — never duplicated per type. Then, for each token type, every attribute is one of three things:
- Required — every token of this type must have it.
- Optional — allowed, but not mandatory.
- Unassigned — not available on this type at all.
| Attribute | Character | Item |
|---|---|---|
| Strength | Required | — |
| Element | Optional | Required |
| Material | — | Required |
| Power | Optional | Optional |
It stays out of your way until you need it
With a single token type, Toko keeps things effortless: any new attribute you create is auto-assigned to that type as optional. The moment you add a second type, that auto-magic stops — new types start with no assignments, and new attributes aren't auto-added to anything. From then on you assign each attribute to each type deliberately. Existing assignments are never disturbed by the switch.
You can set a token's type one at a time in its editor, or select many tokens and move them to a target type at once. A bulk move runs a dry-run first: any token that wouldn't satisfy the target type's rules is reported with the reason and left untouched.
Validation and locking
Token type is part of what's checked when a token moves Draft → Review. A token must have a type, carry all of that type's required attributes, and carry none that are unassigned for it; the transition is blocked otherwise. You can change a token's type while it's a Draft; after Review it's locked, because attributes and identity are settling for go-live.
Scoring and rarity are per type
This is the quietly important part. Because different types have different attributes, Toko scores and ranks them within each type — never pooled across the whole collection. A type with five scoring attributes would otherwise always outscore one with a single attribute and sweep the top tiers. In Weighted rarity, the per-tier quotas are evaluated per type too.
Score Rank reads as “within Character · 312 tokens”, not across everything — so a humble Item can still be the rarest Item. See Token score and Rarity for how that flows through.
In short
- A token type groups tokens that share an attribute set; every collection has at least one, every token has exactly one.
- Attributes are defined once, then set per type as required, optional, or unassigned.
- One type auto-assigns new attributes as optional; adding a second type switches to explicit assignment.
- Draft → Review checks the token has its type's required attributes and none it shouldn't; type is editable only in Draft.
- Scoring and rarity are evaluated per type, never pooled across the collection.