Alphadawg7 Posted Wednesday at 08:47 PM Posted Wednesday at 08:47 PM 2 hours ago, Yard Monkey said: Yes, pathetic. If you are referring to the Packers game, it was his last play as a Bill thankfully. Chan Gailey was furious on the sideline. All of the receivers ran vertical routes and he didn’t throw it. “Trent Edwards' infamous 4th and 11 play happened during his final game as a Buffalo Bill on September 19, 2010, against the Green Bay Packers. Instead of attempting a pass, he ran out of bounds after gaining only 6 yards, sealing Buffalo's fate in a 34-7 loss. It was a frustrating moment for Bills fans, and just eight days later, Edwards was released by the team.” Yeah that was it...so bad, for some reason I thought he was on the team longer than that after it, but still should have been cut before he hit the showers lol Quote
Dr. Who Posted Wednesday at 09:38 PM Posted Wednesday at 09:38 PM 6 hours ago, Jalan81 said: No argument here. We’ll see if wide receiver has changed at all. I’m still confused at how little Cooper added, it was like Brady used him as a decoy more than a strength. Is he washed or just another player we couldn’t take advantage of their skill set? The fact we didn’t attempt to resign him makes it look like we think he was washed or didn’t want to be here. Sad part is McDermott has been here too long to still not have it all put together in my mind. Cooper is probably done. I empathize with concerns about McDermott, though I like the fella. Then I think about the Sabres and what happens when Terry Pegula has more say, and I count my blessings. 1 Quote
BUFFALOBART Posted Wednesday at 11:45 PM Posted Wednesday at 11:45 PM 13 hours ago, uticaclub said: That wasn't a cheap shot & if that hit derails his career, he was never meant for the NFL It was a cheap shot. 2 1 1 Quote
Bleeding Bills Blue Posted 16 hours ago Posted 16 hours ago 12 hours ago, BUFFALOBART said: It was a cheap shot. Im not sure if was a "cheap shot", as I think he's just attempting to disrupt the catch point (because he was late to play the ball -being bad/slow is not cheap). However he lead with the crown of his helmet to a defenseless player and it resulted in a penalty/fine. 1 Quote
finn Posted 16 hours ago Posted 16 hours ago (edited) 18 hours ago, Alphadawg7 said: The worst play I have ever personally witnessed was watching Trent run out of bounds on 4th down on our final drive of the game instead of trying to make a play happen. Most pathetic, gutless, unacceptable play I have ever seen live in a game. She should have been benched or cut before he hit the showers. Makes me smile to think we have the polar opposite of this at QB now. The only way Josh Allen goes out of bounds short of the marker on fourth down with the game on the line is in the air as he throws it on target thirty yards down the field across his body. Edited 16 hours ago by finn 2 Quote
Coach Tuesday Posted 16 hours ago Posted 16 hours ago 16 hours ago, Alphadawg7 said: Yeah that was it...so bad, for some reason I thought he was on the team longer than that after it, but still should have been cut before he hit the showers lol I think he literally was… Quote
SoonerBillsFan Posted 15 hours ago Posted 15 hours ago 1 hour ago, Bleeding Bills Blue said: Im not sure if was a "cheap shot", as I think he's just attempting to disrupt the catch point (because he was late to play the ball -being bad/slow is not cheap). However he lead with the crown of his helmet to a defenseless player and it resulted in a penalty/fine. He left his feet and hit with the helmet. Cheap shot. He has always done this. Quote
Bleeding Bills Blue Posted 14 hours ago Posted 14 hours ago 18 minutes ago, SoonerBillsFan said: He left his feet and hit with the helmet. Cheap shot. He has always done this. I think a cheap shot implies some level of intent to injure or aiming for someone's head. He wasn't head hunting, he was actually playing the ball which is far from "cheap". Was he late? Yes, because his recovery speed is gone. Was it reckless? Yes, you shouldn't be diving like a missile at a receiver trying to make a catch. There will be big hits and violent collisions, it is football. But cheap stuff to me is usually head hunting, or late hits. 1 1 Quote
BADOLBILZ Posted 7 hours ago Posted 7 hours ago 9 hours ago, Bleeding Bills Blue said: Im not sure if was a "cheap shot", as I think he's just attempting to disrupt the catch point (because he was late to play the ball -being bad/slow is not cheap). However he lead with the crown of his helmet to a defenseless player and it resulted in a penalty/fine. For not being sure that it was a cheap shot in your first sentence you literally described it as absolutely a cheap shot in your second. Poyer had the option of pushing him out of bounds or trying to knock the ball out legally. It was a garden variety cheap shot, but dirty nonetheless. 2 Quote
Richard Noggin Posted 3 hours ago Posted 3 hours ago On 5/24/2025 at 2:24 PM, folz said: And no Quaterback can improve their completion percentage from college to the NFL, right? This is just silly. There is no way that Beane thinks he blew this pick already. You don't write any player off after their rookie year as a coach or GM (or you won't have your job for long). Plus, what do the defensive players have to do with anything in relation to the speed of a WR? Also, it's called team building. #1 WR priority according to the Bills at the time was get a bigger guy who can block and get 50/50 balls. They drafted Keon. Now we have that, let's go after our second priority. A guy or some guys with speed. It's not some admission of quilt. Again, it's team building. You don't keep bringing in the same type of player over and over, you have to fill certain roles, have diversity. And it's not like 4.52 and 4.46 are blazing speeds (as far as Beane bringing in only speed players). And our team would get bullied late in the year and in the playoffs by bigger, stronger teams. There has to be a balance. In the 2024 draft, 11 wide receivers were selected in the first two rounds (the first 52 picks). Seven of those WRs were picked before Keon. Here is what the stats of all of those receivers were after week 8 of last year (just before Keon's injury): Pick Player Targets Recs Yards TDs Team (# of team passing plays) 4 M. Harrison 50 26 411 5 Arizona (543) 6 M. Nabers 94 46 498 3 NYG (591) 9 R. Odunze 44 25 391 1 Chicago (566) 23 B. Thomas 49 33 573 5 Jacksonville (546) 28 X. Worthy 39 19 235 3 Kansas City (600) 31 R. Pearsall 9 7 59 0 San Fran (533) 32 X. Legette 35 22 211 3 Carolina (547) 33 K. Coleman 36 22 417 3 Buffalo (520) 34 L. McConkey 52 35 440 4 LA Chargers (510) 37 J. Polk 27 10 78 1 New England (529) 52 A. Mitchell 31 11 118 0 Indianapolis (513) At the time of his injury, Keon's stats were not looking bad in comparison to the other rookies. especially considering: -Nine of those eleven teams threw the ball more than the Bills did overall in 2024 (Bills had a 49/51 run/pass split and 42% of our passing plays went to RBs and TEs). Plus, some of those teams do not have the number of other targets/weapons as say Buf, KC, SF. Not as many balls to go around on such teams. -The disparity in number of targets. For instance, Malik Nambers had 58 more targets than Keon in that span. Tough to compare say yards between the guys who had a lot more opportunities (targets) than the others. And yet, at that time, with the 7th fewest targets (of the 11 players), he was 4th in total yards and tied for 3rd in TDs. There was no way we were going to be able to go up and get Harrison, Nabers, or Odunze. We probably could have swung for Thomas. And obviously, we could have picked Worthy, Pearsall, Legette, McConkey, Polk, or Mitchell---but they chose Keon. And before the injury, McConkey was the only WR that we could have chosen (where we were) that had better stats than Keon. But as others have said, McConkey is more a slot and not the type of WR we wanted/needed (same for Worthy---we weren't looking for a speed guy at that time). So, I'm having a hard time seeing any other move the Bills should have made as far as WR is concerned (other than possibly moving up for Thomas---but we would have had to have a trade partner too, who knows if that was available or not). Yes, Keon struggled coming back from the injury. I think that was two-fold. First off, he was out for almost 5 games starting in week 7 (probably tough for any rookie to acclimate back after that amount of time out). But, that is also the week that Amari arrived. Curtis Samuel got healthy around week 9. And Mack's target share went up a bit also. The offense continued to roll with Keon out and Amari, Curtis, and Mack getting more targets. So, when Keon came back, there was no need to force him in. Just keep rolling with what is working. And I think a rookie coming back from his first major injury to a much smaller role may have gotten in Keon's head a bit. He may have been a bit skittish from the hit. Worried about coming back too soon. A little depressed that his role had decreased, etc. But, again, he was a rookie. Give the kid time to grow, mature, learn, get more experience. It's seems strange to me to write off a high draft-pick rookie who got injured and missed 5 games his rookie season. Have some patience guys. I personally think that he's going to come back with a fire in his belly this year. Just seems like that kind of a kid to me. What an awesome post. The bit about our smaller (often banged-up WRs) getting bodied in the playoffs is accurate. So then it was best when Allen had a diverse/transitional WR crew in Davis, Diggs, and Beasley (and Sanders, sort of), and the bigger outside deep threat was able to beat the Chiefs man and maybe sometimes quarters/cover-3 (?) pressure looks all game long. Also, the slot WR reeled in some vital 1st downs. WR1 disappeared utterly and completely (3 for 7yds WTF). But still they did enough. Possible they've got similar depth and diversity of skills in 2025. No one as good as Diggs, but maybe a grittier, deeper, more physical WR room (especially in weeks 19+). 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.