Mcbolt55 wrote:
I can buy into this multiple roll score. I thought ball carry was supposed to be similar “modifier” for adjusting run speed with the ball. Route run should be the same, and countered by the coverage skills of the defender. Much like the bump and run scores and catching.
The biggest problem with the “physics” rolls or player speed is that the lighter player with more speed will currently dominate without repercussion for being undersized. If force truly matches mass * acceleration, then does our acc skill factor in? Strength should be part of a force calculation as well, as well as the particular type of contact, be it blocking or tackling. I also think height should matter more in contesting passes, or maybe incorporate a “jumping” skill.
It shouldn’t be about just making every player as fast as possible, there should be an impactful sacrifice somewhere. I don’t think the draft should be loaded with quality players, busts should still happen, but players should be created with certain physical mins and max that reflect reality.
Route and cover only come in to play when the receiver makes a cut. B&R does modify the speed depending who wins the roll.
Acceleration only really comes in to play within 1.5 yards.. maybe 3-5 if it’s really low and speed is very high.
Catching and courage act like jumping.
Strength is tied to weight but needs to be used with the body mass index (weight/height) instead.
Its the reason pro OTs are taller than Gs and rbs are stockier than WRs.
Durability is tied to this irl. Here injures happen due to weight and fatigue rates but a player’s density is never factored here ever.
Its the core flaw causing alot of these loop holes to exploit the code.
I was able to get a QB with 8200 pass yards and 88 tds and a wr having 5400 receiving yards and 60 tds in one regular season. This was using only three different plays and is the main reason the current code is like it is today.
Until how speed, strength and fatigue rates are modified by a players weight everything is a bandaid. And crafty users will find a way around the new code tweaks.
The solution is use weight/height instead of weight alone