Ryan Weathers lost nine pounds - and then a no-hitter and game he deserved to win

Ryan Weathers' near-miss no-hitter at Camden Yards carries real DFS weight for Yankees stacks and contrarian pitching pivots. When a starter flirts with a no-hitter—even one that doesn't materialize into a win—it signals elite stuff and command on that particular slate, which directly influences how the optimizer models his ceiling and ownership. The turbulent two weeks leading into this outing (including a nine-pound weight fluctuation) add noise to projection stability. What matters for DFS construction: Weathers proved his arm was elite-tier that night despite external circumstances, which changes how you value Yankees hitters in games where he's on the mound and how you build leverage against chalky pitcher ownership.

The no-hitter attempt itself is a slate-level read. Camden Yards is a hitter's park, yet Weathers neutralized it completely. That performance suggests his stuff was playing up—command-driven outings like this often correlate to lower opponent run totals, which compresses game totals and shifts stack construction away from the opposing team's core order and toward secondary bats or the Orioles' bench mix. If Weathers' velocity, spin, or K-rate spiked in that outing, the optimizer would flag it as a ceiling signal for future matchups, even though he didn't earn the win this time.

For DFS users building Yankees lineups in Weathers' next start, the angle isn't "he threw a no-hitter, so he's locked in"—it's verifying whether the stuff that showed up at Camden Yards is repeatable and checking ownership trends against that confirmation. Late swaps become live if Weathers is scheduled in a high-total game; if ownership stays low due to his recent turbulence, contrarian GPP builders have an opening. Re-examine his pitching matchup and implied totals for the next slate, and cross-reference any changes in his role or workload that the two-week window might have reset.