Possible Recruiting Issue: Emphasis on HB, WR, ATH

[NEOPARADIGM]

It's always something. smh

[BestServedCold]

It could be that you are going off of the SPARQ rating, which is a rating based on athleticism, mainly speed agility and strength.

Naturally, the fastest, most agile players on the field will be the HBs, WRs, and ATH.

So, I'm not sure if this is a problem.

[NEOPARADIGM]

Quote: Originally Posted by BestServedCold

It could be that you are going off of the SPARQ rating, which is a rating based on athleticism, mainly speed agility and strength. Naturally, the fastest, most agile players on the field will be the HBs, WRs, and ATH. So, I'm not sure if this is a problem.

Oh, right on, man. Hope you're right.

[redsfan4life]

It's not the best solution, but if a team recruits too many WR's you could just edit a few coverage ratings and make them a DB. Same for RB's to S/LB etc. If you did this at least the teams that recruit well could still get rewarded.

[weeeeeeez]

Quote: Originally Posted by BestServedCold

It could be that you are going off of the SPARQ rating, which is a rating based on athleticism, mainly speed agility and strength. Naturally, the fastest, most agile players on the field will be the HBs, WRs, and ATH. So, I'm not sure if this is a problem.

That's actually a pretty good point.

[MannyBeltre_PP]

I'm not using the SPARQ rating.

I have been using Pastas rosters, so I tried starting a dynasty with a new set to see if that made a difference. 35/50 were the three positions. I've looked at the ATHs skill sets, and indeed they all match up with HBs and WRs.

I did some quick math on the top 300, over 1/3 are essentially HBs and WRs. That means about 55 RB's and 55 WR's in the top 300. If you divide 300 by 22 (# of positions on field), ideally you'd want something around 13-20 per position in the top 300.

[BestServedCold]

Quote: Originally Posted by MannyBeltre_PP

I'm not using the SPARQ rating. I have been using Pastas rosters, so I tried starting a dynasty with a new set to see if that made a difference. 35/50 were the three positions. I've looked at the ATHs skill sets, and indeed they all match up with HBs and WRs. I did some quick math on the top 300, over 1/3 are essentially HBs and WRs. That means about 55 RB's and 55 WR's in the top 300. If you divide 300 by 22 (# of positions on field), ideally you'd want something around 13-20 per position in the top 300.

http://www.operationsports.com/forum...n-ongoing.html

Based on that thread it doesn't seem to be the problem (see the second graph).

Obviously, more data would be very helpful.

[Milkmoney11]

Okay. I was wrong. Well...sort of.

This is a bigger issue than it was last year. I did some investigating. I generated 10 recruiting classes from this year, and 10 recruiting classes from last year. I looked at the top 20 players (this year SPARC and last year the espn top 150) to see how many were either a HB, RB, or ATH. Here's the results

NCAA 2011 - 9,11,11,13.8,11,13,9,9,12 Mean 10.5
NCAA 2012 - 17,17,18,18,15,15,18,19,17,18 Mean 17.2

In NCAA 2012, 17.2 players out of 20 (on average) were rb, wr, or ath compared to 10.5 on average last year.
Now this is only the first year. I didn't generate any deeper into the dynasty, but there definitely are more HB, WR, and RB being generated this year. At least in the top players.

I'm hoping it corrects itself later in the dynasty. If not, it might be an issue.