Home Discord Chat
Go Back   ChiefsPlanet > Nzoner's Game Room
Register FAQDonate Members List Calendar

View Poll Results: Well?
A 51 41.46%
B 52 42.28%
C 7 5.69%
D 6 4.88%
F 2 1.63%
Gaz 5 4.07%
Voters: 123. You may not vote on this poll

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
Old 04-26-2019, 11:22 PM   #10
Dante84 Dante84 is offline
Tossed Salad & Scrambled Eggs
 
Join Date: Jan 2009
Location: ATX & OPKS
Quote:
Originally Posted by neech View Post
B

He shouldn't have traded up in the second.
Watch the 8 minute presser on KC Chiefs Facebook page and breaks down exactly how it happened.

- They had their eyes on him
- They were getting a lot of calls from teams trying to trade up to 61
- They got a call from the Rams trying to trade down
- They figured it was the time that the WR's were going to have a run, and didn't like how many teams were calling up
- Veach decided to pull the trigger
- They take Hardman
- After the pick, the Chiefs called back all the teams who were trying to trade up to 61 to see if they were interested in 63, and all the teams said "no, thanks."
- He then finds out from his scouts' connections that a lot of teams wanted Hardman
Posts: 19,756
Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.Dante84 is obviously part of the inner Circle.
    Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On

Forum Jump




All times are GMT -6. The time now is 09:35 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2024, vBulletin Solutions, Inc.