Complete Napoleon when every card reaches a legal foundation under its suit, base, direction, capacity and source restrictions. The engine checks the full card partition and terminal rule rather than a visual approximation.
Your unfinished game is saved only in this browser.
Complete Napoleon when every card reaches a legal foundation under its suit, base, direction, capacity and source restrictions. The engine checks the full card partition and terminal rule rather than a visual approximation.
Complete guide
Napoleon uses the independently implemented Napoleon PySolFC 3.6.1 fixed rules v1 profile (R914). Napoleon is an independently versioned browser card game defined by this source-audited rule: Napoleon uses the shared-direction wrapping suit system with two independently depot-gated cells instead of Der kleine Napoleon's single common-gated cell.
Napoleon reconstructs its exact pile counts, concealed-card mask, seeded foundations and stock remainder from the route seed. No independent stock action remains after the sourced opening. Restart reproduces the same deal locally without a network request.
A move is accepted only when its source is exposed, its packet satisfies suit straight up down wrap, and its destination satisfies suit straight up down wrap plus the any vacancy gate. Invalid, stale, non-finite and post-terminal actions do not mutate state.
Complete Napoleon when every card reaches a legal foundation under its suit, base, direction, capacity and source restrictions. The engine checks the full card partition and terminal rule rather than a visual approximation. Before the final commitment in Napoleon, count every live card, locked source and legal destination. Confirm that every card reaches a legal foundation under its suit, base, direction, capacity and source restrictions.
In Napoleon, compare the next forced exposure with the mobility lost by the current move. Napoleon uses the shared-direction wrapping suit system with two independently depot-gated cells instead of Der kleine Napoleon's single common-gated cell. The most common Napoleon error is moving a legal packet without checking its destination-specific size gate; the move may be legal in a neighbouring family while being rejected or strategically fatal in this exact profile.
Napoleon has its own engine ID, save namespace and rules fingerprint because Napoleon uses the shared-direction wrapping suit system with two independently depot-gated cells instead of Der kleine Napoleon's single common-gated cell.
Check source exposure, packet integrity, the exact vacancy gate and the next forced stock or reserve consequence; then compare the next forced exposure with the mobility lost by the current move.
No. The seed guarantees reproducibility and the engine guarantees legal transitions, but the catalog does not make an unsupported claim that every shuffled deal is solvable.