Jump to content

Recommended Posts

Posted
1 hour ago, Bob Chandler's Hands said:

I think that's right.

 

Separately, for the 17th game, since we played Washington at home, then LA on the road, we should get either the NFC North or South next year, and could be home or away, I guess.  If we win the division should be GB or Tampa?

 

Tampa, or whoever wins NFC South. And at home.

 

https://fbschedules.com/2023-buffalo-bills-schedule/

  • Like (+1) 1
Posted (edited)
1 hour ago, LABILLBACKER said:

Exactly....last year we took care of business in Arrowhead but those embarrassing loses to Pittsburgh, Jacksonville & the Wind NE game just destroyed us. We've already lost a weather (112° index) game in Miami.  We can't afford a let down this Sunday regardless of the slew of injuries. 

I think Poyer being out hurts the most because even with the other guys in the secondary out, he was the guy that kept the squad together even with the 2nd and 3rd stringers.

 

I'm gonna blow a gasket if we make this kid look like the second coming of Tom Brady coming off the bench for an injured Bledsoe.

Edited by Billz4ever
  • Like (+1) 2
  • Vomit 1
  • Eyeroll 1
Posted
42 minutes ago, No_Matter_What said:

It doesn't work like that for all divisions, but yeah it does for AFC East. And there is no way how to avoid it. See below.

 

It is not flawed; this is actually the only way how to do it (within existing system). First of all, you need to exclude playoffs from your calculations, that is just something entirely different.

 

Secondly, you can't look at just KC, since 2 out of 3 years we only play them if we end up on the same spot in respective divisions the year before. So, you need to look at it as an AFC West opponent. For a second let's imagine that both we and Chiefs always win our respective divisions. Then we would play them like this:

 

2020 home (we played complete West division, home game vs North winner, road game vs South winner)

2021 away (South whole division, North home, West away)

2022 away (North whole division, South home, West away)

2023 away (West whole division, South home, North away)

2024 home (South whole division, West home, North away)

2025 home (North whole division, West home, South away)

2026 home (West whole division, North home, South away)

2027 away (South whole division, North home, West away)

 

As you can see, it is completely fair, it just doesn't work as you would intuitively expect - rotating those games when we don't play whole division. And here is the trick - it is not possible, at least not for all divisions. It is hard to explain, but trust me on this, you just can't create a formula where you alternate home and road games for all divisions.

 

And for some reason AFC East is a division which plays every other division the way GBF describes above - we play each division twice in a row at home and then it rotates. But since every third year we play all teams from such division, it ends up like it is - we play AFC West counterpart three times at row at home and then three times at row away. It looks weird but it makes scheduling sense. And to be clear, not all divisions work like this. For example, AFC South only plays like this with our AFC East. But vs other divisions they rotate games more.

 

So we are just unlucky to hit away streak vs them and it is multiplied by the fact that we always end up playing at Arrowhead in January. That needs to change :)

 

One last note - as a result of above formula, this is the third year in a row when we play Steelers at home.

Thanks for the explanation. I'm still irritated by it, but I get your point. It wouldn't matter so much if the years of consecutive KC games didn't also coincide with a time when both teams are in the ascendancy and vying for the top seed in the conference. Fluke or not, it's an advantage for KC.

  • Like (+1) 1
Posted
11 minutes ago, Billz4ever said:

I think Poyer being out hurts the most because even with the other guys in the secondary out, he was the guy that kept the squad together even with the 2nd and 3rd stringers.

 

I'm gonna blow a gasket if we make this kid look like the second coming of Tom Brady coming off the bench for an injured Bledsoe.

 

We had the entire secondary out and forced a rookie PS CB in Ingram into the game for 2.5 quarters in Miami and largely made the Dolphins look bad on offense.  Tua threw for 187 yards.

 

We have Dane Jackson this game and Elam now has a few more games of experience and has played very very well.  I think we will be fine.  D Line should maul them up front.

  • Like (+1) 1
Posted (edited)
5 minutes ago, Big Turk said:

 

We had the entire secondary out and forced a rookie PS CB in Ingram into the game for 2.5 quarters in Miami and largely made the Dolphins look bad on offense.  Tua threw for 187 yards.

 

We have Dane Jackson this game and Elam now has a few more games of experience and has played very very well.  I think we will be fine.  D Line should maul them up front.

I certainly hope you're right.  I'm just recalling opponents we've made look better than they really were.

Edited by Billz4ever
Posted
5 hours ago, Back2Buff said:

Guys not playing because of soreness is pitiful.  

 

I can't stand how conservative McDermott is with injuries.  Burned us big time in Miami with the botched snap.  

What botched snap?  

