How to play
You complete Shifting when every card reaches the required foundation under this profile's rank, suit, direction, and access constraints. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim.
- Shifting opens from a versioned seeded position built for Unrestricted talon placement is followed by single-card rank-down rearrangement; only Kings open emptied columns before cards reach suit foundations. Its game ID, rules profile, and deal identity are stored together so restart recreates the same opening without a server request.
- Every Shifting action is checked against the current board, available material, and this defining restriction: Unrestricted talon placement is followed by single-card rank-down rearrangement; only Kings open emptied columns before cards reach suit foundations. Invalid, stale, or post-terminal actions leave the position unchanged.
- You complete Shifting when every card reaches the required foundation under this profile's rank, suit, direction, and access constraints. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim.
Strategy tips
- A practical Shifting plan is to preserve several legal continuations around Unrestricted talon placement is followed by single-card rank-down rearrangement; only Kings open emptied columns before cards reach suit foundations. Use the deterministic hint to inspect one legal action, then compare how it affects the documented objective before committing.
- A common Shifting error is to ignore the boundary rule that Unrestricted talon placement is followed by single-card rank-down rearrangement; only Kings open emptied columns before cards reach suit foundations. Undo is useful for studying that decision, while restart deliberately preserves the original seeded position.
- Near the end of Shifting, recount the remaining obligations needed until every card reaches the required foundation under this profile's rank, suit, direction, and access constraints. Check the boundary rule after every final placement or transfer because terminal status is enforced immediately.