Shared language for modular unit-play

One clear cubit standard and one small modular set beat a cart of impulse buys on week one.

Cubit (table unit)

The agreed modular measure your table uses for footprints and stacks.

Grid footprint

How many squares or hexes a module occupies.

Modular stack

Terrain or kit pieces designed to nest without fighting the grid.

Shared bank

Community dice or modules reserved for guests.

Unit etiquette

Who may rearrange, borrow, or rebuild mid-session.

Label discipline

Readable tags so setup does not become archaeology.

Scale match

Keeping minis, modules, and maps in the same visual language.

Kit checkout

A quick list of what left the shelf and must return.

Archive your campaign notes. Future you—and any guest referee—will thank present you for dated logs and NPC relationship sketches.

Skip merch-shaming. Share unit standards and build tips. Escalate to mods.

High-contrast labels and clear remote camera angles beat pretty kits nobody can parse mid-turn.

Date your unit standard (what a cubit means here) and shared-kit lists. Guests inherit measurements.

Whether you referee weekly or rotate the chair, modular unit-play benefits from a common language. We write for that shared middle ground between lore deep-dives and rules minutiae.

High-contrast labels and clear remote camera angles beat pretty kits nobody can parse mid-turn.

Terms evolve. If your table uses a different gloss, write it into your house doc and tell newcomers which dictionary you are using. Shared language beats winning an etymology fight mid-scene.

When a word is edition-specific, say so out loud. Borrowing vocabulary across systems is fine; silent assumptions are what cause arguments.