Oliver, three notes; two of them are here.
"when the opponent serves the player does not stand at the baseline - but
that's how it should be." setupPoint's receiving marks sat over a metre
INSIDE the court on both sides (22.5 near, 1.2 far) — where you stand to
attack a second serve, not where you wait for a first one. They mirror the
server's depth now, in the one line every serving mode shares.
"when serving results in an out there should be a second service... the
umpire should announce 2nd service and the player must get another chance."
True in tennis mode since forever and absent everywhere else: the duel, the
match and the death match had no service rule at all, so a serve long or
into the net was judged as an ordinary ground stroke — a point, and in the
match a point costs blood. The out branch of onBounce's interlude block
routes a serve to fault() instead, so the second serve, the HUD line, the
umpire and the double fault all come for free.
Three things it dragged out with it:
- fault()'s double-fault branch called pointTo — TENNIS scoring — which in
an interlude banks a number and skips the mode that owns the court. It
goes through resolveInterlude there now. Nothing had ever reached that
line from a duel or a match, because those modes could not fault.
- startDuel never reset G.serveNum: harmless while a duel could not fault,
the next duel's death loop the moment it can.
- the match puts the body back on its receiving mark for the second serve
(placeReceiver, split out of matchReady, which resets the serve number).
"Fault. Second service." is one voiceSeq — a second voice() call would be
dropped, one man one microphone. New recording via the usual say/afconvert.
The service BOX is still not enforced in the match, deliberately: this is
strictly more forgiving than what shipped. The lob gesture is OPEN 14.
4 new tests, 110 pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wuwiandClaude Opus 5
6e07dc74bb