FLOW — Option 1 | OUTSIDE CURL, LIFT UP, CORNER EXIT
ONL five-out default: Pass → screen the adjacent OFF-BALL teammate opposite the pass → read the defense → keep the floor moving. Players are interchangeable by spot.
- Pass: 1 at TOP passes to 3 at RIGHT WING (the player now holding the ball).
- Off-ball screen: 1 screens for adjacent 2 at LEFT WING—not the receiver 3. The arriving player 1 SETS the screen.
- OUTSIDE CURL: 2 travels around the OUTER/HIGH SIDE of 1's screen, away from the paint first, then curls toward the rim while keeping eyes on 3 for a direct layup pass. Do NOT run inside/below 1's screen.
- Continuous upward fills: As the rim cut develops, 1 LIFTS BACK TO THE EMPTY TOP position. Meanwhile 4 LIFTS UP from LEFT CORNER to the vacant LEFT WING left by 2. Off-ball perimeter players fill adjacent empty spots UP, AWAY FROM THE CORNER. They never fill down into a corner.
- Corner exit when denied: If 3 cannot pass to 2 for the layup, 2 EXITS the paint through the now-empty LEFT CORNER vacated by 4. Keep movement continuous; no player should occupy the cutter's exit spot.
Final alignment on denied layup: 1 top, 4 left wing, 2 left corner, 3 right wing with ball, 5 right corner.
Other FLOW defensive reads: vs under, screen receiver LIFTS to perimeter; vs switch, screen receiver LIFTS and screener SLIPS. The pass-from-a-corner BASELINE-CUT exception remains unchanged.
Teaching: Screens are screens, not generic cuts. Basket cutters leave through vacant corners; perimeter off-ball teammates move UP, not toward corners. The drawn animation illustrates the denied-pass/corner-exit continuation; the entry-pass layup is the earlier read.
COACH EDITING NOTE (not a player instruction): This saved animation contains manually verified ONL court geometry. The app's automatic script compiler may change its screening locations, timing, or routes. Keep the currently saved animation as the visual source of truth. If editing the PlayScript, re-check each rendered frame against this play's written execution BEFORE publishing changes. Do not treat a warning-free compile as proof of tactical accuracy.