New Sticky Note

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: [0.4.6] Version 0d5f5ac

By Infinity on Trial
10/31/2020 8:53 pm
What is happening with this toss route?

https://mfn1.myfootballnow.com/watch/12142#2264488

Re: [0.4.6] Version 0d5f5ac

By TheAdmiral
11/01/2020 4:05 am
It looks like the QB makes a poor toss, thowing a little behind the RB - kind of a timing issue, maybe? or just an error.

Also the FB #38 stays too narrow, perhaps forcing the poor toss.
Last edited at 11/01/2020 4:12 am

Re: [0.4.6] Version 0d5f5ac

By raymattison21
11/01/2020 7:00 am
The MLB was on a blitz and the FB went to block him. By observation alone The Whos gonna block who on running plays seems predetermined. I could be wrong but because the LB blitzed that gap the FB blocked that gap.

Him getting in the way and Changing the pass/pitch angle? That’s good....I wonder if that happens on all bad pitches?

The SS who was assigned to man 3 , the rb, had very little cover skill ,I don’t think he was in bump either but he proceeds to over contained the back. That part looks normal and getting all conspiracy theory .... bump or the RT playing C with 75 snapping probably was not a factor.


Probably just a bad pitch but maybe the blitz rushed the QB and he made a bad pitch? Either way this has been a problem since around the same time a lot of current problems arose. It’s not bad but the rate it occurs might be a bit high.

Re: [0.4.6] Version 0d5f5ac

By setherick
11/06/2020 11:34 pm
I just ran a whole lot of data and long passes are completely useless. They get sacked or under pressure 50-80% of the time. And when they don't get sacked, they don't complete passes. There has to be some give take here.

Re: [0.4.6] Version 0d5f5ac

By TheAdmiral
11/07/2020 5:50 am
setherick wrote:
I just ran a whole lot of data and long passes are completely useless. They get sacked or under pressure 50-80% of the time. And when they don't get sacked, they don't complete passes. There has to be some give take here.


This ^^^

QB play has been improved in the last week or so. They now try to find space rather than hide behind a collapsing pocket. However against long passes, forget it. Their is a real reluctance to throw the ball when their is ample opportunity to do it. It's like the QB gets to the end of his reads and then stands still to take the sack.

As an experiment I took long passes out of my gameplan for todays game - result zero sacks taken, we got 12 but our opponent was playing a Tackle with a broken ankle (ankle health: 0) he alone gave up 7 sacks.

With short and medium passes, the QB release is within 2-3 seconds but the pass blocking doesn't hold up beyond that. I would suggest the following as potential fixes.

1. Increase pass blocking effiency against pass rush

2. Pass blocking strength should be position specific. For example, a 60 strength DL, should be the equivalent of a 90 strength LB and a 45 strength DL should be the equivalent of a 90 strength DB. This should do two things - make the battle of strength v speed more even and therefore reduce the amount of teams carrying 15 CB's.

Converting a player from one extreme to another eg DE to CB, LT to WR or vice versa should see extreme changes in strength. On the field it should see good OL bullying weak/understrength rushers pushing them backwards and creating big rushing lanes with an element of boom/bust whereby if the rushers avoids the blocker the QB is in trouble

3. Check what happens with QB logic on extended plays - what are his options when he has finished his reads. Run?, throw to best receiver?, throw into single coverage?, throw deep?, throw it away?, dump off short?, throw a hail mary?

Some of these would result in increased possibilities of interceptions.

4. Increase reception probability on long throws - not massively but if you throw four or five deep ***** in a game you should expect to complete at least one of them

Re: [0.4.6] Version 0d5f5ac

By setherick
11/07/2020 8:39 am
The other problem with yards per attempt is that all of the routes are still too shallow. This has been a problem forever, but it's becoming more apparent now that other things are improving.

Basically every set route needs to be extended 2-3 yards. The drag routes, for instance, hug the LOS when they should be 3-4 yards deep. The 2-3 yard hitch routes would be OK if they were automatic, but they are not hitches. Instead, they are short hooks, which means they should end 4-5 yards deep. The hook routes end up being 5 yards deep when they should end up being 6-8 yards deep.

On the hitch and hook routes, the WR needs to spin and sit because the ball should be in the air before they spin. On the hook route the WR needs to come back fast and sit. Right now, on both types of plays, the WR continues running after he spins.

QBs also do not anticipate their routes and put the ball in the air before the receiver is in position (enough). Like Admiral said above, this is most noticeable on long passes where a QB needs to put the ball in the air when the receiver is 10-20 yards from where he's going to catch it.
Last edited at 11/07/2020 8:49 am

Re: [0.4.6] Version 0d5f5ac

By setherick
11/07/2020 8:46 am
Can these be fixed finally? https://mfn1.myfootballnow.com/watch/12184#2273669

QB has 100 accuracy and the RB has 82 route. These are still happening too frequently.
Last edited at 11/07/2020 8:46 am

Re: [0.4.6] Version 0d5f5ac

By TheAdmiral
11/10/2020 6:11 am
RB's and Field of Vision?

Just a question really but is Field of Vision a factor for RB's and if not should it be? I've noticed that most RB's will follow a blocker and ignore a gap created. Here's an example.

https://mfn1.myfootballnow.com/watch/12207#2277523

The RB is Tennessee's Mull, https://mfn1.myfootballnow.com/player/16073 a very good RB with masses of experience. Initially he appears to go for the gap then veers into a blocker who is being double teamed resulting in a short loss. If he went for the gap, he likely gets a first down

https://mfn1.myfootballnow.com/watch/12207#2277528

On this play my RB Duane Stone has a lead blocker who runs straight into a wall of players instead of veering towards the gap where he should be able to block/slow down the LB. Stone could follow his blocker or use it as misdirection and cut to the right where there is another gap. Instead he too ploughs into a wall of players.

Stone https://mfn1.myfootballnow.com/player/18239 Is a converted QB so not in the same class as Mull. He does have very good field of vision though so should spot the gap and go for it (my opinion) regardless of his lead blocker.

Perhaps it's down to intelligence, perhaps RB's just look for a blocker to follow - you see a lot of Punt returns where the punt returner heads to the sideline looking for a blocker rather than take an easy 5-10 yard gain up the middle. Basic point is RB's should be looking for open space to run into and not blindly following a blocker

Re: [0.4.6] Version 0d5f5ac

By raymattison21
11/10/2020 8:06 am
FOV is the degree of angle the QBs uses when targeting receivers. It takes in to account the way the qb is facing at the moment. Its only used in passing situations. Intelligence/ experience “finds the hole” but i like to use carry in tandem with to simulate the rb having “good vision “

Re: [0.4.6] Version 0d5f5ac

By TheAdmiral
11/10/2020 8:10 am
raymattison21 wrote:
FOV is the degree of angle the QBs uses when targeting receivers. It takes in to account the way the qb is facing at the moment. Its only used in passing situations. Intelligence/ experience “finds the hole” but i like to use carry in tandem with to simulate the rb having “good vision “


But there is no reason why field of vision should not be incorporated for all positions. I see it being very important for MLB's, Safeties, Slot receivers, Tight Ends, Full Backs and Running Backs.