You complete Fission 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.
Your unfinished game is saved only in this browser.
You complete Fission 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.
Complete guide
Fission uses the independently implemented Fission PySolFC 3.6.1 rules profile v1 profile (R399). Fission is a complete deterministic browser game whose distinct rules centre on Removing a top card splits its seven-card source at that depth; resulting singleton fragments become wrapping same-suit foundations while four suit reserves must not self-lock.
Fission opens from a versioned seeded position built for Removing a top card splits its seven-card source at that depth; resulting singleton fragments become wrapping same-suit foundations while four suit reserves must not self-lock. Its game ID, rules profile, and deal identity are stored together so restart recreates the same opening without a server request.
Every Fission action is checked against the current board, available material, and this defining restriction: Removing a top card splits its seven-card source at that depth; resulting singleton fragments become wrapping same-suit foundations while four suit reserves must not self-lock. Invalid, stale, or post-terminal actions leave the position unchanged.
You complete Fission 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. Near the end of Fission, 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.
A practical Fission plan is to preserve several legal continuations around Removing a top card splits its seven-card source at that depth; resulting singleton fragments become wrapping same-suit foundations while four suit reserves must not self-lock. Use the deterministic hint to inspect one legal action, then compare how it affects the documented objective before committing. A common Fission error is to ignore the boundary rule that Removing a top card splits its seven-card source at that depth; resulting singleton fragments become wrapping same-suit foundations while four suit reserves must not self-lock. Undo is useful for studying that decision, while restart deliberately preserves the original seeded position.
Fission has its own runtime and save identity because its rules require Removing a top card splits its seven-card source at that depth; resulting singleton fragments become wrapping same-suit foundations while four suit reserves must not self-lock.
Removing a top card splits its seven-card source at that depth; resulting singleton fragments become wrapping same-suit foundations while four suit reserves must not self-lock.
Fission 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.
