NOTICE: This league is using the BLEEDING EDGE game engine. For more information, click here.

The new user interface is in preview!

Want to check it out? Click here! (If you don't like it, you can still switch back)

League Forums

Main - Beta Chat

Re: [Code Update] Line play/blocking update, player 'frame'

By Ragnulf-le-maudit
8/21/2017 12:10 am
raymattison21 wrote:
The weight of players seem to be changing very rapidly . I comparison to the past . Is this intended ?


I've noticed that too.

Re: [Code Update] Line play/blocking update, player 'frame'

By jdavidbakr - Site Admin
8/22/2017 8:21 am
raymattison21 wrote:
The weight of players seem to be changing very rapidly . I comparison to the past . Is this intended ?


For players near their frame, they will move faster than before.

Re: [Code Update] Line play/blocking update, player 'frame'

By setherick
8/22/2017 8:39 am
I have more notes on OL blocking, but I forgot to post them in this thread (will post them tonight).

In general, the skill vs skill looks better than it did before. But it's really calling out problems with spacing and players not staying home.

Also, it's amazing the difference 2 yards makes when an LB is blitzing: 5 yards out is mostly unstoppable, 3 yards out is always blocked. Can LBs get their spacing adjusted to always be 5 yards out?

---

Here you go.

1) https://beta87.myfootballnow.com/gamecenter/view/600#110505
a) On the snap, the LG spins out of his assignment and double teams the C for no reaason. This allows the blitzing LB to come free. The reason why the LB can come free is he starts at a proper distance from the LOS (5 yards off). When LBs start at this distance, they have proper reaction time, but the OL does not since the OL does not stay home. The majority of LB sacks happen this way.

2) https://beta87.myfootballnow.com/gamecenter/view/600#110506
a) Here's a better example of the weird things that happen by players not staying home. On this play the SLB is going to blitz the gap between the C and the LG. His spacing is off (~3 yards from the LOS). The RT takes the DE and the RG takes the DT. The RB misses the blitz pick up all together and runs right by the crashing LB. However, the LG comes back to make the block. The only reason that the LG can make the block in this case is because he's out of position. So while he makes the sack saving block, the blocking on the play really doesn't make sense.

3) https://beta87.myfootballnow.com/gamecenter/view/600#110511
a) So there isn't a lot you can do when the defense sends 7 against 5, so I see why this is a sack. It does a good job of illustrating how good LBs can be when properly spaced though. The LB starts about 5 yards from the LOS and just runs through it. That seems kind of suspect. I'm just mad because I scouted this play and I don't know why my QB didn't throw a hot read to the wide open TE, but he might not have had time.

4) https://beta87.myfootballnow.com/gamecenter/view/600#110539
a) Adding this play because it's a good example of how run blocking is still broken. Once the running back gets past the blockers, they all still switch places with the defender so that they can still block the defender. Good pick up by the FB though. The LB was properly spaced which meant open hole.

5) https://beta87.myfootballnow.com/gamecenter/view/600#110562
a) The blitzing LB is properly spaced, which usually means good things. The LG immediately double teams the C's man because there is no one in front of him on the snap. The QB manages to find a receiver down field though. Still, if the LG stays home, the QB has more time to find that man.
Last edited at 8/22/2017 6:03 pm