Warrior General Games

This situation needs to be handled like baseball... either throw it to where the play is supposed to be or throw it to where you feel he can catch it... fuck waiting... especially with defensive pressure nowadays...

Originally posted by ryan_grant-25
This situation needs to be handled like baseball... either throw it to where the play is supposed to be or throw it to where you feel he can catch it... fuck waiting... especially with defensive pressure nowadays...

Or at least move around to avoid the three stooges that are attempting the sack.

Originally posted by ryan_grant-25
This situation needs to be handled like baseball... either throw it to where the play is supposed to be or throw it to where you feel he can catch it... fuck waiting... especially with defensive pressure nowadays...

This and/or

Originally posted by TheGreatPuma
Or at least move around to avoid the three stooges that are attempting the sack.

This.

I mean, we all know that Speed is overpowered, and situations like this don't make it any better.
Now, if you want this play to work, you have to have your TE raise speed and agility first?

Eh. Seems sketch to me.

I'm not sure about it being just the tight end not getting to the right spot in time. He's actually somewhat open before the sack takes place, and it just looks really strange when the running back passes in front of the quarterback.. Going to move this on for determination

Originally posted by blaslo
I'm not sure about it being just the tight end not getting to the right spot in time. He's actually somewhat open before the sack takes place, and it just looks really strange when the running back passes in front of the quarterback.. Going to move this on for determination

Thank you. The whole play looks screwy. For example, what the hell is the LOLB doing on this play?

Originally posted by blaslo
I'm not sure about it being just the tight end not getting to the right spot in time. He's actually somewhat open before the sack takes place, and it just looks really strange when the running back passes in front of the quarterback.. Going to move this on for determination

If QB's slider is set to route distance (rather than open man), doesn't matter if he's open before the sack. Also even if not, likely depends on QB passing vision check to see the man is open, etc. Furthermore, it may be the case that on screen passes the open man vs. route distance slider isn't even active (to avoid QB throwing a screen pass to HB on the first or second tick after he receives the snap, etc.)

I get that there are suggestions for improving this play... but in an edge case with the TE moving that slowly and not getting into position in time, I just don't think the play was coded up to deal with that highly unusual situation, and certainly can't say it's intended to cover that unusual situation the way that most of us would think "makes sense".

Feels much more like a suggestion than a bug to me, AND, the suggestion would need to be better thought out as to how you would actually implement it without creating more problems than you solve. I think that a QB being able to tuck and run, or at the very least move in the pocket to avoid pressure, even on a screen play would be a good suggestion. Would need to give much more thought to conceive of a well thought out suggestion for "throwing the ball sooner on a screen play when the receiver is moving at a sloth's pace" scenario. Either way, suggestions for improving this play seem like, well, suggestions... someone would need to point out something here that is not the way Bort intended to code things for this to be considered a bug. Just disagreeing with the way Bort chose to code it doesn't usually make it a bug.

Originally posted by haole
For example, what the hell is the LOLB doing on this play?

Looks like RT gives him an unusually massive shove, and that he likely has really low agility such that takes him a really long time to change his momentum back towards the QB. Just a best guess.

I agree with Doug. It's not pretty, but it's how screens are currently coded - the QB drops back, waits until the intended target gets to the screen spot, and then throws it. It does NOT use any of the standard "pass play" code for the QB - no vision lines, no scrambling, just drop, wait, throw.

Screens have already been remodeled to some degree this season, and perhaps they still need further improvement to look more realistic, but right now this is just a limitation of how screens are coded.

Not a bug.

Originally posted by Stray Doug
Looks like RT gives him an unusually massive shove, and that he likely has really low agility such that takes him a really long time to change his momentum back towards the QB. Just a best guess.


Yup. Also, same with the LDE, who gets pushed out wide and then can't adjust his path. This is what happens when you have dots with unbalanced attributes - they don't look human in some ways, because no human exists with those relative attributes.