Is it just me being stupid but there doesn't appear to be anywhere that shows which players blocked punts? This would allow people to easily spot the players that typically get the job done and allow you to scheme against specific players etc

Also why do fumbles and interceptions on specific plays not show up on play cards? All very good knowing you get 5.8 yard average on three different playcalls but it would help to know how many ints or fumbles you have made on each play. Maybe you're better taking a play with a lesser average yards but also less chance of turning the ball over.

It would be good to get a breakdown of where the ball has gone too for each play e.g.
Play called 15 times 10 receptions 58 yards 2 drops 2knockdown, 1 int
RB 2 rec 7 yds 3.5 av 2 drops
TE 1-6 (6) INT
WR1 7-45 (6.5) 2 Knockdown
WR2 0-0
WR3 0-0

And for each player to show there stats when playing in different positions HB, RB, FB, TB, TE, SE, FL, SL, WR4, WR5
WR1

This might be a better fit in the Suggestion Box. I would also like more info if possible.

With the current state of the game...punt blocks need to show up somewhere instead of calling them fumbles or turnover on downs since we seem to have 3 to 4 punt blocks per game now.

I'd like to see punt blocks go the way of the punt return TD, maybe have 1 or 2 per year per league. I just lost another game yesterday because of this BS.

I've stopped seriously gameplanning anymore. I set my depth chart, load my saved gameplan and hit auto scout...I will continue to do this until this is changed

I would say the NFL has maybe 1 or 2 (punt blocks) most weeks, probably more with maybe 5-10 returned for TD's over the course of a season

2019 regular season - 11 punts blocked total
2018 regular season - 16 punts blocked total
2017 regular season - 11 punts blocked total

stats from https://www.footballdb.com

I had 7 punts blocked in one Conference Final alone, and the guy who did the damage just could run fast, nothing else.

I would be happy, if the Punt block Numbers would go drastically down. Don't want to have to check my Punt Protection team every game and let my DBs rush the Punter, despite them having ridicolous low standard rankings as a ST Rusher

The same reason punts are blocked is the same reason we cant return them now.

PR had gigantic numbers years ago. If a team used AI and had no speed they would let up at least 1 PR td a game. It was fun, but it decided close games just like punt blocks now.

The reason is the "actual" speed gaps created by weight, but by no means are the blocks now as bad as the returns were years ago (in my gaming experience of late)

Balance is the impossible part because of this imbalance of actual speed. The skill ratings are rendered ineffective when top notch actual speed is apllied.

What i see here is another suggestion for a nerf applied to make up for this speed gap. Not that i care what is done to patch/fix code anomiles but i want the speed gaps fixed at some point.

Then we will be able to move forward with alot of what i consider exploits. Punt blocks are one, but currently i still cannot block them at an nfl rate in big games. So....

On the other hand i would say the most competitive users all use some form of what i consider these "speed gap" exploits in other or all areas of the game. Fun or not i have lobbied for these types of "root cause" changes for years.

Of the latest beta changes the value of zero speed has been upped, since i seen little to no blocks in beta, besides TJs team who using a RB at punter. Do these same 96 speed punt blocks happen in beta....IDK? but i know the zone changes have balanced the level of man and zone.

Is it perfect, definitely not ......have we been on 4.5 too long? well at least 6 months too long in my opinion, but that doesn't matter cause the feedback of 4.6 would be like 4.5 and 4.4 and 4.3.....and so on...

Still, he has tired to do the right thing and is looking at the game as whole and , imo , is addressing the most important areas whithin a reasonable scope of where the current code is at in relation to what can actually be fixed with out completely messing another area up.

2018 16 punts blocked
2019 11 punts blocked

The Patriots set a team record with 4 blocked punts last season

https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.patriots.com/news/game-notes-patriots-set-team-mark-with-fourth-blocked-punt-of-the-season&ved=2ahUKEwiwidajuaboAhU4mHIEHY8lB7cQFjAOegQIAhAB&usg=AOvVaw1Py5bDlS5nmQRoJG0723B

In my leagues

XFL LEAGUE WEEK 9 featured 8 total punts blocks (144 over 16 games)

CHAMPIONS LEAGUE WEEK 8 featured 5 total punt blocks (80 over 16 games)

Without balance how can anything be argued. Champions best numbers are producing punt return tds at a rate six times lower than the nfls. That would sway games outcomes just like the blocks?

QBs dont even run or scramble thats 10% of real football completely missing...... How about the horrid throws into double coverage or tight windows? My rates there are absurd compared to the nfls.

Others completely whack are tackle for losses ( i had 16 with one player in one game) another is hurries....arron Donalds realife numbers 600% higher than any player in beta.

Fumbles and missed tackles show how weak the skill rating actully matters the more "actual speed " is played with......its the speed gaps that need fixing asap...

Flanker hitch any weak side run and every pass to a RB in the flats are all broke bad because of the speed gap.

Small dlinemen being better pass rushers just like punt blocks all from speed gaps being off....

The same glitches i apllied years ago still work now its just a smaller window. Playing this way, "taking advantage of speed gaps within players weight differences" with the same gameplan and no scouting will get you plently of unfair wins.

I just dont get how the punt blocks are a big deal.....is ANYONE putting small fast pass blockers to counter act this? (combined with elite long snapping and punt timing).... probably not cause it will hurt your team in other areas....

Were really complaining about the pass block code here...that whole thing could use an upgrade