The collection's attribute schema and scoring. Four fixed V1 sub-tabs — Manage Attributes, Calculation, Generator Mapping, Apply Values — plus a collection-level "Show Score?" toggle. Schema and score visibility lock at Live. Framed on the studio page shell: breadcrumb on white, header on grey.
01Attributes · first run (empty)No attributes yet — hero empty state with Add-attribute & Add-token-type CTAs and common-starter presets. Show-Score stays hidden until at least one attribute exists.
Define the attributes your tokens can have. Add your first attribute or start from a common preset — values get assigned to individual tokens later.
Draft
Add your first attribute
Attributes are the attributes that make each token unique — Strength, Class, Tags, Description. Define them once here, then assign values to individual tokens later. Pick a quick-start below, or build your own.
Token types Editable in Draft
Each token references exactly one token type. Your collection starts with a Default type, so you can get going without configuring this — new attributes auto-assign to Default as Optional. Add a second type later if the collection mixes fundamentally different kinds of tokens (e.g. Characters and Consumables).
Default · 0 tokens
02Attributes · Manage Attributes (populated)Schema source of truth: token types, the attribute list with required/optional states, and the Show-Score toggle (shown once attributes exist).
Define the trait schema, decide which attributes each token type requires, and choose whether a token's score is shown to collectors.
Draft
Show Score? Locks at Live
Each token can be given a score based on its attributes. Choose whether that score is visible to collectors in the token preview and edit views.
Attribute schema
Locks at Live
The master list of attributes for this collection — each attribute is defined once here. An attribute has a name and a number of values (one or many). Whether it's required is not a property of the attribute itself; it's set per token type. With a single token type, new attributes auto-assign to Default as Optional — the column below shows that assignment. Once the collection goes Live the schema is immutable.
Name
Kind
On Default type
Strength
Number
Required
Class
Category
Required
Tags
Flags
Optional
Signed by
Principal
Optional
Holographic
Boolean
Optional
Cooldown
Duration
Optional
Description
Text
Optional
Token types
1 type
Each token references exactly one token type. This collection has a single Default type, so every attribute's requirement is set right here in the schema's "On Default type" column — there's no assignment matrix. Add a second type if the collection mixes fundamentally different kinds of tokens.
Default · 80 tokens
03Attributes · CalculationPick the score method. Affects score output only; visibility is controlled by the Show-Score toggle.
Choose how the per-token attribute score is calculated from the mapped numeric values.
Draft
Score method
Affects every token's score
Only values that are actually mapped contribute — unmapped values are skipped, not treated as zero.
Add Values Defaultscore = Σ values
Sum all mapped numeric values. The most common, predictable method.
Multiply score = Π values
Multiply the mapped values together — rewards tokens that hit several high attributes at once.
Highest score = max(values)
Take only the single highest mapped value. Good when one standout trait should define the token.
04Attributes · Generator Mapping (Layer)Sub-tabbed into Layer mapping and Part mapping. Layer rules are the fallback; a part rule overrides its layer for the same attribute. Mapping is added via a modal (frame 18).
Turn generator composition into attribute metadata. A selected part's mapping wins over its layer's mapping for the same attribute.
Draft
Precedence: a part-level mapping overrides the layer-level mapping for the same attribute. Each trait resolves to at most one value per token — conflicting configs are rejected on save.
Generator: Lorem Drop No. 1
Layer · Background→BackgroundLayer
Layer · Body→BodyLayer
Layer · Headwear→HeadwearLayer
Layer · Eyes→EyesLayer
Per-part overrides live under Part mapping. A part rule wins over its layer rule for the same attribute.
05Attributes · Apply ValuesAssign numeric values to non-numeric trait values so they can feed the score. Numeric attributes feed directly.
Give each non-numeric trait value a number so the calculation can score it. Values left blank simply don't contribute.
Draft
Numeric value mapping
Method: Add Values
Only non-numeric attributes appear here — numbers like power feed the score directly. Map an attribute's values to numbers in a modal; each row shows its status. Required attributes must be fully mapped before Review.
Background
Category · 3 values
RequiredAll values mapped
Eyes
Category · 3 values
Optional2 of 3 mapped
Class
Category · 4 values
RequiredNeeds values
Class is required but not fully mapped. A required attribute with unmapped values blocks Review. Optional values left blank simply contribute no score.
06Attributes · Live (read-only)Schema and score visibility lock at Live. The configuration stays visible for reference.
The schema buyers' tokens were validated against — locked when the collection went Live.
Live
This collection is Live. The attribute schema and the Show-Score setting are locked. Required-field edits are blocked; draft-only normalization no longer applies.
Locked at Live (read-only)
Token typesStandard
Attributes5 (2 required)
Calculation methodAdd Values
Show scoreShown to collectors
Generator mappings4 (2 part overrides)
07Attributes · Add modalsCreate a new attribute (key, label, kind, arity, required) or a new token type.
Add attribute
Category = single-select (pick one) · Flags = multi-select (pick any) · Fields = nested record. You define the values for Category and Flags.
With one token type, this attribute auto-assigns to Standard as optional. Make it required from the attribute row.
Add token type
Adding a second token type turns off auto-assignment. From then on, every attribute must be assigned to each type explicitly as required, optional, or unused.
08Attributes · Delete modalsDeleting an attribute — the destructive confirm, and the blocked state when the attribute is locked by non-draft tokens.
Delete attribute "Eyes"?
This removes the eyes trait from the schema, along with its numeric value mapping and any generator mappings that target it. Affected token scores will be recomputed.
Only possible while every token that uses this attribute is in Draft. This can't be undone.
Can't delete "Background"
background is referenced by tokens in Review or Live, so it's locked. Used by non-draft tokens
Return the referencing tokens to Draft to edit or delete this attribute. Required-field edits and deletions are blocked while any token is in Review or Live.
09Attributes · multiple token typesMaster schema kept separate; the Token types panel is tabbed — pick a type to manage which attributes apply and how (required / optional / unused). Scales to many types and reflows on mobile, unlike a wide matrix.
This collection mixes more than one kind of token. The attribute schema is shared; each type's requirements are managed in its own tab below.
Draft
Show Score? Locks at Live
Each token can be given a score based on its attributes. Choose whether that score is visible to collectors.
Attribute schema
Locks at Live
The master list of attributes — defined once and shared by every token type. Whether each is required is set per token type in the Token types panel below, not here.
Name
Kind
Strength
Number
Class
Category
Tags
Flags
Cooldown
Duration
Description
Text
Token types Editable in Draft
6 types
Each token references exactly one type. Pick a type to manage which attributes apply and how. Add, rename or delete types while in Draft; types lock at Live. This scales to any number of types and stacks cleanly on mobile.
Character
62 tokens · 2 required · 2 optional · 1 unused
Strength
Number
Class
Category
Tags
Flags
Cooldown
Duration
Description
Text
10Attributes · Edit & assign modalsOpened from the schema table's edit icon: editing an attribute under one token type vs. multiple types (per-type assignment), and adding under multiple types. The delete confirm and its blocked state are in 08.
Edit attribute · Class
Requirement is set per token type. With one type it's set here.
Edit attribute · Class 3 types
Character
Creature
Item
With more than one token type, set whether this attribute is required, optional or unused for each.
Add attribute 3 types
Character
Creature
Item
More than one token type, so there's no auto-assign — choose this attribute's requirement for each type before adding.
11Attributes · multiple token types — Live (read-only)A multi-type collection after launch. The shared schema, the Show-Score setting and every per-type requirement are locked. The Token types panel stays tabbed for reference, but read-only — no edit, no segments, no add.
A collection with several token types, now Live. The shared schema and each type's requirements are locked exactly as buyers' tokens were validated against them.
Live
This collection is Live. The attribute schema, the token types, every per-type requirement and the Show-Score setting are read-only. Types can't be added, renamed or deleted, and requirements can't change.
Each token type's attribute requirements as they were at launch. Switch tabs to inspect a type — nothing here can be changed while the collection is Live.
Character
62 tokens · 2 required · 2 optional · 1 unused
Strength
Number
Required
Class
Category
Required
Tags
Flags
Optional
Cooldown
Duration
Optional
Description
Text
Unused
12Calculation · Live (read-only)The score method, locked at Live. The chosen method is shown; the options can't change.
How the attribute score was calculated for this collection — fixed when it went Live.
Live
This collection is Live, so the score method is read-only — it can't change without altering scores buyers already saw.
Score method
Locked · read-only
Add Values In usescore = Σ values
Sum all mapped numeric values.
Multiply score = Π values
Highest score = max(values)
13Generator Mapping · Part mappingThe Part sub-tab. Per-part overrides, each beating its layer rule for the same attribute. Paginated when there are more than 10.
Generator Mapping turns generator composition into attribute metadata. This collection isn't using a generator.
Draft
Layer & part mappings
Unavailable
No generator linked
Generator Mapping converts a generator's layers and parts into attribute metadata. This collection isn't built with a Toko generator, so there's nothing to map — tokens carry only the attributes you set by hand.
15Generator Mapping · linked, no mappings yetA generator is linked but nothing's mapped. Mapping is optional — map your first layer or part to add metadata.
A generator is linked. Mapping its layers and parts to attributes is optional — unmapped composition just won't produce metadata.
Draft
Generator: Lorem Drop No. 1
Map your first layer or part
Nothing is mapped yet. Mapping is optional — map a layer or part to a trait to add metadata to tokens. Anything you leave unmapped simply won't produce a trait.
16Generator Mapping · Live (read-only)Mappings locked at Live. Both sub-tabs stay browsable, read-only — no Add / Edit / Remove.
The generator mappings tokens were derived from — locked when the collection went Live.
Live
This collection is Live. Layer and part mappings are read-only — the attribute metadata buyers' tokens carry can't shift underneath them.
Layer mappings
Locked · read-only
Layer · Background→BackgroundLayer
Layer · Body→BodyLayer
Layer · Headwear→HeadwearLayer
Layer · Eyes→EyesLayer
17Generator Mapping · Live — no generator linkedA collection that launched without a generator, now Live. The tab is read-only and was never used — no layers or parts to map.
This collection launched without a generator — there were never any mappings to lock.
Live
This collection is Live and launched without a linked generator, so Generator Mapping was never used. The tab is read-only.
Layer & part mappings
Locked · read-only
No generator — nothing was mapped
This collection didn't use a Toko generator, so no layer or part mappings were ever created. Its tokens carry only the attributes set by hand.
18Generator Mapping · Map & remove modalsAdd, edit or remove a mapping. The Value field matches the target attribute's kind — Category, Boolean, Number, Text or Duration. A part rule overrides the layer rule for the same attribute.
Map layer
A layer covers many parts, so each token takes the value of whichever part it has. For a Category attribute, part names should match the attribute's values.
A layer rule is the fallback for every part in that layer. A part rule can override it.
Map part · Category attribute
Category attribute — pick one of its defined values.
This part rule overrides the Headwear layer rule for tokens that include Gold Crown.
Map part · Boolean attribute
Boolean attribute — the value is a flag.
The Value field matches the attribute's kind: Category → pick a value · Boolean → Yes or No · Number / Decimal → a number · Text → free text or part name · Duration → a duration.
Remove mapping?
This removes the mapping Part · Gold Crown → Headwear. Tokens that relied on it fall back to the Headwear layer rule — or carry no value for that attribute if there's no layer rule. Affected attribute metadata and scores are recomputed.
Only possible while every token that uses this mapping is in Draft. This can't be undone.
19Apply Values · no attributes yetNothing to map because no attributes exist. Points back to Manage Attributes.
Apply Values gives non-numeric trait values a number for scoring.
Draft
Numeric value mapping
No attributes
No attributes yet
There's nothing to map until you've added some attributes. Create them on Manage Attributes first; any non-numeric values will appear here for scoring.
20Apply Values · nothing to mapAll attributes are already numbers that feed the score directly — no non-numeric values to assign.
A trait-heavy collection. Map each non-numeric value to a number; the list pages 10 attributes at a time.
Draft
Numeric value mapping
Method: Add Values
This collection has more than 10 mappable attributes, so they're paged 10 at a time. Each row shows its status; a required attribute with missing values blocks Review.
Background
Category · 3 values
RequiredAll values mapped
Eyes
Category · 3 values
OptionalAll values mapped
Headwear
Category · 4 values
RequiredAll values mapped
Aura
Category · 3 values
Optional2 of 3 mapped
Class
Category · 4 values
RequiredNeeds values
Material
Category · 5 values
OptionalNot mapped
Showing 1–10 of 22 attributes
22Apply Values · Live (read-only)Value mappings locked at Live. Numbers stay visible for reference; inputs are disabled.
The numeric value mappings scores were built from — locked when the collection went Live.
Live
This collection is Live, so value mappings are read-only — changing them would change scores buyers already saw.
Numeric value mapping
Locked · read-only
Each non-numeric attribute and its mapping status as it launched. Read-only at Live.
Background
Category · 3 values
RequiredAll values mapped
Eyes
Category · 3 values
OptionalAll values mapped
Class
Category · 4 values
RequiredAll values mapped
23Apply Values · Map values modalOpened from a row's Map values / Edit. Give each of the attribute's values a number; required attributes must have every value set before Review.
Map values · Eyes
Optional
Give each value a number for scoring (method: Add Values). Optional attribute — values left blank contribute nothing.
Eyes Category3 values
Plain
Glow
Laser
Map values · Class
Required
Required attribute — every value must have a number before the collection can go to Review.
Class Category4 values
Knight
Mage
Ranger
Rogue
2 of 4 values still need a number. You can save progress, but Review is blocked until every value is set.
