Warrior General Games

Originally posted by Adderfist
Speaking of Headfake/Juke. Carrying NEEDS to be taken out of the hf/juke equation when running routes.

Why? A player still needs to be able to hold onto the ball when he's juking

Originally posted by r8
Originally posted by Adderfist

Speaking of Headfake/Juke. Carrying NEEDS to be taken out of the hf/juke equation when running routes.

Why? A player still needs to be able to hold onto the ball when he's juking

Not if he doesn't have the ball

fakes are overpowered period, carrying or not. Guys can do a fake running full speed without breaking stride which is bull shit.

Originally posted by r8
It looks to me like the WR does make a few little moves, and the CB is just reacting to them.

So that is causing the 5 yard fallback as well? I mean think about things here for a minute. Close/AGG plays your man 5 yards in front of the WR....Semi plays your man 5 yards behind your WR. There has to be a middle ground we can find somewhere, correct?

Originally posted by tautology
Originally posted by Modok

http://goallineblitz.com/game/replay.pl?game_id=477470&pbp_id=8818365

This CB is on Close/Semi. Watch he he falls back after the ball has thrown then watch him shimmy/shake. I havent seen the funny shaking before.

I have seen the shimmy a few times as well...I was curious about what it meant...?

It looks a lot like the CB failed a vision check.

Originally posted by Modok
Originally posted by r8

It looks to me like the WR does make a few little moves, and the CB is just reacting to them.

So that is causing the 5 yard fallback as well? I mean think about things here for a minute. Close/AGG plays your man 5 yards in front of the WR....Semi plays your man 5 yards behind your WR. There has to be a middle ground we can find somewhere, correct?



I agree 100%

Originally posted by PierreThomas
Originally posted by tautology

Originally posted by Modok


http://goallineblitz.com/game/replay.pl?game_id=477470&pbp_id=8818365

This CB is on Close/Semi. Watch he he falls back after the ball has thrown then watch him shimmy/shake. I havent seen the funny shaking before.

I have seen the shimmy a few times as well...I was curious about what it meant...?

It looks a lot like the CB failed a vision check.

So he is blind and epileptic.

so r8, what were the conclusions from the initial test games?

Originally posted by ijg
so r8, what were the conclusions from the initial test games?

Sorry guys, I've had a pretty rough week.

My very basic conclusion, and also a point of discussion on the test server right now, is that this may be more caused by the pass trajectory then anything else. I really need to run a test with the CBs on Close/Aggressive, with one QB on Bullet and one on Loft, and with deep passes.

Regardless, we've talked about changing the trajectory of the passes a bit. Here's a highly-simplified picture that sorta shows what the theory is.
http://i138.photobucket.com/albums/q262/ratenxs/CB-Int-Point.jpg

The Green line is the CB's point at which he is calculating where to make the interception. The red line is the current ball trajectory, and the blue line would be the same trajectory but with a little fluctuation in the height. As you can see the red trajectory means the trajectory for the ball intercepts the CBs INT point at a spot much farther away then with the blue trajectory.

That's the theory at least :-S We're getting there.

http://goallineblitz.com/game/forum_thread.pl?thread_id=2637368 - see Live Issues discussion here related to Issue 2.

Originally posted by odg62
fakes are overpowered period, carrying or not. Guys can do a fake running full speed without breaking stride which is bull shit.

Fakes are over powered? No, not even close.

I didn't crunch the numbers... It's almost Midnight... But which CB do you think did the best throughout that?

Originally posted by r8
Originally posted by ijg

so r8, what were the conclusions from the initial test games?

Sorry guys, I've had a pretty rough week.

My very basic conclusion, and also a point of discussion on the test server right now, is that this may be more caused by the pass trajectory then anything else. I really need to run a test with the CBs on Close/Aggressive, with one QB on Bullet and one on Loft, and with deep passes.

Regardless, we've talked about changing the trajectory of the passes a bit. Here's a highly-simplified picture that sorta shows what the theory is.
http://i138.photobucket.com/albums/q262/ratenxs/CB-Int-Point.jpg

The Green line is the CB's point at which he is calculating where to make the interception. The red line is the current ball trajectory, and the blue line would be the same trajectory but with a little fluctuation in the height. As you can see the red trajectory means the trajectory for the ball intercepts the CBs INT point at a spot much farther away then with the blue trajectory.

That's the theory at least :-S We're getting there.

If this is the case, then this is a vision issue? With the right amount of vision I'd think the CB is able to calculate where at which point he can intercept the ball.

It's my understanding that they don't want, or have not, changed where the CB is going to go after the ball. They are just changing the trajectory to make it to where the CB doesn't jump so far out on the receiver.

Which doesn't really help the underlying problem IMHO...

It should, IMO, be a vision check for the optimal place for the CB to catch the ball, not the first place he can.

Originally posted by Tigam
It's my understanding that they don't want, or have not, changed where the CB is going to go after the ball. They are just changing the trajectory to make it to where the CB doesn't jump so far out on the receiver.

Which doesn't really help the underlying problem IMHO...

It should, IMO, be a vision check for the optimal place for the CB to catch the ball, not the first place he can.

On the flipside, however, if he went for the 100% optimal place to catch the ball every time, we'd see waaaaaaaaaaaaay too many PDs and INTs.

I suggested that instead of a CB going for the first intercept every time or going for the best intercept point every time, that it should fluctuate somewhere in between based on a vision, jumping, catching, and a little randomness.