Help - Editing & Syncing Components

Realtime Playtest

Editing & Syncing Components

Understand the blueprint-vs-table-copy model, and use the right-click Component menu to edit, restore, and save changes.

Editing & Syncing Components in a Room

This is one of the most useful concepts to understand, and the one that confuses people most. Every piece on the table is a live copy of a saved component in your project. Knowing how the two relate lets you fix and tweak things mid-playtest without breaking your table.

Blueprint vs. Live Copy

  • The component in your project's Components tab is the blueprint: the master definition (name, image, size, and so on). It's the source of truth.
  • A piece on the table is a live copy you spawned from that blueprint. You can move, flip, and rotate it freely without touching the blueprint.

Important

Editing the blueprint does not automatically update copies already on the table. Change a component's image in the library and the pieces already spawned keep the old art until you sync them (below) or spawn fresh ones.

The Component Menu

Right-click a component-linked piece and open Component ▶ to move changes between the blueprint and the table:

  • Edit Component: open the full editor in a modal and change the blueprint without leaving the room.
  • Save State to Component: push this piece's current scale, rotation, color, and snap points up to the blueprint.
  • Restore (Load) from Component: pull the blueprint's latest definition down onto this piece.
  • Save as New Component: promote a quick-spawned generic piece into a brand-new component in your project.

Worked Example: Fixing Art Mid-Playtest

A tester points out a confusing card:

  1. Right-click the card and choose Edit Component.
  2. Swap in the corrected art and save.
  3. Right-click the copies on the table and choose Restore from Component.

The new art appears immediately, with no re-spawning and no need to close the room.

Tip

Built a piece by feel from the Generic Objects panel and want to keep it? Save as New Component files it into your project so you can spawn it again next session.


Related: Host Controls · Components · Dextrous Import