How to play
You complete Box Kite 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.
- Box Kite opens from a versioned seeded position built for Twelve spokes build one card up or down by rank with wrapping around paired Ace-up and King-down suit foundations; the initial deal leaves no redeal. Its game ID, rules profile, and deal identity are stored together so restart recreates the same opening without a server request.
- Every Box Kite action is checked against the current board, available material, and this defining restriction: Twelve spokes build one card up or down by rank with wrapping around paired Ace-up and King-down suit foundations; the initial deal leaves no redeal. Invalid, stale, or post-terminal actions leave the position unchanged.
- You complete Box Kite 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 Box Kite plan is to preserve several legal continuations around Twelve spokes build one card up or down by rank with wrapping around paired Ace-up and King-down suit foundations; the initial deal leaves no redeal. Use the deterministic hint to inspect one legal action, then compare how it affects the documented objective before committing.
- A common Box Kite error is to ignore the boundary rule that Twelve spokes build one card up or down by rank with wrapping around paired Ace-up and King-down suit foundations; the initial deal leaves no redeal. Undo is useful for studying that decision, while restart deliberately preserves the original seeded position.
- Near the end of Box Kite, 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.