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.5] Version 2dbb07a

By jdavidbakr - Site Admin
1/25/2019 12:38 pm
Warthog wrote:
My QB had 21 passes that were not complete. Of these, 4 were intercepted and 15! were knocked down. Feels like his high accuracy lead to some of these issues.


He did throw 55 passes, which is a lot. He was still > 60%.

The algorithm is dramatically different than it was when high accuracy resulted in lower completion rates (that was I think a 0.4.3 change but might have been 0.4.4). The completion rate is now completely tied to the accuracy of the passer (which includes calculations about pressure, pass distance, etc) + the catching skills of the WR (which includes several factors like the catch attribute, defender presence, height vs defenders, etc)

Re: [0.4.5] Version 2dbb07a

By setherick
1/25/2019 1:51 pm
To be clear, I'm fine with the knockdown rates as long as knockdowns are tied to Punish.

Re: [0.4.5] Version 2dbb07a

By jdavidbakr - Site Admin
1/25/2019 2:10 pm
setherick wrote:
To be clear, I'm fine with the knockdown rates as long as knockdowns are tied to Punish.


Indirectly they are ... right now, if the ball is not caught (punish/courage has a strong impact in that) and a DB is close enough to knock the ball down, they are getting the knockdown. Right now there is nothing else preventing a knockdown stat, but I can add a layer in the decision to reduce knockdowns for players with lower punish attributes.

Re: [0.4.5] Version 2dbb07a

By setherick
1/25/2019 3:31 pm
jdavidbakr wrote:
setherick wrote:
To be clear, I'm fine with the knockdown rates as long as knockdowns are tied to Punish.


Indirectly they are ... right now, if the ball is not caught (punish/courage has a strong impact in that) and a DB is close enough to knock the ball down, they are getting the knockdown. Right now there is nothing else preventing a knockdown stat, but I can add a layer in the decision to reduce knockdowns for players with lower punish attributes.


That would help. I would want to know that high punish is the reason that a defender is making a play and not that the ball was just uncatchable.

Re: [0.4.5] Version 2dbb07a

By raymattison21
1/25/2019 4:17 pm
setherick wrote:
jdavidbakr wrote:
setherick wrote:
To be clear, I'm fine with the knockdown rates as long as knockdowns are tied to Punish.


Indirectly they are ... right now, if the ball is not caught (punish/courage has a strong impact in that) and a DB is close enough to knock the ball down, they are getting the knockdown. Right now there is nothing else preventing a knockdown stat, but I can add a layer in the decision to reduce knockdowns for players with lower punish attributes.


That would help. I would want to know that high punish is the reason that a defender is making a play and not that the ball was just uncatchable.


If bump is keeping defenders close...maybe the cover/route skill could be layered in as well. Just so punish doesn't become overpowered . Same for the catch rating.

We had a lot of catch overs last game as passes seemed near or on target . We just gronked them to death. I thought it was realistic as our TE was in the slot often.

Re: [0.4.5] Version 2dbb07a

By Warthog
1/25/2019 7:56 pm
jdavidbakr wrote:
Warthog wrote:
My QB had 21 passes that were not complete. Of these, 4 were intercepted and 15! were knocked down. Feels like his high accuracy lead to some of these issues.


He did throw 55 passes, which is a lot. He was still > 60%.


I wasn't really questioning the completion percentage. It was more the fact that over 70% of the passes not completed were knocked down. That seems high. I mean, maybe this is related to setheric's point about "punish". In the real NFL, I don't think that many passes are "knocked down". Maybe I am splitting hairs about why a pass was not complete. Some times it is knocked away, so times its a well timed hit (punish), some times its a drop, some times its just good coverage by the DB that makes it difficult for the WR to catch the ball. Maybe that is what I am looking for clarification on. Was this really 15 knockdowns or were there some of these other scenarios in there as well?

My opponent's QB threw 50 passes, 22 incompletions, and my defense had 15 knockdowns.

Also, I've been wondering about the "... got away with a hold on that play." What is that all about? Really trying to make this realistic by having missed calls? Saints fan won't appreciate that.
Last edited at 1/25/2019 8:00 pm

Re: [0.4.5] Version 2dbb07a

By jdavidbakr - Site Admin
1/25/2019 9:36 pm
Warthog wrote:
Also, I've been wondering about the "... got away with a hold on that play." What is that all about? Really trying to make this realistic by having missed calls? Saints fan won't appreciate that.


This indicates that the DB successfully altered the path of the WR but it was not significant enough for the flag to be thrown. That happens all the time in the NFL - but it's not normally commented on; since you can't actually see it happen, there's an indication in the play-by-play to let you know that it did indeed happen.

Re: [0.4.5] Version 2dbb07a

By setherick
1/26/2019 8:57 am
jdavidbakr wrote:
Warthog wrote:
Also, I've been wondering about the "... got away with a hold on that play." What is that all about? Really trying to make this realistic by having missed calls? Saints fan won't appreciate that.


This indicates that the DB successfully altered the path of the WR but it was not significant enough for the flag to be thrown. That happens all the time in the NFL - but it's not normally commented on; since you can't actually see it happen, there's an indication in the play-by-play to let you know that it did indeed happen.
If

here's a good example of having it in the play by play: https://mfn1.myfootballnow.com/watch/9252#1685831

Without the hold this is a TD.
Last edited at 1/26/2019 8:58 am

Re: [0.4.5] Version 2dbb07a

By jdavidbakr - Site Admin
1/26/2019 10:08 am
setherick wrote:
jdavidbakr wrote:
Warthog wrote:
Also, I've been wondering about the "... got away with a hold on that play." What is that all about? Really trying to make this realistic by having missed calls? Saints fan won't appreciate that.


This indicates that the DB successfully altered the path of the WR but it was not significant enough for the flag to be thrown. That happens all the time in the NFL - but it's not normally commented on; since you can't actually see it happen, there's an indication in the play-by-play to let you know that it did indeed happen.
If

here's a good example of having it in the play by play: https://mfn1.myfootballnow.com/watch/9252#1685831

Without the hold this is a TD.


Should we change the text from 'got away with a hold' to something less incriminating? Any ideas?

Re: [0.4.5] Version 2dbb07a

By JCSwishMan33
1/26/2019 10:40 am
jdavidbakr wrote:
setherick wrote:
jdavidbakr wrote:
Warthog wrote:
Also, I've been wondering about the "... got away with a hold on that play." What is that all about? Really trying to make this realistic by having missed calls? Saints fan won't appreciate that.


This indicates that the DB successfully altered the path of the WR but it was not significant enough for the flag to be thrown. That happens all the time in the NFL - but it's not normally commented on; since you can't actually see it happen, there's an indication in the play-by-play to let you know that it did indeed happen.
If

here's a good example of having it in the play by play: https://mfn1.myfootballnow.com/watch/9252#1685831

Without the hold this is a TD.


Should we change the text from 'got away with a hold' to something less incriminating? Any ideas?

Why not something simple like, "[DBplayername] knocked the WR off his route", or, "[WRplayername] couldn't get into position because of the defender"?