Think in members, not just the visible pile
A pile on the table can represent several physical cards with different identities, owners, face directions, and roles. The visible top card is only one view of that composition. Before changing the pile, inspect its members and identify which card is the top, which cards are sources or attachments, and whether any member is intentionally face down.
This matters for layered shields, evolution stacks, linked cards, and effects that place a card above or below an existing object. A shortcut that flips or moves the entire pile can erase information that belongs to individual members.
State the insertion position
When adding a card, choose whether it becomes the visible top, sits directly under the top, or goes to the bottom of the composition. The correct choice depends on the agreed effect. For a face-up shield with new face-down members beneath it, preserve the existing face-up top and insert the new members below it rather than covering the whole object.
- Open the destination object's member view.
- Confirm the current top card and each member's face direction.
- Select the incoming cards and the explicit insertion position.
- Set the incoming members' individual face direction if the effect requires it.
- Confirm the resulting order and visible top before continuing play.
Preserve ownership through composition changes
Control of a table object does not necessarily change the owner of every physical card inside it. When members leave a composition for a hand, deck, graveyard, or external zone, route each member according to the operation and its owner-specific destination. In online play, do not expose a returning private card to the other player merely to verify that the move succeeded.
If an effect temporarily combines cards owned by different players, announce that fact before building the stack. It is much easier to confirm ownership at insertion time than after the members have been reordered several times.
Handle multi-face and mode state independently
A card's selected face or runtime mode belongs to that card, not automatically to every card in the pile. Changing the visible face of the top card should not flip hidden sources or rewrite their identities. Likewise, rotating or tapping a combined object should follow the supported composition operation rather than applying an unrelated face change.
Use the inspector to verify the current face and any mode-specific value, including power, before and after a composition change. If a workflow does not preserve the intended state, stop and resolve manually rather than forcing the closest-looking layout.
Audit before resolving a leave event
Before breaking, detaching, returning, or moving a composition, review the complete member list and the destination for each role. Resolve replacement choices and owner-specific returns before clearing the visual pile. After the action, compare zone counts with the number of physical members that left.
- The number of members before and after the action balances across zones.
- The correct member remained on top or left first.
- Face-down information was not revealed unnecessarily.
- Each returned card went to the correct owner's zone.
- The action log describes the reusable operation clearly enough to review.