Formal Specification
Belgian palm ball — Formal Specification
Belgium · ball-team · Confidence: low
← Back to game pageImplementation Suitability
Suitability: adaptation-requiredFidelity: discretizedGap-fills: 2
# Balle pelote — AI-optimized specification
## General idea
A traditional Belgian territory-conquest team ball game derived from outdoor *jeu de paume*. Two 5-player teams strike a hard leather ball bare-handed or with palm guards across an open paved ballodrome, using dynamic *chasses* (ground markers where dead balls are stopped) to temporarily divide the pitch and trigger end-switches to resolve territory disputes. Points follow the 15-30-40-*jeu* system, with matches won by claiming 13 or 15 games.
## Formal model
- **Abstraction taken:** The continuous flight and physical striking of the ball are discretized into a 2D court grid () with discrete ball trajectory steps and stochastic strike outcomes parameterized by agent positioning, velocity, and skill.
- **Player/agent count:** 2 teams (), each with 5 agents assigned to designated roles (Livreur, Foncier, Contre-foncier, 2 Cordiers).
- **Turn model:** Alternating delivery and real-time reactive rally exchange ticks until the point is scored or a chasse is marked.
## Formal rules
R1. **Court Structure:**
- The court is divided into -side (Petit Jeu, delivery side) and -side (Grand Jeu, receiving side) along a lateral short-boundary line and back baselines .
R2. **Service Phase:**
- The active server (*livreur*) delivers the ball from the delivery box.
- The ball must clear and land within the lateral boundaries of the Grand Jeu; failure immediately awards points to the receiving team.
R3. **Rally Exchange:**
- Agents move on a 2D discrete grid to intercept the incoming ball.
- Legal returns require striking the ball on the fly or after exactly 1 ground bounce.
- Striking the ball past the opponent's back baseline on the fly (*outre*) scores an immediate points.
- Missing a return or hitting out-of-bounds commits a fault, awarding points to the opponent.
R4. **Chasse Marking:**
- If a ball is stopped by an agent after 2 bounces in bounds, or rolls over a side boundary after 1 bounce, a *chasse* marker is recorded at that longitudinal position.
- At most 2 active chasses can be stored in the pending queue .
R5. **Side-Switch & Chasse Resolution:**
- When , or when and either team's score , teams switch ends.
- The next point(s) are played to resolve .
- If the attacking team drives the ball past , the attacking team wins points; otherwise, the defending team wins points.
- is then popped from the queue.
R6. **Game and Match Progression:**
- Scoring within a game advances: .
- [gap-fill] At 40–40 (deuce / *deux à deux*), standard advantage play applies: two consecutive points won are required to claim the *jeu*.
- First team to win 13 games wins the match.
## Edge cases
- **Tie at the end condition:** Not applicable — games are discrete, and the first team to reach 13 games wins immediately.
- **A player with no legal move:** Not applicable — during a rally, an agent whose position cannot reach the ball simply allows the ball to land or be played by a teammate.
- **Repetition / cycles:** Impossible — every point concludes either with an immediate score increment or a marked chasse, and games monotonically increment toward 13.
- **Simultaneous claims on the same resource or position:** When two teammates attempt to strike the same ball on the same tick, the agent with the higher priority role (Foncier > Contre-foncier > Cordier) executes the strike.
- **Player elimination mid-round; turn order repair:** [gap-fill] If an agent is disqualified or injured, the team plays down one player (4 on field) with existing role assignments redistributed, or a designated bench substitute enters at the start of the next service.
- **Resource exhaustion (pieces, tokens, space, time):** Not applicable — ball is persistent and replenished after each rally; court space is fixed.
- **Termination guarantee:** Each point resolves in finite ticks; each game terminates upon reaching the win threshold; matches terminate when one team reaches 13 games.
## State representation
- **Persistent state:** Team scores (), current game points (), side alignment (), pending chasse queue of coordinate floats.
- **Per-tick state:** Ball 3D vector , bounce count , agent coordinates and stamina vectors.
- **Observable information:** Fully observable to all agents.
## Action space
- `serve(power, target_x, target_y)`: Executed only by Livreur during service phase.
- `move(dx, dy)`: Grid displacement per simulation tick.
- `strike(elevation, direction, power)`: Executed when ball is within strike radius ().
## Playability notes
- **Single-player-vs-AI:** Natural by assigning 9 AI agents to the remaining positions and letting the human agent control the server/foncier.
- **Group games (n>4):** Reduces to a 2-agent model by having 1 agent per team control all 5 field positions via tactical positional macros.
- **Physical-skill games:** Ball trajectory and hit success modeled via: .
- **What is lost in the adaptation:** The physical sting of the dense leather ball on bare skin, cobblestone bounce irregularities, and the vibrant crowd atmosphere of the village ballodrome.
## Implementation hints
- Implement the *chasse* state queue and side-switching logic as a discrete sub-state machine before integrating the continuous physics rally resolver.
- Discretize the court into a grid for spatial pathfinding.
- Suggested first milestone: Build the game-scoring and chasse-tracking state engine with mock binary point outcomes.
Download as JSON
Download the full game corpus entry for this game as structured JSON.
Download JSONCite this page
Belgian palm ball (Belgium). (n.d.). Games of Countries. https://gamesofcountries.com/games/be-belgium/balle-pelote
@misc{gamesofcountries-be-belgium-balle-pelote,
title = {Belgian palm ball (Belgium)},
year = {n.d.},
publisher = {Games of Countries},
url = {https://gamesofcountries.com/games/be-belgium/balle-pelote}
}