Jump to content

Bleeding Bills Blue

Community Member
  • Posts

    11,379
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bleeding Bills Blue's Achievements

All Pro

All Pro (7/8)

3.9k

Reputation

  1. Knox is also wide open. You could make an argument they probably score on a throw to cooks too since its cooks + blocker vs. 1 defender, since 29 and 22 both chased keon. Pretty good example of when the rush and the coverage don't match up. My GUESS is one of 29/22 has cooks in motion - and the other has keon. They ended up both chasing keon thinking the other takes cooks.
  2. I posted elsewhere but: LAC - 8-4 - PHI, @KC, @DAL, HOU, @DEN - Absolutely brutal schedule - 10-7? Maybe? IND - 8-4 - @JAX, @SEA, SF, JAX, @HOU - Another tough slate - Also 10-7. JAX - 8-4 - IND, NYJ, @DEN, @IND, Tenn - Couple easy home games, 3 tough games - 11-6 best case which would probably take the division HOU - 7-5 - @KC, ARI, LVR, @LAC, IND - Couple easier games at home, but 3 tough games - 10-7 best case - indy week 18 might be win and in KC - 6-6 -HOU, LAC, @TEN, DEN, @LVR - Easy road games, and 3 teams they can beat at home - I'd guess 10-7 and if the loss is to denver they're very much in the mix. BAL - 6-6 - PIT, @CIN, NE, @GB, @PIT - 3 wins would get them to 9-8 PIT - 6-6 - @BAL, MIA, @DET, @CLE, BAL - Could see them splitting and both finishing 9-8, another interesting week 18 scenario.
  3. The primary competition in WC - not going to get into tiebreakers because i think its too early. LAC - 8-4 - PHI, @KC, @DAL, HOU, @DEN - Absolutely brutal schedule - 10-7? Maybe? IND - 8-4 - @JAX, @SEA, SF, JAX, @HOU - Another tough slate - Also 10-7. JAX - 8-4 - IND, NYJ, @DEN, @IND, Tenn - Couple easy home games, 3 tough games - 11-6 best case which would probably take the division HOU - 7-5 - @KC, ARI, LVR, @LAC, IND - Couple easier games at home, but 3 tough games - 10-7 best case - indy week 18 might be win and in KC - 6-6 -HOU, LAC, @TEN, DEN, @LVR - Easy road games, and 3 teams they can beat at home - I'd guess 10-7 and if the loss is to denver they're very much in the mix. BAL - 6-6 - PIT, @CIN, NE, @GB, @PIT - 3 wins would get them to 9-8 PIT - 6-6 - @BAL, MIA, @DET, @CLE, BAL - Could see them splitting and both finishing 9-8, another interesting week 18 scenario. Based on this - Buffalo is probably the 5 seed if they go 3-2 the rest of the way. It will depend on who wins the AFC South - but if there's an 11-6 team, the other 2 are probably 10-7. I don't see any of the other 3 going on a 5-0 run to get to 11 wins, and we have tiebreakers over all of them anyway. So I think the ideal scenario would be BAL losing @CIN, and PIT losing @DET and @BAL. Week 18 game would be for the division as they'd both finish 9-8 and Pittsburgh would take it on divisional record. I would rather play a team we handily beat than a team that trucked us in week 1 - injured lamar is still more dynamic than rodgers.
  4. Dolphins had a few extra days against Buffalo, and Falcons off the bye week.
  5. A cheap depth WR who can play special teams. He shouldn't be playing this much, and ideally there are 5 options ahead of him in 2026. I also don't mind bringing in competition from a similar player. At the same time - good blocks should earn you some routes too. Shavers cap hit next year is 1M, but there's no shortage of similar special teams players who might offer a more rounded player offensively. These types of Hollins guys are always pretty available in the 1-2M AAV range, and I would suggest bringing one in to compete for that back of the roster spot.
  6. It was Gabe before that. "Why does gabe play more than sanders and brown?" was frequently a point of contention and it was blocking back then.
  7. If they're going to show 2 high looks, run at them until they change it. We aren't fast enough to attack the boundary through the air, but if they do - there needs to be an element of misdirection like a play action, a screen, a double move, etc. The outside leverage screen isn't working that well these days.
  8. At the time, many mock drafts had both jefferson and aiyuk off the board. So we were getting mocked Higgins and Pittman in the 1st. Both turned out to be good players though so i guess it would have worked out. I think the challenge here is that only buffalo gets to use hindsight to know what JJ is pre-draft, not the lions or giants who picked busts at 3 or 4.
  9. When you get called for phantom holds all season long you tend to let go at that point to try to not get called.
  10. Latu was elevated as a 3rd tight end in case someone is injured, and to play special teams. Most 3rd tight ends do some combo of that like Morris did for Buffalo for a couple of years, we just use Hawes more because he's such an impact blocker and kincaids missed so much time this year.
  11. Doubt ur getting a 1st for a WR with one cheap year left, who's never hit 1000 yards, and was suspended for a really bad DUI. I'd say best case you're looking at the 3rd for pickens, but probably less. And paying him closer to 20.
  12. Game reminds me too much of Zach Wilson that its hard to see him being successful. To be fair... the trade was not executed during the draft. They traded for diggs before the draft, not knowing who would be available at the pick. So to say they didn't see value in a player they didn't know would be available in their draft slot is a bit of a stretch.
  13. Wildcards can and do catch fire come January. Brady's Bucs were 7-5, losers of 3 of 4, and got blown out 38-3 at home by New Orleans before going on their run. Helped playing a 7-9 division winner with a backup QB in the first round, but that's the kind of thing that happens in the NFL. A Nix/Jones/Maye injury and suddenly the favorites aren't so favorite. Just going through their playoff run and its so strange... Washington - Heinicke in the playoffs - played the best game of his life with no run game and got them pretty close. TB was a 10 point favorite though and Washington kind of sucked New Orleans revenge game - 21 points off turnovers, and lived off some short fields. Packers - The scotty miller TD comes to mind as the difference in a 5 point game. Ball at midfield with :28 left in the half and somehow they get a 40 yard TD pass with 8 seconds left in the half. Another short field turnover/TD to open the 3rd quarter and it was 28-10. Brady threw 2 picks in the 4th quarter and GB made the strange decision to kick a FG down 8 from the 8 yard line. They never touched the ball again. Chiefs SB - Pretty terrible first half by KC but its still 14-6 with 1 minute in the half, and KC gets 50 yards of PI penalties on the drive to go into half down 21-6. Which essentially screwed what was left of their gameplan.
  14. The reason you use mesh is it sets open window reads and they're all really rapid. So you know - this guy uncovers first, then this guy, then finally that guy - and this guy over here is the hot. But if none of them uncover in rhythm (because the opponent knows you're running mesh) - they know once you move off read 1, you don't have time to go back to read 1, so i no longer have to cover him, then you end up with these busted plays where no one is open. There's plenty of ways to beat man coverage beyond mesh or rub routes. The challenge with the construction of these plays is always going to be proper diagnosis of coverage, identifying when players will uncover, and knowing when you have to get the ball out. Plus route running will help, but it's more of an issue of timing. When you run a timing based offense the ball goes to the same place at the same time. If you're running double moves to shake tight man coverage, that takes more time regardless of how fast you are. Part of the challenge buffalo is running into on a lot of scramble drills also reflects on the route's they're running. They run too close together so buying time doesn't create space since there will be multiple defenders in the area of bunched receivers. End of the day - if they're getting home with 4 THAT consistently, you have to change your approach.
×
×
  • Create New...