Adjusting Speed Skill range in MainData

[nmleague]

I have already edited the speed skill range for each position once and have just done it again to try to get a better speed relationship between players.

1. Reduced the differences between WR, DB, TE, QB, RB and LB, bring the upper limit of all closer.

2. Im not sure about this, but the game generates over 400 players for each positon for the initial draft. Is this done randomly or is it done so that a normal bell curve results? If it generates a normal bell curve, there are so many players generated, that depending upon the number of teams in a league, each team would have no problem drafting players from the upper percentile. So if this is the case I have made the ranges between the uppper limit and lower much larger. Will give it a try to see the results.

Below are the initial R1 (speed) rating for each postion, and the new ones after the edit.



speed
positon old new
SB 75/80 65/80
QB 55/70 55/80
C 50/55 50/55
OL 50/55 50/55
K 55/65 55/65
P 55/65 55/65
BL 50/60 50/70
DL 50/55 50/70
RB 70/75 60/84
WR 75/85 60/88
KR 65/85 65/85
LB 60/70 60/80
DB 75/85 65/90
HO 55/70 55/70
TE 75/80 60/83
CO 50/60 50/60

[nmleague]

Here is an update. I recreated the 1959 NFL league using the MainData file with the above changes and the Pro league level. Here are the speed ranges for some particular positons for one team. This is after the draft, training camp and cuts.

QB 74-84
RB 73-93
REC 88-96
TE 75
OL 56-63

DL 60-76
LB 74-90, one player had the 90 the next highest was 86
DB 86-99, one player had the 99 the next highest was 96

Did a little of a quick game and things looked pretty good.

[Magnum357]

I do like how you set some of the ratings, it looks like there will be more variation between players with this Formula. But I'm a little concerned about the Defensive players. They look like they have slightly better Speed Ratings then the Offense. Any basis for this?

[nmleague]

Here is the rational for my ratings.

1. The DB speed range has the higher upper limit, Im still concerned about the pass coverage ability/logic in the game and have given them a slight advantage because of this. But otherwise my opionion from coaching and playing at the college level is that DB and REC are very close in speed.

2. Not based on any hard data, but on experience playing, coaching, and the perspective given on players by commentators like Mel Kibber (sp) here are what I think are realistic 40 yard times for each positon.

REC 4.3-4.7 realistic, majority probably 4.5-4.7, TE slower
DB 4.4-4.6 for most good coverage guys this is realistic, some SS may be slower
RB 4.4-4.8 May be very few faster, probably only some blocking backs slower
LB 4.5-4.9 Outstanding OLB are easily in this range, ILB more like 4.7-5
DL 4.7-5.3 most DE have pretty good speed, large DT may be slower than 5.3

This was my basis. And becuase Im concerned that the large number of players generated per posiiton (480), would create such a large number of upper percentile playlers in relation to the number of teams picking, so that each team would end up with players with a very narrow, very high speed range.

The first league created using this data seems to be meeting my desired results in two ways.

1. There is an overlapping of speed ranges of more positions ie. outstanding LB can now match all but the fastest RB

2. There is more variance in speed by position not the narrow 4-6 rating points that I was getting from the original MainDate, but more like 10-12

Again it is just my take, and an attempt to get more realistic results.

[VCFL Commish]

So you could also use this to make arena league teams to.Make it so WR/HB are the same generated number takeing the best atributes of the receiver and the best attributes of a Halfback and have a player that plays both ways.Same with DL/OL

[nmleague]

I have only been concerned with the players speed skill range so far, but all the skills can be edited. So you could probablly edit to get what you wanted, say you could edit so that OL get a skill range for block shedding, and that DL could have a skill range for holding block. Same for DB, REC and RB.

[mark1726]

ORIGINAL: nmleague

I have only been concerned with the players speed skill range so far, but all the skills can be edited. So you could probablly edit to get what you wanted, say you could edit so that OL get a skill range for block shedding, and that DL could have a skill range for holding block. Same for DB, REC and RB.

Good work. I actually went another route and made some fictional fast guys on a pro team. I had them catch the ball at the 50 then run to the 10 and time it to get a 40 time. From this I adjusted the "PhysicsBaseMoveSpeed" to 5.5 in the MainData .mdb (it was 7).

I found the fastest guys possible (speed 99/agility 99) to be running ~ 3.65 40's before this, now they run ~4.2 40's.

[nmleague]

That sounds like some great information! Have you tested it out in the game to see what effect it has?

Im going to make some more changes to the speed ranges. Probably reduce the upper limit for DL speed by 3-5 points. I havent done anything with the OL line yet, but I think I need to add 5 points to their upper limit.

Right now DT are causing alot of problems, doesnt seem to be because of their improved speed becuase guys with 73-75 are causing the problems. Maybe the OG just are fast enough off the ball so will give them a boost.

[mark1726]

ORIGINAL: nmleague

That sounds like some great information! Have you tested it out in the game to see what effect it has?

Im going to make some more changes to the speed ranges. Probably reduce the upper limit for DL speed by 3-5 points. I havent done anything with the OL line yet, but I think I need to add 5 points to their upper limit.

Right now DT are causing alot of problems, doesnt seem to be because of their improved speed becuase guys with 73-75 are causing the problems. Maybe the OG just are fast enough off the ball so will give them a boost.

Haven't tested it in anything other than practice. I found that out of the box the players were way too fast and needed to be slowed down so I did some experimenting.