You complete Matrimony when every card reaches the foundation target while the profile's access, packet, and sequence restrictions remain satisfied. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim.
Your unfinished game is saved only in this browser.
You complete Matrimony when every card reaches the foundation target while the profile's access, packet, and sequence restrictions remain satisfied. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim.
Complete guide
Matrimony uses the independently implemented Matrimony PySolFC 3.6.1 fixed rules profile v1 profile (R492). Matrimony is a complete deterministic browser game whose distinct rules centre on Jack-down-to-Queen and Queen-up-to-Jack suit foundations run in opposite wrapping directions; sixteen tableau piles are individually recycled in a fixed bottom-right-to-top-left schedule.
Matrimony opens from a versioned seeded position built for Jack-down-to-Queen and Queen-up-to-Jack suit foundations run in opposite wrapping directions; sixteen tableau piles are individually recycled in a fixed bottom-right-to-top-left schedule. Its game ID, rules profile, and deal identity are stored together so restart recreates the same opening without a server request.
Every Matrimony action is checked against the current board, available material, and this defining restriction: Jack-down-to-Queen and Queen-up-to-Jack suit foundations run in opposite wrapping directions; sixteen tableau piles are individually recycled in a fixed bottom-right-to-top-left schedule. Invalid, stale, or post-terminal actions leave the position unchanged.
You complete Matrimony when every card reaches the foundation target while the profile's access, packet, and sequence restrictions remain satisfied. The engine evaluates the full position rather than relying on a visual shortcut or an unsupported solvability claim. Near the end of Matrimony, recount the remaining obligations needed until every card reaches the foundation target while the profile's access, packet, and sequence restrictions remain satisfied. Check the boundary rule after every final placement or transfer because terminal status is enforced immediately.
A practical Matrimony plan is to preserve several legal continuations around Jack-down-to-Queen and Queen-up-to-Jack suit foundations run in opposite wrapping directions; sixteen tableau piles are individually recycled in a fixed bottom-right-to-top-left schedule. Use the deterministic hint to inspect one legal action, then compare how it affects the documented objective before committing. A common Matrimony error is to ignore the boundary rule that Jack-down-to-Queen and Queen-up-to-Jack suit foundations run in opposite wrapping directions; sixteen tableau piles are individually recycled in a fixed bottom-right-to-top-left schedule. Undo is useful for studying that decision, while restart deliberately preserves the original seeded position.
Matrimony has its own runtime and save identity because its rules require Jack-down-to-Queen and Queen-up-to-Jack suit foundations run in opposite wrapping directions; sixteen tableau piles are individually recycled in a fixed bottom-right-to-top-left schedule.
Jack-down-to-Queen and Queen-up-to-Jack suit foundations run in opposite wrapping directions; sixteen tableau piles are individually recycled in a fixed bottom-right-to-top-left schedule.
Matrimony stores its game ID, rules version, and seeded deal identity. Those values recreate the same opening locally without promising that the position is forced or winnable.
