Foursuit! Dev Diary

Foursuit! Beta 0.1 — Milestone Notes

Early May 2026

• Initial concept formed.
  Development began as a “War”-like standard-deck card game with fantasy elements. The early goal was simple: use a normal deck of cards as the engine for a browser game with more agency than pure card-flip randomness.


• 3×3 field became the core board.
  Cards 2–10 became the main battlefield, arranged into a hidden 3×3 grid. The reveal-and-compare structure gave the game its basic rhythm: place, reveal, compare, score.


• Scoring shifted toward surviving total value.
  The game settled on scoring by survivor total difference instead of simply counting won squares. This became one of the most important design choices, because it made card value and placement matter more than raw square count.


• Royal powers were defined.
  Jack, Queen, King, and Ace became limited tactical powers rather than ordinary high cards. Their roles settled into: Jack claims a tie, Queen restores a fallen card, King cancels an opposing survivor, and Ace swaps adjacent opposing cards.


• The Royal Parlay became the main tactical layer.
  The royal phase was refined into a one-royal commitment system. Matching royals draw, higher royals win, the winning royal resolves, and the lower royal is blocked. This gave the game its main moment of post-reveal decision-making.


• The Heir / Bloodline rule was locked in.
  The final unused royal can never be spent. In Classic this became the Heir; in Fantasy it became the Bloodline. This added needed pressure to royal use.


• Fantasy factions took shape.
  The four suits became four fantasy factions: Lifeblood Order, Starshine Druids, Rockbreaker Clans, and Earthworker Tribes. This gave the game a second identity beyond the plain card-table version.


• Classic mode was introduced, then became central.
  Classic first appeared as a visual alternative to the fantasy presentation, but after testing and reflection it became the main default mode. The fantasy version remained as a parallel presentation rather than the only identity of the game.


• The Foursuit! / Loresuit! split was chosen.
  The base game became Foursuit!, with the tagline “Four suits. Two colors. One deck.” The fantasy-facing version became Loresuit!, with the tagline “Four factions. Two sides. One crown.”


• Game modes expanded.
  The game grew from a single-match format into three main modes: Single / Battle, Trifecta / Campaign, and Colors / Allies. These modes reused the same core rules while changing the scope and pressure of play.


• Old themed skin ideas were removed.
  Earlier visual skin experiments, including retro-style palette options and hidden unlock-style presentation choices, were cut from the beta path. The game moved toward a cleaner Foursuit / Loresuit identity instead.


• Computer royal logic was improved.
  The Computer initially made royal choices that could feel arbitrary, such as using a powerful royal for a tiny gain. Difficulty settings and threshold-based royal evaluation were added so the Computer would use royals more intentionally.


• Difficulty options were added.
  Easy, Medium, and Hard were added as a clean way to tune Computer royal judgment. The goal was not to create a perfect opponent, but to make the Computer feel fair, readable, and less random.


• House Rules were added for real-card play.(*Work in progress)
  The browser game remained the main rules engine, but a downloadable House Rules version was added for table play with a real deck. The tabletop version preserves the spirit of the game while adjusting Royal Parlay timing for two human players.


• Sound was added through a custom soundboard workflow.
  A native browser sound system was added using named sound codes from a custom soundboard tool. This made it easier to assign consistent sounds to menu actions, cards, modals, errors, locking, showing, and advancing.


• Major UI flow fixes were made.
  CLEAR was added so players could reset their field before reveal. Wrap was added so players could read the final report before moving to the end screen. Score boxes, stat boxes, and screen centering went through several layout passes.


• A tutorial was added.
  The Rules section gained a tutorial explaining the field, reveal, royal powers, Royal Parlay, scoring, and the Heir / Bloodline rule. The tutorial was added after testing showed that the rules existed, but the strategy needed clearer teaching.


• Social and web presence were secured.
  The domain playfoursuit.com was secured, the X account x.com/foursuit was secured, and the project was prepared for static hosting through GitHub Pages.


• Dev blog added.
  A static dev blog was planned at blog.playfoursuit.com as a place for milestone notes, development updates, and longer explanations that do not belong in the in-game splash screen.


• Beta 0.1 reached public-test readiness.
  By Beta 0.1, Foursuit! included Classic and Fantasy presentations, three modes, three difficulties, Royal Parlay, Heir/Bloodline, sound, tutorial, House Rules download, announcement modal, and a working static site path.