Put goals in the goals #44

Closed
opened 2026-10-17 20:41:11 +00:00 by sermuns · 1 comment
Owner
 2  man_made=soccer_goal

Two mapped goals, on the campus pitches, plus leisure=pitch with
sport=soccer on 12 ways and sport=soccer;basketball on one.

A goal is two posts and a crossbar and it is the only piece of campus furniture
with a scoring rule attached to it. A thrown object that hits the frame scores;
one that misses does not. That is a rule, not a mesh.

Small, but it is the smallest complete game in the campus: walk to a pitch,
press one key, watch where it lands. Pairs with the pitch-colouring issue so the
pitch reads as a pitch.


Related

  • #32 the pitches the goals stand on
  • #33 the same modelling problem
  • #11 the sibling scored throw
  • #10 the sibling mechanic
``` 2 man_made=soccer_goal ``` Two mapped goals, on the campus pitches, plus `leisure=pitch` with `sport=soccer` on 12 ways and `sport=soccer;basketball` on one. A goal is two posts and a crossbar and it is the only piece of campus furniture with a scoring rule attached to it. A thrown object that hits the frame scores; one that misses does not. That is a rule, not a mesh. Small, but it is the smallest complete game in the campus: walk to a pitch, press one key, watch where it lands. Pairs with the pitch-colouring issue so the pitch reads as a pitch. --- **Related** - #32 the pitches the goals stand on - #33 the same modelling problem - #11 the sibling scored throw - #10 the sibling mechanic
sermuns added this to the Play milestone 2026-10-19 22:18:53 +00:00
Author
Owner

The goal is already the right shape for a physics engine: a frame, and a rule
about what hit it.

With #112's thrown body, the football is a body with a mass and a
restitution, and the goal is two posts and a crossbar that it can hit. The
rule does not change — an object that hits the frame scores, one that misses
does not — but it stops being a special case of the throw and becomes the
normal consequence of the throw.

The posts are also a wall, and that is the interesting part. A ball that
clips the post and spins out is a different outcome from one that goes in,
and it is the kind of difference the players will actually argue about. A
frame that is a wall rather than a trigger plane gives that for free.

Where the ball lives is the same question the disc asks: the ball is
server-authoritative, so its position travels on the wire, and the goal
itself is static geometry that the collision layer carries.

Related: #110 the physics engine, #112 the shared thrown body.

The goal is already the right shape for a physics engine: a frame, and a rule about what hit it. With #112's thrown body, the football is a body with a mass and a restitution, and the goal is two posts and a crossbar that it can hit. The rule does not change — an object that hits the frame scores, one that misses does not — but it stops being a special case of the throw and becomes the normal consequence of the throw. The posts are also a wall, and that is the interesting part. A ball that clips the post and spins out is a different outcome from one that goes in, and it is the kind of difference the players will actually argue about. A frame that is a wall rather than a trigger plane gives that for free. Where the ball lives is the same question the disc asks: the ball is server-authoritative, so its position travels on the wire, and the goal itself is static geometry that the collision layer carries. Related: #110 the physics engine, #112 the shared thrown body.
Sign in to join this conversation.
No description provided.