# PIECE

> The PIECE panel — Platform kind, Surface, the seat an entity belongs to, token and coin flipping and card paper thickness. A Platform panel, not a component.

- Source: https://diceytable.com/docs/editor/inspector/piece
- Last verified: 2026-10-06

`PIECE` is a **Platform panel**, rendered with the platform header accent, sitting directly
below `ENTITY` and above `RENDER`. It used to be two fields (`TYPE`/`SURFACE`) living inside
`RENDER`, which made "what is a component?" unanswerable — entity kind and physical surface
are DiceyTable classifications, not render state. Splitting them into their own panel is why
the accent-color distinction exists at all; see
[Provenance and lifecycle](https://diceytable.com/docs/editor/concepts/provenance#why-the-inspector-colors-headers-differently).

Source: the `PIECE` `EmCollapsible` (`tone="platform"`) in `TableEditModeShell.tsx`'s `object`
Inspector branch.

## Fields

`PIECE` renders one of two forms depending on whether the object carries a custom/imported
model (`metadata.customModelAssetId` is set).

### Custom / imported pieces — both fields editable

| Field | Type | Values | Default | Runtime effect | Replicates |
|---|---|---|---|---|---|
| **Type** | select | the 11 Platform kinds, by their author-facing names: `Card`, `Deck`, `Die`, `Token`, `Board`, **`Container`** (the `bag` wire kind — see [CONTAINER](https://diceytable.com/docs/editor/inspector/platform-panels#container)), `Custom piece`, `Card holder`, `Button`, `Table` (furniture the game is played on — see [Object kinds § Table](https://diceytable.com/docs/mods/reference/object-kinds#table)), `Coin` (a flat piece that players can toss with **Flip Coin** — see [Object kinds § Coin](https://diceytable.com/docs/mods/reference/object-kinds#coin); set your own coin model to it to make it tossable). The list is derived from `tableObjectKindSchema.options` and labelled by `tableObjectKindLabel`, so no wire spelling ever reaches the dropdown. | the kind chosen at creation | Reclassifying an object's kind. Drives the sound-event mapping (which events this piece can emit) and, through `defaultObjectPhysicsForKind`, the *suggested* physics defaults shown as placeholders under `RIGIDBODY` — it does not overwrite physics fields you have already set. | Yes — `TableObjectState.kind` |
| **Surface** | select | the 12 sound materials, by label: `Wood`, `Cardboard`, `Metal`, `Plastic`, `Card / paper`, `Tile`, `Felt`, `Cloth / leather`, `Glass`, `Stone / ceramic`, `Generic`, `Silent` (wire values `wood` … `silent`, labelled by `soundMaterialLabel`) | the kind's default material | The physical surface, and it works in **two directions**. As the piece that moves, it picks the impact clips — `felt`/`cloth` borrow the `cardboard` recordings and `glass`/`stone` the `tile` ones, because the licensed pack has none of their own. As the thing **underneath**, it colours the sound of every piece that lands on this one: set a board to `Felt` and a die dropped on it thuds, set it to `Glass` and the die rings (see [Sound material § Struck-surface tone](https://diceytable.com/docs/reference/enums/sound-material#struck-surface-tone)). It also drives — via the same `defaultObjectPhysicsForKind` — the read-only "From surface" mass/friction/restitution readout under `RIGIDBODY`. `silent` suppresses the piece's own sound entirely. | Yes — `TableObjectState.material` |

A hint under these two fields spells out the coupling: *"Surface drives impact sounds and the
physics defaults (mass, friction, bounce). Adjust the numbers under Rigidbody afterward."*

### Standard (non-custom) pieces — read-only

For every standard-preset piece (not a custom/imported model), `PIECE` shows a single
read-only row:

| Field | Type | Runtime effect | Replicates |
|---|---|---|---|
| **Type** | read-only text | Displays `object.kind` (e.g. `die`, `card`) with no control to change it. Standard pieces are not reclassified from the Inspector — their kind was fixed by the preset they were spawned from. | n/a (read-only view of `TableObjectState.kind`) |

Standard pieces have no editable **Surface** field either — their sound material is fixed by
the preset, and the admin-only [SOUND SETS (BUILT-IN)](https://diceytable.com/docs/editor/inspector/platform-panels#sound-sets-built-in)
section shows the resulting bindings read-only.

### Flippable (`token` and `coin` pieces only)

Every `token` and every `coin` — custom or standard — gets one more row, below **Type**:

| Field | Type | Values | Default | Runtime effect | Replicates |
|---|---|---|---|---|---|
| **Flippable** | select | `Auto (…)`, `Yes`, `No` | `Auto` | Whether this piece offers **Flip** (turn over 180°). **Auto** removes the per-object override so the **shape** decides — a piece at most half as tall as its narrower footprint flips (checkers, coins, chits), a taller one does not (meeples, miniatures) — and the option shows the shape's current answer, e.g. `Auto (Yes)`. **Yes** / **No** pin it. A token that may not flip has no Flip in the context menu, touch rail or VR menu, and the host refuses a `flip` sent to it by anyone, scripts included. | Yes — `TableObjectState.flippable` (absent under Auto) |

A hint under it reads *"Whether this piece offers Flip (turn over 180°). Auto lets flat pieces
like checkers flip and keeps tall ones like meeples upright."* A pinned value here wins over the
model's own [`.meta.json` `flippable`](https://diceytable.com/docs/mods/files/sidecars#flippable), which is only the
default a newly placed piece starts with. A **coin** is flat by definition, so it does not consult its
shape: left on **Auto** it flips, and only **No** turns Flip off. Cards and decks always flip and no other
kind does, so the row is not shown for them. See
[Object kinds § Flipping a token](https://diceytable.com/docs/mods/reference/object-kinds#flipping-a-token) for what a
token's flip actually does, and [§ Flipping a coin](https://diceytable.com/docs/mods/reference/object-kinds#flipping-a-coin) for a coin.

### Seat

Every entity — custom or standard, any kind — gets a **Seat** row:

| Field | Type | Values | Default | Runtime effect | Replicates |
|---|---|---|---|---|---|
| **Seat** | select | `No seat`, then the scene's seats by the names the scene gives them (the whole seat palette when the scene has no seats yet) | `No seat` | **None.** It labels the entity as belonging to that seat — White's sixteen chess pieces to the White seat — so a table script can read [`handle.seat`](https://diceytable.com/docs/scripting-api/objecthandle#objectdataseat) or ask for [`getAllObjects({ seat })`](https://diceytable.com/docs/scripting-api/world#worldgetallobjects). It does not hide the entity, put it in anyone's hand, change its physics, or stop another player moving it. | Yes — `TableObjectState.seat` (a seat id; absent under `No seat`) |

The value stored is the seat's **id** (its colour — `white`, `brown`, …), so renaming a seat in the scene does not
detach its pieces, and a script compares against the id rather than the name.

This is **not** the hand ownership that hides cards (`ownerSeat`, which a hand zone sets and clears as cards move),
and it is **not** the [seat template](https://diceytable.com/docs/editor/working/zones-and-seats): the template clones holders once per
claimed seat, while an entity with a seat is one fixed entity that exists whoever sits down. An entity the seat
template stamps onto a seat shows **From the seat template** here, disabled — the template decides its seat.

To give a seat to many entities at once — a whole folder of pieces, or a selection — use
[`GROUP EDIT`'s Seat row](https://diceytable.com/docs/editor/working/multi-select#seat) instead of setting it one by one. The Hierarchy
shows a small dot in the seat's colour after the name of every entity that has one.

### Deck source (`deck` pieces only)

| Field | Type | What it tells you |
|---|---|---|
| **Deck source** | read-only text | `Custom: <deck id>` when the object carries a baked `metadata.customDeck` slice — hover for the image/card counts and sheet path — or a warning-coloured **Standard 52-card deck** when it does not. |

This row exists because the two are otherwise **indistinguishable**: a deck spawned from
one of your `.deck.json` assets and one dragged out of the standard preset catalog look
identical on the table and carry the same `deck` kind in the Hierarchy. The only
difference is a `metadata.customDeck` slice, which nothing else surfaces — and mods have
shipped a generic playing-card deck while their author was busy editing and republishing
a custom deck that had never been placed.

If it reads *Standard 52-card deck* and you wanted your own, delete the object and drag
the deck in from **Project → Decks**; see
[the Deck editor](https://diceytable.com/docs/editor/item-editors/deck#authoring-a-deck-is-not-the-same-as-placing-it).

### Paper thickness (`card` and `deck` pieces only)

Every `card` and every `deck` — custom or standard — gets one more row:

| Field | Type | Values | Default | Runtime effect | Replicates |
|---|---|---|---|---|---|
| **Paper thickness (mm)** | number | 0.05–3, step 0.01, **always millimetres** | `0.3` (a standard playing card) | The thickness of one card. A `card` is one sheet thick; a `deck` stands *thickness × the number of cards in the pile* tall, and gets shorter as it is drawn from. A card drawn or dealt from a deck inherits the deck's value, so a pile and the cards that came out of it are always the same stock. Changing it resizes the entity and its collider at once. | Yes — `TableObjectState.metadata.paperThicknessMm` (absent at the default) |

A hint under it does the sum for a deck — *"52 cards × 0.3 mm = 15.6 mm tall."* — and, for
both kinds, reads *"A standard playing card is 0.3 mm."*

The field stays in millimetres whatever length unit **File ▸ Preferences** has the rest of the
editor showing. Card stock is specified in millimetres, and the number is too small to read in
anything larger: 0.3 mm is 0.000984 ft. The top of the range, 3 mm, is thick enough for a tile
or a chipboard token.

Setting the field back to `0.3` removes the key rather than storing the default, so an
entity nobody has touched keeps following the platform default.

> **The default was 0.2 mm before 2026-10-01**, and it was not a setting. Every card and deck
> without a value of its own is now half as thick again: a 52-card deck stands 15.6 mm
> (0.0512 ft) where it stood 10.4 mm. Nothing in a scene needs editing; set the field to `0.2`
> on a deck you want at its old height.

### Search (`deck` pieces only)

A container (`bag`) has the same two rows, but they are not here — they moved to the
[CONTAINER](https://diceytable.com/docs/editor/inspector/platform-panels#container) panel, where they sit beside
`Form`, `Container mode` and the rest of that container's policy.

| Field | Type | What it does |
|---|---|---|
| **Search** | select | Who may privately look through this pile: `Not set`, `No one`, `Owner seat only`, `Host only`, `Owner seat and host`, `Anyone`. |
| **After search** | select | What happens to the remainder when the session closes: `Not set`, `Shuffle the rest`, `Keep the order`. |

Both are three-state. **Not set** removes the setting entirely, which is the only way back to
unauthored once you have picked something: the pile then inherits from the surrounding `Area`
zone, and then from the kind default (`Owner seat and host` for a deck, **`No one` for a bag**,
`Shuffle the rest` for the order).

Set here, either one **overrides** what the zone says — and the two resolve independently, so a
deck that sets only **After search** still inherits the zone's audience. The `Not set (…)` label
names the *kind default*, not the zone's value, so read the zone's own dropdown to see what an
unset pile sitting in it will do.

Full precedence rules, defaults and what a search looks like at the table:
[Deck and Bag Search](https://diceytable.com/docs/editor/workflows/deck-search).

## What "Type" is not

Neither **Type** field is `parentId`, and neither is the read-only `Kind` in
`ENTITY (ADVANCED)` (the *engine* component-type list, which is a completely different axis —
see [The scene model](https://diceytable.com/docs/editor/concepts/scene-model#the-hierarchys-node-kinds)). This
`Type` is `TableObjectState.kind`, the Platform classification described in
[Provenance and lifecycle](https://diceytable.com/docs/editor/concepts/provenance#axis-1-provenance-who-defined-it).

## See also

- [platform-panels.md](https://diceytable.com/docs/editor/inspector/platform-panels#sound-sets-built-in) — where
  `Surface`'s sound bindings surface for review.
- [rigidbody.md](https://diceytable.com/docs/editor/inspector/rigidbody) — where the "From surface" physics readout
  driven by this panel's `Surface` field appears.
- [render.md](https://diceytable.com/docs/editor/inspector/render) — the next section down, and the one `PIECE`
  used to be (wrongly) part of.
- [`ObjectHandle`](https://diceytable.com/docs/scripting-api/objecthandle) — `ObjectData.kind`, the same kind as a table script sees it.
