Warrior General Games

Nice post.

But I'm wondering on those plays where the ball hits the WR but it's an incomplete, what attributes or SAs affecting the "can I catch it" check are too low that they think they can't catch it.

Originally posted by Viscount
Nice post.

But I'm wondering on those plays where the ball hits the WR but it's an incomplete, what attributes or SAs affecting the "can I catch it" check are too low that they think they can't catch it.

wow that's interesting...is it possible the ball is hitting the receiver after its already incomplete?

I also thought its interesting that a dropped ball = a ball that the receiver tries to catch but doesnt. There's a difference between trying and not catching, and actually getting your hands on it and dropping it.

I saw that post too, definately good stuff. Think I've finally got a handle on how it works. All about the catching/jumping/how "open" the WR is (not having a CB molest you in first 1.5 seconds of a catch ), maybe strength too if a CB is near (contesting the catch) As far as the dropped balls, no WR should ever catch 100% of the passes thrown to him... mistakes will be made, sun gets in his eyes,he gets "butter-fingers" syndrome,ect...

If a WR is catching 100% of the ball thrown his way there is no reason to get catching up to 100

Originally posted by breakyourneck
If a WR is catching 100% of the ball thrown his way there is no reason to get catching up to 100

Yes there's a reason, so you're ''catchable ball radius'' gets bigger