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: Beta update release

By raymattison21
3/22/2018 8:05 pm
https://mfn1.myfootballnow.com/watch/7836#1416181

Why would this db stop covering? Looks as though he tripped .

Re: Beta update release

By raymattison21
3/22/2018 8:08 pm
https://mfn1.myfootballnow.com/watch/7836#1416318

This db stopped covering as well . Why?

Re: Beta update release

By raymattison21
3/22/2018 8:11 pm
https://mfn1.myfootballnow.com/watch/7836#1416195

Another play that looks like the db had tight coverage but stopped running right before the pass get to the wr.

Re: Beta update release

By setherick
3/23/2018 12:28 am
In another sure sign that attributes don't have anything to do with interceptions, 100 Accuracy, 100 Look Off QB threw 5 INTs against an AI team.

Also, I said this before, but this is more proof. Crossing patterns. Do. Not. Work. Now.

https://beta87.myfootballnow.com/watch/1545#282850

https://beta87.myfootballnow.com/watch/1545#282899

The QB throws the pass way too early into the pattern and throws into the worst coverage situation possible.

QB decision making on a lot more interceptions is also questionable. This QB has 94 FOV.

Throws into double coverage despite that EVERY OTHER WR is in single coverage: https://beta87.myfootballnow.com/watch/1545#282906

Single coverage on the outside, QB throws to the middle of the field into a cluster of four defenders: https://beta87.myfootballnow.com/watch/1545#282916

Pretty sure this is another example of the stutter step bug where the QB throws the ball to the wrong spot after the WR stutters to break free: https://beta87.myfootballnow.com/watch/1545#282960

So on interceptions, I'm a point where one of two things needs to happen:

1) DB's ability to intercept the ball gets turned down again.

OR

2) QB decision making to not throw into double or triple or quadruple coverage when there are single covered WRs available, the QB has time, and the QB has good FOV is improved.

Since I think 2 is going to be a big change, I think doing 1 would move 0.4.3 closer to release. The number of interceptions, especially on crossing patterns and short passes, makes this unreleaseable because no one will excuse an increase on INTs within 10 yards of the LOS.
Last edited at 3/23/2018 12:36 am

Re: Beta update release

By Ragnulf-le-maudit
3/23/2018 3:48 am
Some kind of stutter step bug
https://beta87.myfootballnow.com/watch/1552#284098

Overall it looks like the qb doesn't read his progression anymore, and stay on his first option.

I've had at least two a punt return straight into the gunner. Here is one.
https://beta87.myfootballnow.com/watch/1552#284164

Re: Beta update release

By raymattison21
3/23/2018 7:02 am
setherick wrote:
In another sure sign that attributes don't have anything to do with interceptions, 100 Accuracy, 100 Look Off QB threw 5 INTs against an AI team.

Also, I said this before, but this is more proof. Crossing patterns. Do. Not. Work. Now.

https://beta87.myfootballnow.com/watch/1545#282850

https://beta87.myfootballnow.com/watch/1545#282899

The QB throws the pass way too early into the pattern and throws into the worst coverage situation possible.

QB decision making on a lot more interceptions is also questionable. This QB has 94 FOV.

Throws into double coverage despite that EVERY OTHER WR is in single coverage: https://beta87.myfootballnow.com/watch/1545#282906

Single coverage on the outside, QB throws to the middle of the field into a cluster of four defenders: https://beta87.myfootballnow.com/watch/1545#282916

Pretty sure this is another example of the stutter step bug where the QB throws the ball to the wrong spot after the WR stutters to break free: https://beta87.myfootballnow.com/watch/1545#282960

So on interceptions, I'm a point where one of two things needs to happen:

1) DB's ability to intercept the ball gets turned down again.

OR

2) QB decision making to not throw into double or triple or quadruple coverage when there are single covered WRs available, the QB has time, and the QB has good FOV is improved.

Since I think 2 is going to be a big change, I think doing 1 would move 0.4.3 closer to release. The number of interceptions, especially on crossing patterns and short passes, makes this unreleaseable because no one will excuse an increase on INTs within 10 yards of the LOS.


Actual qb skill matters less in this code . Same for line play , but gameplan matters most.

Re: Beta update release

By setherick
3/23/2018 7:15 am
Skill does matter, but elite QBs are so over-generated right now, they are being artificially nerfed.

There should only be a few QBs in the league with ACC, Look Off, and FOV over 90, but the league is filled with them because so many people complained about how weak drafts were and how there were no late round boom players and that they didn't have a roster filled with elite players and that they couldn't win unless they had a roster full of elite players and that they didn't actually want to take the time to game plan for their roster, etc. etc. etc. etc. etc.

Re: Beta update release

By raymattison21
3/24/2018 6:38 am
setherick wrote:
Skill does matter, but elite QBs are so over-generated right now, they are being artificially nerfed.

There should only be a few QBs in the league with ACC, Look Off, and FOV over 90, but the league is filled with them because so many people complained about how weak drafts were and how there were no late round boom players and that they didn't have a roster filled with elite players and that they couldn't win unless they had a roster full of elite players and that they didn't actually want to take the time to game plan for their roster, etc. etc. etc. etc. etc.


The logic is there.....but should this guy be best at completing passes and avoid pressure ?

Michael Feltner 36Att 23comp 63.9 % 253 yrd 1/9 s/y2tds 2 ints 79.98rating

He's a sub 70 passer in all relevant categories but seems to hold his own time and time again.

Re: Beta update release

By setherick
3/24/2018 8:23 am
1) https://mfn1.myfootballnow.com/watch/7857#1420002
a) Stutter stepping by the WR throws off the ball placement of the throw.

2) https://mfn1.myfootballnow.com/watch/7857#1420049
a) Stutter disrupts ball placement.

Re: Beta update release

By jdavidbakr - Site Admin
3/24/2018 11:18 am
setherick wrote:
In another sure sign that attributes don't have anything to do with interceptions, 100 Accuracy, 100 Look Off QB threw 5 INTs against an AI team.

Also, I said this before, but this is more proof. Crossing patterns. Do. Not. Work. Now.

https://beta87.myfootballnow.com/watch/1545#282850

https://beta87.myfootballnow.com/watch/1545#282899

The QB throws the pass way too early into the pattern and throws into the worst coverage situation possible.

QB decision making on a lot more interceptions is also questionable. This QB has 94 FOV.

Throws into double coverage despite that EVERY OTHER WR is in single coverage: https://beta87.myfootballnow.com/watch/1545#282906

Single coverage on the outside, QB throws to the middle of the field into a cluster of four defenders: https://beta87.myfootballnow.com/watch/1545#282916

Pretty sure this is another example of the stutter step bug where the QB throws the ball to the wrong spot after the WR stutters to break free: https://beta87.myfootballnow.com/watch/1545#282960

So on interceptions, I'm a point where one of two things needs to happen:

1) DB's ability to intercept the ball gets turned down again.

OR

2) QB decision making to not throw into double or triple or quadruple coverage when there are single covered WRs available, the QB has time, and the QB has good FOV is improved.

Since I think 2 is going to be a big change, I think doing 1 would move 0.4.3 closer to release. The number of interceptions, especially on crossing patterns and short passes, makes this unreleaseable because no one will excuse an increase on INTs within 10 yards of the LOS.


Looking at these I suspect that a probability for the QB to not "see" the DB is firing. I am removing that, I'm not sure it's necessary with some of the other updates, to see if it turns down the interceptions a bit.