Quote:
First off, yes, creating a rule just for you to not do this would really suck and be wrong.
Secondly, the rule was there to keep people who were quitting the league from rage quitting and destroying all their players or getting mad at a guy who would not sign a new contract extension and making him worthless before becoming a FA.
Lastly, about the change and player in question and my opinion. It certainly seems that on the FOFC boards the consensus is that WR>RB in this version. However, we also know that a new version is in the works for release this year or early next year and the value of one position over another could be very different. Ok, taking that speculation aside, what about this player making the change right now in this version. We know that the WR bars will go down some as a 100 RR for a RB is not the same as 100 RR for a WR, so we know he will not be a 90 overall WR. He has near 100 talent in most every bar for a RB and some of the WR bars will be unknown, but likely to be definitely above average for Courage, Big Play, and Adjust to Ball, but also likely to not be 100. At 5'10", he is not suffering a penalty at RB, but a 5'10" WR will perform between 2%-5% lower than what the WR bars suggest he would perform. All of those dings would still make him a top 8 WR in this league and my guess would be around a 75 overall rating. WRs that start every game gain XP at a decent clip, so he should max out in under 3 seasons after the move. If I had a top 5 or 10 QB and a team nibbling at the playoffs, I would have to really consider this move, but with your QB situation and the uncertainty of the new version of FOF, if it were my team, I could not make that change at this time.
This, and all other comments about the idea, from you all are appreciated, especially the fairness they were offered with.
As it turns out, Knight's top would drop from 91 to 88 as a wideout, but once a position change is submitted to a game engine, those changes can drop even more, sometimes drastically. But apparently Knight is sort of a Percy Harvin type that can really go either way. Charlie Taylor (from the Redskins of the early 70's) was originally a running back (hence his 42 number) and converted, and Bobby Mitchell also converted to wide out before his Hall of Fame career was over. It's not a stretch in terms of immersion or realism.
I would rather have an 88 potential WR than a 91 potential RB.
But I'm not going to convert him right now. I need a QB more than any thing, and chances are if I'm drafting one, or developing my rookie Mandylor successfully, my QB will be limited in formations and TEs, RB's and even FBs become a little more helpful to young QBs. WRs always trump all those other positions (unfortunately), but I'm not ready to toss away such potential bell-cow and work-horse (see what I did there) like Knight. He tweaked his knee earlier this season for a couple games and I can't run as much as I want since the Bees are usually behind on the scoreboard or he'd be among the leaders in rushing and all-purpose yards. (If padding stats gave me a willy just for the sake of it, I could run, run, run, but I'd rather win games, if I can.)
However, I will be sending him out wide on a number of formations (in the Formation Personnel screens) and putting my fullbacks or other halfbacks in the backfield instead. I've already been doing it lately with some success. Probably the only success the snake-bitten Bees can claim is having a dual threat like Knight to move the chains. So, keeping him where he is lets me get the most out of him.
Thanks, guys.
Login
FAQ
