Skip to main content
Formal Specification

Fistball — Formal Specification

Germany · ball-team · Confidence: high

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 1
# Faustball — AI-optimized specification ## General idea A dynamic 5v5 team court game played on a 50 m×20 m grass pitch divided by a 2.0-meter-high center ribbon. Agents exchange a leather ball exclusively using fist or forearm strikes. Unlike volleyball, the ball is legally allowed to bounce once on the grass between touches, and teams execute a three-touch progression (Reception → Setting → Spiking) to create downward attacks past opponent defenders. ## Formal model - **Abstraction taken:** The 3D outdoor field [−25,25]×[−10,10] m with net at x=0 (Hnet=2.0 m) is discretized into synchronized real-time ticks Δt=0.1 s. Ball motion follows 3D ballistic trajectory with restitution egrass≈0.60. Player movement is discretized into continuous velocity vectors with sprint acceleration bounds. - **Player/agent count:** 2 teams (A and B), 5 agents per side arranged in offensive and defensive zones. - **Turn model:** Synchronized ticks during active rally; set scoring structure. ## Formal rules R1. **Court Boundaries:** Field dimensions [−25,25]×[−10,10] meters. Team A defends x∈[−25,0]; Team B defends x∈[0,25]. Center ribbon height Hnet=2.0 m at x=0. R2. **Service Action:** Serving agent from behind the 3-meter line executes `serve(target_x, target_y, power)`. The ball must clear x=0 at height z>2.0 m and land within the opponent's boundary. R3. **Rally Phase & Legal Hit:** - Only single fist (*Faust*) or single forearm (*Unterarm*) strikes are legal. - Two-handed contact or touching with lower body is an immediate fault. - An agent within Rreach=1.2 m of the ball may submit action `hit(target_x, target_y, power, strike_type)`. R4. **Ground Bounce Rules:** - Within each team possession, the ball may bounce on the ground (z=0) at most **once before each touch**. - If the ball bounces ≥2 times before a touch, the possession ends in a fault. R5. **Three-Touch Limit:** A team must return the ball across x=0 at height z>2.0 m in at most 3 contacts. No individual agent may touch the ball twice within the same possession sequence. R6. **Fault Resolution & Scoring:** A fault by Team T immediately awards +1 point to the opposing team. Fault conditions: - Ball touches ribbon or passes beneath z≤2.0 m at x=0. - Ball lands outside court boundary lines. - ≥2 ground bounces before contact. - Team touch count >3. - Agent contacts ribbon or steps over x=0. R7. [gap-fill] Set & Match Structure:** A set is won by the first team to reach 11 points with a minimum 2-point lead (e.g. 11–9, 13–11); if score reaches 14–14, the team scoring the 15th point wins immediately (15-point hard ceiling). A standard match is best-of-5 sets. ## Edge cases - Tie at the end condition: Sets reaching 14–14 are decided by sudden-death at 15 points per R7; matches tied 2–2 sets play a deciding 5th set. - A player with no legal move: If no defender can reach the ball before its second bounce, the rally terminates automatically as an unreturned ball fault. - Repetition / cycles: Bounded by 3 touches per rally and finite point increments toward the 11/15 set target. - Simultaneous claims on the same resource or position: If two teammates attempt a hit on the same tick, the agent with smaller Euclidean distance to the ball is assigned contact; the other agent incurs a recovery cooldown. - Player elimination mid-round; turn order repair: If an agent disconnects, the remaining 4 agents reposition to cover zones without altering team touch rules. - Resource exhaustion (pieces, tokens, space, time): Not applicable; ball is reset to server at every point. - Termination guarantee: why the game provably ends: Guaranteed because each rally concludes in finite time with a point awarded to one team, and sets terminate at the latest at point 15. ## State representation - **Persistent state:** Set scores (SetsA,SetsB), current set points (PtsA,PtsB), server ID, team rosters. - **Per-player state:** 2D position (xi,yi), velocity vector, stamina, cooldown timer, role (`attacker`, `setter`, `defender`). - **Per-turn ephemeral state:** Ball 3D state (x,y,z,vx,vy,vz), possessing team ID, touch counter touches∈{0,1,2,3}, bounce count since last touch. - **Observable information:** Perfect information; 3D ball coordinates, agent positions, set scores, and fault logs are common knowledge. ## Action space - `move(dx, dy)`: horizontal translation vector satisfying ‖𝐝‖≤vmax⋅Δt. - `hit(target_x, target_y, power, strike_type)`: - `target_x, target_y`: intended landing/target coordinates. - `power` ∈[0.0,1.0]. - `strike_type` ∈{bump_pass,fist_set,spike}. Precondition: agent within Rreach of the ball with bounce count ≤1. - `serve(target_x, target_y, power)`: service strike from behind service line. ## Playability notes - Single-player-vs-AI: Natural; 1 human user controlling the lead spiker with 4 cooperative AI agents against an AI team. - Group games (n>4): 10 agents reduce cleanly to a 2-agent match (1 tactical coach per team issuing high-level positional and set commands). - Physical-skill games: Spiking power and dive-save execution are parameterized with Gaussian angle error scaled by agent skill. - What is lost in the adaptation: The tactile stinging sensation of wet leather on the forearm and grass-sliding friction dynamics. ## Implementation hints Standard 3D sports simulation framework. Milestone 1: implement parabolic ball flight with grass bounce damping and ribbon collision detection, then verify 3-touch rally progression and 11-point set evaluation.

Download as JSON

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

Download JSON
Cite this page

Fistball (Germany). (n.d.). Games of Countries. https://gamesofcountries.com/games/de-germany/faustball

@misc{gamesofcountries-de-germany-faustball,
  title = {Fistball (Germany)},
  year = {n.d.},
  publisher = {Games of Countries},
  url = {https://gamesofcountries.com/games/de-germany/faustball}
}