Warrior General Games

This is gonna sound dumb, but in a sim like this, you never know.

Do the QB and receiver even try to connect in stride on a slant pattern or route that is based on running after the catch? I see many times where a receiver in the Pro leagues should be lead to a spot where he can run after the catch, but instead, the ball is thrown right at hi, so he has to stop to catch it.

Originally posted by WiSeIVIaN
Ball hawk sucks for receivers imo...

Well I feel like the speed/agility bonus is generally worthless, but that vision bonus could get really interesting for speedsters with 60+ vision. Then you'd be pushing 100 vision while you're about to catch the ball, which could result in catching a lot more balls in stride. I'd imagine the effect would be even more pronounced with a QB with lower throwing but insane strength. A bunch of 115+ speed receivers with 60 vision and 15 ball hawk coupled with a QB with maybe only 90 throwing but also 90 strength would be interesting to watch.

Originally posted by Blamo
Well I feel like the speed/agility bonus is generally worthless, but that vision bonus could get really interesting for speedsters with 60+ vision. Then you'd be pushing 100 vision while you're about to catch the ball, which could result in catching a lot more balls in stride. I'd imagine the effect would be even more pronounced with a QB with lower throwing but insane strength. A bunch of 115+ speed receivers with 60 vision and 15 ball hawk coupled with a QB with maybe only 90 throwing but also 90 strength would be interesting to watch.

Even 60 vision won't activate it to often, from what I've seen (mostly with defense). 70 gets maybe 3-5 hawks per game that I notice.

Originally posted by Blamo
Originally posted by WiSeIVIaN

Ball hawk sucks for receivers imo...

but that vision bonus could get really interesting for speedsters with 60+ vision. Then you'd be pushing 100 vision while you're about to catch the ball,

Math fail

1st off, did anyone with Ball Hawk actually analyze whether or not it made a difference on catching the ball in stride? How do you measure something that is highly subjective? According to Lithium, vision will help with your catch roll to make it more likely you catch in stride rather than stopping. If this is true, it minimizes the effect of using vision to get into position to catch the ball and maximizes vision as just another part of the catching equation- the real usefulness is for catching in stride. So again, were any nay sayers of Ball Hawk actively monitoring its effects on "catch-in-stride" balls, if so how the hell did you determine what was a "slow down" and what wasn't?

Doesn't ball hawk give a 20% vision increase fully pointed? Going from 48 to 58ish is huge! On paper that is a big difference. I don't think a speedster will need more than 68 vision ever. So going to 60 and taking ball hawk would get you there no problem, but I suspect 60 vision is more than acceptable.

Back to speed penalties. If someone is going to spend 6 SP for 1 point of speed, they shouldn't have to invest more into agility, vision, and catching to make up for that SP spent, that just isn't fair. As if there wasn't enough of a penalty on excessive speed with the increased cap costs (remember these, if this game were balanced correctly this should be the only penalty and apply to all attributes), the reduced effectiveness of speed against CBs, the need for higher agility to hit top speed, now we need higher vision and catching just because we invested in more speed than someone else at a higher cost which means we get less return on the SP, and even less on the attribute with the other previously mentioned penalties. Fuck speed, this sounds like something designed by Bernie Madoff.

Originally posted by foofighter24
This is gonna sound dumb, but in a sim like this, you never know.

Do the QB and receiver even try to connect in stride on a slant pattern or route that is based on running after the catch? I see many times where a receiver in the Pro leagues should be lead to a spot where he can run after the catch, but instead, the ball is thrown right at hi, so he has to stop to catch it.

It happens, but it's rare http://goallineblitz.com/game/replay.pl?game_id=695086&pbp_id=19526186

Originally posted by kurieg
Originally posted by foofighter24

This is gonna sound dumb, but in a sim like this, you never know.

Do the QB and receiver even try to connect in stride on a slant pattern or route that is based on running after the catch? I see many times where a receiver in the Pro leagues should be lead to a spot where he can run after the catch, but instead, the ball is thrown right at hi, so he has to stop to catch it.

It happens, but it's rare http://goallineblitz.com/game/replay.pl?game_id=695086&pbp_id=19526186

That was a thing of beauty.

Originally posted by kurieg
It happens, but it's rare http://goallineblitz.com/game/replay.pl?game_id=695086&pbp_id=19526186

The problem is that's too rare. I'd rather see more plays where the ball is thrown in front of the WR, and he either runs to it and catches it in stride, or fails to catch it, than the current situation, where the ball is almost always thrown directly to where the WR is, and he has to stop or slow down to catch it.

T

Originally posted by tsherr
The problem is that's too rare. I'd rather see more plays where the ball is thrown in front of the WR, and he either runs to it and catches it in stride, or fails to catch it, than the current situation, where the ball is almost always thrown directly to where the WR is, and he has to stop or slow down to catch it.

T

It's pretty rare in the NFL too. Brett Favre was probably the best player at it of all time (Joe and Steve were pretty good too) and even he didn't get it perfect all too often. I think it should happen more than it does now, but not too much.

Perhaps there needs to be an option (perhaps on a WR by WR basis) where the QB can be set to try to throw the ball in front of the WR and let the WR run to it (the way Chicago attempted to do with Hester last season, but Orton didn't have the arm for it.) It wouldn't work all the time, since it would be hard for a)the QB to get the ball in front of the WR in the right spot, b)the WR to see the spot and run to it successfully, and then c)all the normal catching issues. But when it worked, it would look cool, and would really reward all the WRs who have cranked speed.

T

It's rare enough where it almost makes me believe it was a "bad throw" that just happened to lead the WR.

Originally posted by WiSeIVIaN
Ball hawk sucks for receivers imo...

I disagree to a point. I like having 5 or so ball hawk on my WR, but wouldn't spend a full 15 on it.

x-factor