6ce52a6e85aeb4734f25b3cf1e62f30325e38f58
The laser look came from carrying the AIMING picture unchanged into the flight. While you pull, a bright saturated line spanning you to the target is exactly right — it is the information you are deciding on. Once fired it is spent, and a projectile drawing its own future in a continuous saturated line from itself to what it is about to hit is the visual definition of a targeting beam. No real ball shows where it is going. So a fired band now desaturates toward dust, collapses, and shrinks to a short streak. TUNE.shotTail picks which side of the ball that streak sits on: 0 a WAKE ahead of it, dissolving — your erase idea, beam cut down to a wisp 1 a TAIL behind it, nothing ahead at all — conventional projectile language The shadow follows the same slice, because "nothing ahead" has to include the ground or it still gives the future away. The target mark fades with it: a mark still burning on the shambler is the other half of the laser. Both leave the aiming band untouched. Built the collapse squared first and it was wrong — both variants were gone by a third of the flight, which is not "less like a laser", it is no streak at all, and the strobing at release is what this trail exists to prevent. Linear now. The SHORT SLICE is what kills the beam; the fade only has to make sure nothing is still burning when the ball lands. Flip it live on the phone: T panel, shotTail, type 0 or 1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Languages
JavaScript
75.2%
Python
15.8%
HTML
7.3%
Shell
1.4%
Swift
0.2%