![]() |
Quote:
|
I chose QB.
|
EDGE
We have shown the ability to make due with average WRs, RT, and S but say what you want about Frank Clark - we have no one across Karlaftis right now. That's an actual hole unless Brett can plug it before the draft. In order I'd say: 1. EDGE 2. WR 3. OT 4. S/DT |
Quote:
I wasn't wanting a WR or LT high in the draft but our options are slim at this point. I could see them taking RT. I don't care where we draft a WR because it's pretty clear that guy isn't getting starting snaps anyway. I'm holding out hope that we make a trade commonly seen on draft day: no one knew that player X was even on the block but during round one was traded. There's a lot of these trades that teams don't want info leaking to the media because it may not pan out and then player X is pissed off and still there. I think that happens with LT or WR honestly. Veach let two WR's go on very affordable deals. He's got something planned. |
Taylor is your LT. Barring one of the top two falling....drafting a LT isn't going to happen. Not sure why people can't come to grips with that.
|
Quote:
|
Quote:
Just like we shouldn't have drafted MEH in the first round. Veach is great but he ain't perfect... |
Quote:
Can both of these things be true at the same time? They are both things that have come from the Chiefs. |
I went DE. I think WRs and RTs can be found in the 2nd. I wouldn't be a bit surprised to see Veach trade some of those Day 3 picks in order to move up into Day 2.
|
We have a bottom 10 WR corps right now. People are reading the wrong things from last season if they think the takeaway should be Mahomes and Kelce are enough by themselves.
|
Thank you
|
Quote:
|
Felt like OT or DL a week or so ago, but we have guys with experience there. Tony and Moore going into next season still feel a bit green to me.
|
Quote:
|
DE.
That said I think Veach should just go best player available there's no real huge need. |
All times are GMT -6. The time now is 04:07 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.