Skip to main content
Formal Specification

Bouncing Fistball — Formal Specification

Germany · ball-team · Confidence: high

← Back to game page

Implementation Suitability

Suitability: adaptation-requiredFidelity: discretizedGap-fills: 1
# Prellball — AI-optimized specification ## General idea A turn-based or real-time ticked volleyball-derivative team game on a bounded 2D court divided by a low 40 cm ribbon. Two teams of 4 agents exchange a bouncing ball. Every strike must be a downward fist/forearm drive preceded by exactly one ground bounce within the team's half. Possession sequences allow up to 3 distinct player touches before returning the ball across the ribbon. ## Formal model - **Abstraction taken:** The 3D indoor court (16 m×8 m) is discretized into a 2D planar grid with an explicit height coordinate z(t) for the ball trajectory. Real-time motion is discretized into synchronized ticks Δt=0.1 s. Physical downward fist strikes (*Prellen*) are modeled as downward impulse vectors satisfying z˙<0. - **Player/agent count:** 2 teams (A and B), each consisting of 4 agents positioned in defensive quadrants within their 8 m×8 m half. - **Turn model:** Synchronized ticks during dynamic ball flight; rally scoring with possession transitions. ## Formal rules R1. **Court & Net:** Rectangular field [−8,8]×[−4,4] meters. Center line at x=0 with ribbon height Hnet=0.4 m. Team A defends x∈[−8,0]; Team B defends x∈[0,8]. R2. **Service:** Serving agent executes `serve(target_x, target_y, power)` from behind baseline x=±8. The ball must bounce once at xbounce∈OwnHalf before crossing x=0 with height z(x=0)>0.4 m. R3. **Rally Mechanics & Bounce Constraint:** When the ball enters Team T's half: - Team T touch count is reset: touchesT←0. - The ball must bounce exactly once on the floor (z=0) within Team T's half before any agent touches it. - If the ball bounces ≥2 times, or touches outside court bounds, a fault is declared immediately. R4. **Legal Strike (*Prellen*):** An agent within reach radius Rreach=1.0 m of the ball after bounce 1 may submit `strike(target_pos, downward_angle)`. - Downward motion constraint: strike vector must satisfy θpitch<0 (must drive ball toward the floor). - Team touch counter increments: touchesT←touchesT+1. - An agent cannot execute two consecutive strikes (agentcurr≠agentprev). R5. **Passing & Attacking:** - If touchesT<3, the ball may be bounced to a teammate within the same half (satisfying 1 floor bounce before teammate contact). - On or before touchesT=3, the ball must be driven over x=0 at height z>0.4 m to land in the opposing court. R6. **Faults & Scoring:** A fault by Team T awards +1 point to the opposing team. Fault triggers: - Ball contacts ribbon (z≤0.4 at x=0). - Zero bounces or ≥2 bounces before hit. - Upward deflection (θpitch≥0). - Team touches >3. - Stepping across x=0 or touching ribbon. R7. **Match Clock:** The match runs for Tmax=12000 ticks (20 minutes total running clock). R8. [gap-fill] Tie-Breaking Rule:** If points are tied at Tmax, play enters sudden-death where the first team to establish a 2-point lead wins. ## Edge cases - Tie at the end condition: Resolved via R8 (sudden-death 2-point margin extension). - A player with no legal move: If no agent can reach the ball before its second bounce, the rally terminates naturally as a missed-ball fault. - Repetition / cycles: Bounded by maximum 3 touches per possession and fixed match clock Tmax. - Simultaneous claims on the same resource or position: If 2 teammates simultaneously attempt a strike, the agent with smaller distance to the ball executes the hit; the other is considered a non-contacting teammate. - Player elimination mid-round; turn order repair: If an agent disconnects, the remaining 3 agents cover the quadrants; team touch limits remain 3. - Resource exhaustion (pieces, tokens, space, time): Match clock monotonically decrements to 0. - Termination guarantee: why the game provably ends: Guaranteed by strictly decreasing game clock Tmax combined with discrete point increments per rally. ## State representation - **Persistent state:** Score tally (ScoreA,ScoreB), match time remaining trem, team rosters. - **Per-player state:** 2D position (xi,yi), velocity vector, stamina, last-touched boolean. - **Per-turn ephemeral state:** Ball 3D state (x,y,z,vx,vy,vz), current possession team, touch counter touches∈{0,1,2,3}, ground bounce counter. - **Observable information:** Perfect information; 3D ball coordinates, player positions, score, and clock are globally observable. ## Action space - `move(dx, dy)`: planar displacement vector with ‖𝐝‖≤vmax⋅Δt. - `strike(target_x, target_y, power)`: downward fist strike driving ball toward floor target. Precondition: agent within Rreach of ball following exactly 1 bounce. - `serve(target_x, target_y, power)`: baseline service action. ## Playability notes - Single-player-vs-AI: Natural; 1 human player controlling an individual court agent with cooperative AI teammates against an AI quad. - Group games (n>4): 8 agents reduce cleanly to a 2-agent match (1 captain per team selecting team defensive positioning and strike targets). - Physical-skill games: Downward fist strike accuracy is parameterized with Gaussian dispersion on target position scaled by agent skill. - What is lost in the adaptation: The physical impact of the heavy leather ball on the fist/forearm and physical floor dives. ## Implementation hints Discretized 3D ball physics with low computational overhead. First milestone: implement 2D parabolic ball trajectory with floor bounce damping (ez≈0.75) and verify that 3-touch sequence and 40 cm ribbon checks trigger correct point allocations.

Download as JSON

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

Download JSON
Cite this page

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

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