The Lions’ 41-31 loss to the Bills on Thursday night did more than send Detroit back to the drawing board. It also put the spotlight on a rookie class that was missing pieces, still sorting itself out, and in a few cases already flashing real value.
The biggest absence was right tackle Blake Miller, who had to sit after hurting his knee late in Week 1. With Miller out, Larry Borom got the call and had a rough first start as a Lion, drawing three penalties and giving up a sack. Detroit may be comfortable using Borom for depth, but the gap between the two was obvious in Buffalo.
That absence mattered because Miller had already shown enough in his first start against the Saints to make it clear he’ll be a major part of the offense if he stays healthy. The encouraging part for Detroit is that the injury does not sound severe, and some around the team believed he might have played in Week 2 if the Lions had a full week instead of only three days between games.
On the other side of the ball, the Lions were also without cornerback Keith Abney, who was inactive after making his NFL debut with 25 defensive snaps last week. Detroit chose to dress veterans Christian Izien and Roger McCreary instead, and that decision kept Abney on the sideline even after he had already gotten a taste of game action.
Still, the question lingers: could Abney help this secondary more than the team is currently asking? He’s undersized, but he has shown the kind of speed and physical edge that can play in the slot. Thursday’s game only sharpened that debate.
There’s also some uncertainty around Avonte Maddox, who left the Bills game with a foot injury. There were no new updates by publication, but Dan Campbell did sound uneasy about it. If Maddox can’t go next week against the Jets, Detroit could lean more on Izien at safety alongside Chuck Clark and Thomas Harper, which would open the door for Abney in Week 3.
Beyond the injured and inactive, the rookies already on the field have given the Lions a mixed but interesting early picture.
Moore has appeared in both games and has worked as a rotational pass-rusher, but he’s still chasing his first real impact play. He hasn’t logged a tackle through two weeks, even as Aidan Hutchinson has carried the load with three sacks. Moore has the tools to matter in Detroit’s defensive line rotation, but the production hasn’t shown up yet.
Gill-Howard, on the other hand, has looked like a player the Lions are happy to keep feeding snaps. After a strong preseason, he’s earned a heavy workload and has played 71 snaps through two games.
He nearly delivered a splash play Thursday, diving for an interception that was wiped out by a defensive holding penalty. Even so, he looks like a good fit next to Alim McNeill in passing situations.
Rolder is still waiting for his first game action. A leg injury cost him valuable time in training camp, and that helped lead to Detroit bringing in Devin White. With seven linebackers on the active roster and several veterans ahead of him, Rolder has not been able to break through yet, though he had impressed in OTAs and appears to be moving toward a rotational role if he stays healthy.
There’s a similar theme with Law, who is already out for the season after tearing his ACL in offseason workouts. If he had been healthy, he might have had a chance to help on special teams and in the return game, but Detroit has used Tay Martin and Tom Kennedy in those spots instead.
O'Neill has found a way to help right away, just not at his listed position. He has stood out on special teams, where he’s had two solid games on the coverage units. That has helped keep him active on game days over Ahmed Hassanein, even though O'Neill remains lower on the defensive end depth chart.
Two games in, the Lions’ rookie class has already shown how quickly availability can shape opportunity. Some are injured, some are waiting, and a few are starting to carve out roles that could matter soon.
In Other News...
Lions Fans Had Another Reason To Be Furious During Bills Loss
The Lions had enough to process after a 41-31 loss to the Bills on Thursday Night Football, but the broadcast gave frustrated Detroit fans one more thing to notice in real time. Buffalo moved to 2-0 with the win, and Josh Allen did plenty of damage with five total touchdowns, yet the scoreboard on the screen briefly told a different story.
During the telecast, a graphic error incorrectly listed the Bills at 3-0 and the Lions at 1-2, a mix-up that was especially annoying for a fan base already watching its team absorb a costly defeat. It was the kind of small mistake that usually gets brushed off, except in a game like this it only added to the irritation as Detroit tried to make sense of a night that got away from it. [Read more 🡒]
Bills Had Dan Campbell Fuming Before This Game Was Even Settled
The Lions had enough offensive production to keep themselves in the fight at Highmark Stadium, but the bigger issue was how quickly the game slipped away. Jared Goff threw for 327 yards and four touchdowns, yet Detroit spent most of Thursday night chasing Buffalo after the Bills built a sizable lead behind a string of Lions mistakes and a defense that never found steady footing.
Dan Campbell was left visibly frustrated by the way the night unfolded, with the Lions piling up 10 penalties and taking repeated blows up front as Goff was sacked four times. Even with the late push, Detroit could not turn the score into a true comeback, and the loss served as another reminder that the margin for error shrinks fast when the discipline and defensive execution are not there. [Read more 🡒]
Lions Fans Had One More Reason To Hate That Primetime Loss
The Thursday night loss in Buffalo was already a rough one for Detroit, and it came with an extra annoyance for Lions fans watching at home. The Bills beat the Lions 41-31 in a game that pushed Buffalo to 2-0, while Josh Allen piled up five total touchdowns and kept the home side in control through the prime-time showcase.
Still, the broadcast itself gave the night a strange aftertaste. A graphic error briefly flashed the Bills as 3-0 and the Lions as 1-2, and that was enough to set off a wave of social media chatter about a supposed Week 3 script leak. It was just a mistake, but for a fan base already dealing with a frustrating result, it only added another layer to a night they would rather forget. [Read more 🡒]