Skip to content
View in the app

A better way to browse. Learn more.

BluegrassPreps.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bengals 27 Seattle 24 OT

Featured Replies

The update thread is very funny. I don't know how we won a game. We had a terrible defense, terrible clock management, terrible Marvin, Bad Andy is back, Nugent sucks, Tate sucks, Bengals are fraud, and the Bengals still won. Of course, now Seattle isn't very good.

 

Will someone please tell me when we play a team that is decent. I'm tired of playing all bad teams.

 

This week was a decent team if you need to know.

 

Don't read the update thread if you don't understand the ev and flow of an update thread. When the Bengals looked bad it was posted at the time they looked bad, when they looked good it was posted when they looked good. To come in after the fact as if you knew how it would end up is kind of cowardly. When Andy looked bad, it was stated. When Andy looked great it was stated. When defense looked bad with horrible tackling again it was stated at that time, when they made huge plays it was stated also. Not sure what you think an update thread is supposed to be like, but apprently it isn't for you.

  • Replies 100
  • Views 12.5k
  • Created
  • Last Reply
New England and Green Bay aren't on the schedule. Therefore we don't play anybody any good.

 

Right. Should be 16-0! Same old Bengals if they lose to one of the slacker teams on their schedule...

So according to some, bad Andy today. 30-44 331 yards 2td 1int and had an 80 yard TD reception called back.

 

The interception was bad but overall, another great performance. He has been a top 5 QB this year.

This week was a decent team if you need to know.

 

Don't read the update thread if you don't understand the ev and flow of an update thread. When the Bengals looked bad it was posted at the time they looked bad, when they looked good it was posted when they looked good. To come in after the fact as if you knew how it would end up is kind of cowardly. When Andy looked bad, it was stated. When Andy looked great it was stated. When defense looked bad with horrible tackling again it was stated at that time, when they made huge plays it was stated also. Not sure what you think an update thread is supposed to be like, but apprently it isn't for you.

 

I was there the whole time...

Since you avoided the question in the other thread, how was this a bad call?

 

An invalid fair catch signal is when the player signaling for a fair catch does not fully extend his arm above his head. If the player's arm is flexed, an invalid fair catch penalty will be called and the ball will be marked down at the spot of the invalid fair catch and then assessed a five yard penalty.

 

That's literally exactly what happened.

 

I was going off of what the announcers stated who are supposed to know the rules more than me or you. They said the arm needs to be raised above the shoulders. It wasn't, some may say it wasn't even a motion of a fair catch in the first place, some will say any wave of a hand is a signal. I went off of what the announcers said and according to them at the time it was a blown call.

  • Author
So according to some, bad Andy today. 30-44 331 yards 2td 1int and had an 80 yard TD reception called back.

 

The interception was bad but overall, another great performance. He has been a top 5 QB this year.

Rush TD as well.

again, no fair catch signal was made, so not sure where it was decided it was a fair catch move.

 

He flexed his arm to try and trick the Seahawks defender. It worked, but he didn't fool the ref. That's what this rule is there for.

So according to some, bad Andy today. 30-44 331 yards 2td 1int and had an 80 yard TD reception called back.

 

The interception was bad but overall, another great performance. He has been a top 5 QB this year.

 

He had another great game if you ask me. Some bad decisions made him look bad at times, and his 3rd qtr he reverted back to his old self but fixed it and had an outstanding 4th qtr except for taking some unnecessary sacks.

He flexed his arm to try and trick the Seahawks defender. It worked, but he didn't fool the ref. That's what this rule is there for.

 

That's fine. Like I said, I was going off of what was said on TV.

5-0.For some of the younger members, this could be the best Bengals team you have seen. Try to enjoy it...

 

I was 8 the last time.

That's fine. Like I said, I was going off of what was said on TV.

 

I figured, which is fine. But I've learned over the years that the guys doing the commentating don't generally have the best understanding of the rules. I typically ignore them and try to find an interpretation elsewhere.

I was 8 the last time.

 

I'm so old.

Not your same old Bengals huh?

 

I think playoff time will determine that.

For all those people talking about the update thread. At around 3pm when the Bengals went down 17, where were all those folks posts then saying the Bengals were going to win? Nowhere, that's where. So do us a favor and don't criticize those talking about what is going on at the time n a game and come back later and criticize those who are actually making posts unless you have the guts to make posts stating the Bengals would win being down 17 at that time.

  • Author
I think playoff time will determine that.

No matter what happens in the playoffs this is not a game the "same ol Bengals" would win.

Archived

This topic is now archived and is closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.