Skip to main content
Formal Specification

Game of the Palm (Courte Paume / Real Tennis) — Formal Specification

France · ball-team · Confidence: low

← Back to game page

Implementation Suitability

Suitability: engine-readyFidelity: discretizedGap-fills: 2
# Jeu de paume — AI-optimized specification ## General idea The original court tennis game featuring asymmetric court architecture (penthouses, wall galleries, winning openings) and a dynamic territorial state machine powered by *chasses* (chases). Points where a ball is not returned before its second bounce are suspended as territorial markers; players swap court ends to replay the contested ground, where the attacker must place the second bounce deeper than the recorded chase line to win the suspended point. ## Formal model - **Abstraction taken:** The complex asymmetric 3D hall is modeled as a 2D grid partitioned by a central net at X=0. Hazard side spans X∈[0,+14.5] m; Service side spans X∈[−14.5,0] m. Floor chase lines are discretized into 1-yard intervals (y∈{1..14} on each side). Winning openings (*Dedans*, *Grille*, *Winning Gallery*) are represented as discrete target zones with hit probabilities conditioned on agent skill and shot selection. - **Player/agent count:** 2 agents in 1v1 (Server S, Receiver R). - **Turn model:** Alternating stroke rallies with pending chase FIFO queue. ## Formal rules R1. State tracking: Match score (sets, games, current point score ∈{0,15,30,40,adv}), active server ID, side allocation, pending chase list Q=[] (max length 2), and active chase in dispute Cactive∈null∪ℝ. R2. Service: Server must hit onto the service penthouse (X∈[−14.5,0],Y∈roof); ball must roll off roof into the Hazard service box (X∈[7.0,12.0]). A fault gives a second serve; two faults award 1 point to receiver. R3. Direct winning conditions: An agent scores a point directly if: - Opponent hits into net or out of court. - Agent hits into a winning opening (*Dedans*, *Grille*, *Winning Gallery*). - Opponent fails to return ball before second floor bounce while NO chase is being played and the second bounce occurs in the Hazard hazard-chase-free zone. R4. Chase creation: If a ball's second bounce occurs on the floor in a chase-marked zone: - The exact coordinate Xbounce is recorded as a new chase c=|Xbounce|, appended to queue Q. - The score does NOT change; the point is suspended. R5. Side switch trigger: - If |Q|==2, OR if (|Q|==1 and (scoreS==40∨scoreR==40)), play pauses and players switch sides (Server becomes Receiver and vice versa). R6. Playing off chases: When players switch sides with pending chases in Q: - The first chase c=Q.pop(0) becomes Cactive. - The attacker (the player who did not lay the chase) serves/returns attempting to make the ball's second bounce land deeper than c (|X|>c). - If attacker's shot has second bounce with |X|>c: Attacker wins the point. - If attacker's shot fails or has second bounce with |X|≤c: Defender wins the point. - [gap-fill] Direct winners (net fouls, winning openings) override chase comparisons. R7. Game scoring: Standard tennis ladder: 0→15→30→40→Game. At 40−40 (deuce), an agent must win 2 consecutive points to win the game. First to 6 games wins a set. Match is best of 3 sets. ## Edge cases - Tie at the end condition: Standard deuce-advantage loop at 40-40, bounded by non-zero point outcome probabilities. - A player with no legal move: Not applicable; serving or stroke actions are always available during active play. - Repetition / cycles: The deuce loop terminates with probability 1 because each point has independent transition probabilities strictly bounded away from zero. - Simultaneous claims on the same resource or position: [gap-fill] Chase queue is strictly ordered FIFO; chases are resolved sequentially one per point. - Player elimination mid-round; turn order repair: Fixed 1v1 match structure. - Resource exhaustion (pieces, tokens, space, time): Single active ball per point; max 2 chases stored in queue Q. - Termination guarantee: Set and game scores advance monotonically based on Bernoulli point outcomes, guaranteeing match completion. ## State representation - Persistent state: Sets won (S1,S2), games won (G1,G2), current game points (P1,P2), server indicator, chase queue Q=[c1,c2]. - Per-point ephemeral state: Ball trajectory state (x,y,z,vx,vy,vz), bounce counter, Cactive, penthouse roll state. - Observable information: Public game state; all chase markers and court positions are visible. ## Action space - `serve(power, target_penthouse_x)`: Service stroke from service end. - `strike(target_x, target_y, target_z, shot_type)`: Shot types ∈{groundstroke,volley,cut_stroke,aim_dedans,aim_grille}. ## Playability notes - Single-player-vs-AI: Highly strategic 1v1 contest where AI must calculate the tactical value of laying deep chases versus attacking winning openings. - Group games (n>4): Reduces naturally to 2 agents in 1v1 singles format. - Physical-skill games: Parameterized by accuracy variances on cut-shots and target openings. - What is lost in the adaptation: The intricate acoustic dampening of the cork ball on wooden gallery roofs and the heavy wrist-strain of the asymmetric wooden racket. ## Implementation hints Medium complexity due to the chase queue state machine. Structure the engine as two nested state machines: outer machine manages chase queue and side switches (R4–R6); inner machine manages standard rally exchange. First milestone: implement rally engine and verify FIFO chase resolution logic.

Download as JSON

Download the full game corpus entry for this game as structured JSON.

Download JSON
Cite this page

Game of the Palm (Courte Paume / Real Tennis) (France). (n.d.). Games of Countries. https://gamesofcountries.com/games/fr-france/jeu-de-paume

@misc{gamesofcountries-fr-france-jeu-de-paume,
  title = {Game of the Palm (Courte Paume / Real Tennis) (France)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/fr-france/jeu-de-paume}
}