Have changed the position matrix to allow safeties to be converted to LB.

One of our new owners has suggested the following, which Im going to do unless there's objection with good reason.

QBs - > RB / FB
TE's - > OL
OL - > TE's
CB's - > LB's

You can post objection here or PM me to discuss. cheers, G

The only thing I would say is the matrix currently serves two purposes.

1. Specifies the positions you can convert a player to.
2. Allows positons for them to be in depth chart.

The two are different beasts.

If you want a CB to be able to convert to say MLB, then fine - would need to gain 50 lbs.
By doing so, however, that means people can put unchanged CBs into the depth chart at MLB - being around 50 lbs underweight, you're looking at around 7 points of speed or so.

Another problem is that someone (not me) requested things be made easier on matrix by making things reciprocal.

Which means you click to allow CB to play LB then by default LB to CB is also enabled.

End of the day, it's your league, your call, personally weight/speed is an issue.

I've suggested JDB decouple the two, have depth chart also consider player weight so grossly underweight players can't be selected.

I've no objection to whatever you decide, just things to be aware of.

Also, as said, you select TE to play OLine, then OLine are also auto selected to play TE.

TE will never meet the weight for G, T so will always be under. C would be ok.

Thanks Martin, you know as much as anyone playing the game about the game code, engine, et al. For now, I will go ahead with the request as posted, if there are any "hiccups" or noticeable "exploits", then will revert back to a more strict position matrix. There is also the near future roster auto-manager to be considered and how that will affect the position matrix. In the meantime, lets see how it goes and whether or not to retain the changes. Personally, I dont see it being a major issue, unless we see performance and stat anomallies, like WRs leading the league or their teams in rushing with 5 yd per carry or more averages. Exploitation of speed will not be tolerated. The weight/speed issue will most likely be a problem, even with conversion. At this point, Im in between, 50/50 one way or another. My priority is to get more of a RL simulation than less, so any future actions taken will relate to that.

OK, here's the RL analysis of CB converting to LB in the NFL.

"Directly converting a full-time, pure cornerback to a traditional linebacker is exceptionally rare in the NFL because of the massive physical differences in size and run-stopping duties. Instead, teams commonly transition safeties or large hybrid defensive backs (like Deone Bucannon or Markquese Bell) into box linebacker roles."

Based on that analysis, the goal being more RL simulation, and the potential for speed exploit, Im going to have the CB to LB conversion not eligible. If there is a request for change, give me an example/proof of it being done in the RL NFL.

I'd just say for clarity I have no access to the game code or game engine internal details.

From experience though, I've found my best defences have always been heavy blitzing ones - beats O linemen, can stuff the run. Putting CBs as LB would imo be problematic - 3-4 defence, blitz 1, 2, 2+ could be a pretty difficult D to play against, because the speed/weight advantage would be big - not as much as CB at DE - hasten to add, that's my gut feeling.

For those interested (or those who only joined the product committee lately so missed it... ), my suggestion was to amend the game engine with respect to the matrix.

A player should only be valid in depth chart or override slot if their weight is a minimum of a few % under the position weight. That would alleviate a lot of the problems caused by pushing underweight players - also feeds into the whole issue of conversions and weights, bodyframe should be a factor.

That in addition to several game engine changes/amendments being discussed in the MFN1 TEST league forum. In the meantime, will try for a good balance on the position matrix. I will be keeping a watchful eye on player performance after conversion or by overide. The stats will show and when I see out of the ordinary stat results, I will take a close look at whether or not there was a speed exploit involved. I doubt that it will be a problem, but will keep watch and also respond to any complaint about it.