User Pass
Home Sign Up Contact Log In
Gabrosin
offline
Link
 
Replay: http://goallineblitz.com/game/replay.pl?game_id=191547&pbp_id=218912

Okay, I see the pause to break the LB's tackle, and then our HB continues up the empty sideline. It looks like he moves for the sideline to avoid either the FS coming from across the field or the blocked CB... then, as if he cut TOO hard to the sideline, he comes to a dead stop, then tries to accelerate again, and gets caught by the FS who shouldn't have had any chance to stop this play (not without a long chase down the sideline). Is this what it looks like? Juke to avoid a player, then juke/stop to avoid the sideline? Would be nice if this was managed better.

When a real player is near the sideline and is getting pressed towards it by an approaching defender, he usually takes an arcing path that splits the difference for maximum yardage. I would think that some sort of adjustment that takes proximity to the sidelines into account when dodging a tackler wouldn't be too tough.
 
tigerbait22
offline
Link
 
Play looks fine to me
 
joeami
offline
Link
 
He stopped to make sure he had the first down
 
Novus
offline
Link
 
Build up his Agility or his Quick Cut rating. He had to change his running angle to stay in bounds, also known as a "cut." That's why he stopped momentarily.

By the way, never tell a programmer that you think something "shouldn't be too tough." Sometimes it's the stuff that a layman thinks "should" be easy to program that turns out to be the toughest.
 
JefT@nk
offline
Link
 
I think, the last stop, on his route down the sideline was because he was trying to juke the SS like he was going inside. I'm guessing the SS's vision was good enough to not let him fall for the juke.
 
Mightyhalo
offline
Link
 
FS is a level 6 too and he was all over that play.
 
Gabrosin
offline
Link
 
Originally posted by Novus
Build up his Agility or his Quick Cut rating. He had to change his running angle to stay in bounds, also known as a "cut." That's why he stopped momentarily.

By the way, never tell a programmer that you think something "shouldn't be too tough." Sometimes it's the stuff that a layman thinks "should" be easy to program that turns out to be the toughest.


Unless you're also a programmer, which I am :-)
 
Gabrosin
offline
Link
 
Originally posted by JefT@nk
I think, the last stop, on his route down the sideline was because he was trying to juke the SS like he was going inside. I'm guessing the SS's vision was good enough to not let him fall for the juke.


SS wasn't in the play, and if you mean the FS, his vision is only 25 and his agility is less than 15. Just seems odd that his player, with such low stats, is able to make the play on a HB who has 50+ speed and 50+ agility.

I'll suggest a couple of points in Quick Cut though.
 
RMiller517
offline
Link
 
Thread locked by moderator.
 


You are not logged in. Please log in if you want to post a reply.