(02-25-2022, 05:29 PM)RiverRat13 Wrote: I don't think they will cut Hopkins until they have a known quantity to replace him.  That may not happen until after the draft.

(02-25-2022, 05:27 PM)ochocincos Wrote: I see talk about wanting to upgrade the C position, and I think it makes sense if the Bengals can find an actual upgrade for a not-crazy cost since OT and OG also need taken care of and are higher priority.
But what I also see a lot of is people talking about cutting Hopkins to use the $6 mill in saved cap to (help) cover the new C.

Rather than that idea, I wonder if it would actually be worthwhile to try moving Hopkins to either LG or RG vs cutting him if a C upgrade is added. Hopkins is entering the final year of his contract and could give that extra year for Carman to develop if he needs it.

It's worth pointing out that back when Hopkins was drafted, many experts felt his best spot on the OL was LG. It fit his profile of being an athletic, quality pass-blocking OL.
Hopkins also started at RG back in 2018 when Pollack previously was the OL coach.
Hopkins allowed 4 sacks that year and just 2 penalties. His pass-blocking PFF grade was 72.8, and his run-blocking grade was 53.0.
Many did not like Hopkins at RG that year because of his lack of ability in the run game.

Keep in mind that when healthy (which is now), Hopkins is a better pass blocker than any other IOL who was on the team last season.
Hopkins also would provide that backup option for C if an injury were to occur.

Would you consider keeping Hopkins but moving him to OG if the Bengals decide to upgrade the C position?

(02-25-2022, 05:29 PM)RiverRat13 Wrote: I don't think they will cut Hopkins until they have a known quantity to replace him.  That may not happen until after the draft.

(02-25-2022, 05:29 PM)RiverRat13 Wrote: I don't think they will cut Hopkins until they have a known quantity to replace him. That may not happen until after the draft.

(02-25-2022, 06:18 PM)Whatever Wrote: To me, it depends on a number of factors.  Cap space is the biggest one.  If we need the cap space, then cut him loose.  If not, I would hold on to him.  While he would be overpaid for a backup, he can play all 5 OL positions.  He's not great at any of them, but can at least be a serviceable spot starter anywhere on the OL and allow you to run your offense.  If the Bengals tag/resign Bates AND land an A tier FA OL(Armstead, Brown, Scherff), I think they have to cut him.  

It's not what I would do, personally, but I think Trey gets kicked to RG and will likely compete with Carman for that spot.  The logic with that move is Trey is a better RG than anyone we had there last year, so you improve two positions on your OL with one FA C signing.  By having him compete with Carman, they aren't giving up on a 2nd round pick after only one year, either.  

(02-25-2022, 07:45 PM)SunsetBengal Wrote: I voted release him.  I really feel that moving him back to Guard would yield terrible results, he simply cannot move defenders off the ball.  He can't even budge the guy right over him enough to get a yard on critical short yardage situations.  He's been adequate in pass protection, but I think that we can at least expect adequate protection from a guy that can at least come through in short yardage situations.

Cut him, save the $6M, and use that money toward a Center that can move someone.

(02-25-2022, 07:56 PM)bengalfan74 Wrote: Me to

I just think it's time we stop accepting so-so Olinemen and start expecting better.

(02-25-2022, 06:23 PM)XenoMorph Wrote: If he couldnt make the starting 5 he be a good backup not sure his salary though

if we draft any OL we will have a lot of OL on the 1st or 2nd year of a rookie deal unless we cut some from last year