Posted
2 hours ago, ColoradoBills said:

 

They got 5 DTs.  One has to sit.  I think Ed plays and Phillips sits one more week and is ready for KC.

Jones, Settle, Bryant and Oliver will be more than enough to give the PIT(T) rookie fits.

 I think that's likely

  • Thank you (+1) 1
Posted
Just now, Bob in STL said:

What botched snap?  

 

It's scored as a Josh Allen fumble.  There was an aborted snap in the 1Q of the MIA game. 

 

But @Back2Buff is confused, because it was recovered, just cost us a down, and we scored a TD 3 plays later.  The other 2 fumbles were strips.

 

It was clear that Allen was having to look for the ball and adjust A Lot, and that cost us all game in being able to quickly adjust and also in not being able to operate under center (Dorsey admitted that).  

 

But Morse and Allen had a couple of exchange problems at the end of the Tennessee game as well, and Morse and Allen had an aborted snap that put us in 4th and 1 in the 3Q of the Ravens game.  So it's  really not clear that McDermott was being "too conservative" vs. Morse genuinely having a R arm injury that affected his ability to snap and caused him to need to rest a week and heal (incompletely).

Posted
13 minutes ago, Billz4ever said:

I certainly hope you're right.  I'm just recalling opponents we've made look better than they really were.

 

That's been many many years ago. I am not sure that has happened under McD.  Usually we make them look like they shouldn't be in the NFL.

  • Agree 1
Posted
4 minutes ago, Beck Water said:

 

It's scored as a Josh Allen fumble.  There was an aborted snap in the 1Q of the MIA game. 

 

But @Back2Buff is confused, because it was recovered, just cost us a down, and we scored a TD 3 plays later.  The other 2 fumbles were strips.

 

It was clear that Allen was having to look for the ball and adjust A Lot, and that cost us all game in being able to quickly adjust and also in not being able to operate under center (Dorsey admitted that).  

 

But Morse and Allen had a couple of exchange problems at the end of the Tennessee game as well, and Morse and Allen had an aborted snap that put us in 4th and 1 in the 3Q of the Ravens game.  So it's  really not clear that McDermott was being "too conservative" vs. Morse genuinely having a R arm injury that affected his ability to snap and caused him to need to rest a week and heal (incompletely).

And the play that Allen failed to spike the ball before the half, that was on Allen.  He lost control of the ball.  

Posted
3 minutes ago, Bob in STL said:

And the play that Allen failed to spike the ball before the half, that was on Allen.  He lost control of the ball.  

 

Watch the snap again...it was a bad snap...he snapped it off the top of his butt.

Posted
5 minutes ago, Bob in STL said:

And the play that Allen failed to spike the ball before the half, that was on Allen.  He lost control of the ball.  

 

I'm not so clear on that.  When there's a problem with the C QB exchange, you don't know which side it's on usually.

Posted
41 minutes ago, Billz4ever said:

I think Poyer being out hurts the most because even with the other guys in the secondary out, he was the guy that kept the squad together even with the 2nd and 3rd stringers.

 

I'm gonna blow a gasket if we make this kid look like the second coming of Tom Brady coming off the bench for an injured Bledsoe.

I am wondering where this worry is coming from

We have shut down Stafford Lamont and Tua Now we’re worried about a rookie on a losing team?

 

The defense is as healthy as it’s been in weeks because we’re finally getting some interior pass rush back

 

Relax

  • Like (+1) 1
Posted
3 hours ago, CEN-CAL17 said:

Yeah to miss 4 games with an ankle injury seems like a lot…. Was Ed’s ankle a high ankle? Cause I just thought it was ankle…. Didn’t seem serious but he’s played like 2 Qtrs this year 

 

I think it was a locker room interview, Oliver said he didn't think it was a high ankle initially but by the time he got off the plane from LA, he knew.  So yeah, and missing 4-6 weeks is kinda standard for that.

Posted
18 minutes ago, Big Turk said:

 

That's been many many years ago. I am not sure that has happened under McD.  Usually we make them look like they shouldn't be in the NFL.

I kinda put the Jacksonville game last year in that category.  I still can't believe we blew that game.

  • Disagree 1
Posted
Just now, Billz4ever said:

I kinda put the Jacksonville game last year in that category.  I still can't believe we blew that game.

 

Trevor Lawrence threw for 118 yards.

  • Thank you (+1) 1
Posted
13 minutes ago, Beck Water said:

 

I'm not so clear on that.  When there's a problem with the C QB exchange, you don't know which side it's on usually.

As a former center I think I do.  LOL 

  • Haha (+1) 3
This topic is OLD. A NEW topic should be started unless there is a very specific reason to revive this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...