User Pass
Home Sign Up Contact Log In
Page:
 
PING72
offline
Link
 
Why in the world would he jump behind the HB?

http://goallineblitz.com/game/replay.pl?game_id=784760&pbp_id=13806581

I understand to a certain extent he is reacting to a faster DB, but this still isn't right.
 
blankspace
offline
Link
 
Looks like the FB thought the HB was going to bounce to the outside instead of cutting in.
 
tragula
title
offline
Link
 
One ugly looking play.

The FB tries to block the SS, but since he is not fast enough he choose a senseless angle. As the OP said, it is clear how the it happen with the existing si. A player should understand that it is better to go to the next defender than to do what the FB does here.
 
tragula
title
offline
Link
 
Originally posted by blankspace
Looks like the FB thought the HB was going to bounce to the outside instead of cutting in.


Look at the FB path (use the script) he take an angle toward his own endzone. If he wanted to allow a cutbak he should go horizontally or slightly forward. That backward angle is silly

BTW,
isn't HB making a cutback inside in GLB just too rare ? In real football DBs and DEs are much better forcing the RBs to cut inside toward the LBs. In GLB this rarely happens
Edited by tragula on Sep 10, 2009 14:34:45
 
Captain Kaos
offline
Link
 
I see the FB is only level 9

Could you post rough numbers for the following?:
HB Speed -
HB Agility -
FB Speed -
FB Agility -
FB Vision -

Thanks in advance!
 
tragula
title
offline
Link
 
Originally posted by cwisler
I see the FB is only level 9

Could you post rough numbers for the following?:
HB Speed -
HB Agility -
FB Speed -
FB Agility -
FB Vision -

Thanks in advance!


Why is that relevant ? Obviously a good FB would not do that. But the FB had passed a vision check to change his path and made him go toward his own goaline, that vision check should never be there.

A bad build can result in not making a change of path (low vision), being too late (low speed) or overshooting his target (low agility). Vision check that makes a player decide to go into a wrong direction are bad to the game.
Sure in RL stupid players do awful things (I can tell you mine), but for GLB stupidity is a disaster (too many low level players out there). Vision can be used to make take good decision, but lack of vision should not be used to make stupid decision.
Edited by tragula on Sep 10, 2009 14:45:13
 
Captain Kaos
offline
Link
 
Originally posted by tragula

Why is that relevant ? Obviously a good FB would not do that. But the FB had passed a vision check to change his path and made him go toward his own goaline, that vision check should never be there.

A bad build can result in not making a change of path (low vision), being too late (low speed) or overshooting his target (low agility). Vision check that makes a player decide to go into a wrong direction are bad to the game.
Sure in RL stupid players do awful things (I can tell you mine), but for GLB stupidity is a disaster (too many low level players out there). Vision can be used to make take good decision, but lack of vision should not be used to make stupid decision.


Well pretty much exactly why you stated. FB may have been way too slow to make the lead block. Fortunately, I just happened to run that same exact play on the test server for play diagram accuracy.

http://test.goallineblitz.com/game/game.pl?game_id=1401

Cincinnati Terror was set to run it 100%. I noticed 1 play where that same exact thing was noticeable: http://test.goallineblitz.com/game/replay.pl?game_id=1401&pbp_id=304553

To me, it looks more like a speed/agility issue and not a bug. The rest of the game, the FB seemed to make the blocks every time.

Input is welcome.
 
TrevJo
offline
Link
 
That's awful. Reminds me of this stupid pathing by my FS today, trying to track down a speedy punt returner.
http://goallineblitz.com/game/replay.pl?game_id=713923&pbp_id=13792553
Give me a flippin break! He gets somewhat close to him and then runs straight back 5 yards!! Terrible.
 
TrevJo
offline
Link
 
Originally posted by cwisler
Cincinnati Terror was set to run it 100%. I noticed 1 play where that same exact thing was noticeable: http://test.goallineblitz.com/game/replay.pl?game_id=1401&pbp_id=304553

To me, it looks more like a speed/agility issue and not a bug. The rest of the game, the FB seemed to make the blocks every time.

Input is welcome.


It's a bug. It's triggered by a speed/agility issue, but it's a bug. There is no way in hell the player should be doing that.
 
Captain Kaos
offline
Link
 
Originally posted by TrevJo
That's awful. Reminds me of this stupid pathing by my FS today, trying to track down a speedy punt returner.
http://goallineblitz.com/game/replay.pl?game_id=713923&pbp_id=13792553
Give me a flippin break! He gets somewhat close to him and then runs straight back 5 yards!! Terrible.


Looks like all the players follow the FS's lead. Imo, it's a different problem. I think this is just more about lack of speed/agility on the FBs part by the time he passes his vision check.

In your situation, I think that deals with more of a pathing issue for tackling. Mind making a new post for this and titling it something like "Tackling Pathing Issue"? Thanks!
 
tragula
title
offline
Link
 
Originally posted by TrevJo
It's a bug. It's triggered by a speed/agility issue, but it's a bug. There is no way in hell the player should be doing that.


This.

Vision should not be an issue either.
 
TrevJo
offline
Link
 
Originally posted by cwisler
Originally posted by TrevJo

That's awful. Reminds me of this stupid pathing by my FS today, trying to track down a speedy punt returner.
http://goallineblitz.com/game/replay.pl?game_id=713923&pbp_id=13792553
Give me a flippin break! He gets somewhat close to him and then runs straight back 5 yards!! Terrible.


Looks like all the players follow the FS's lead. Imo, it's a different problem. I think this is just more about lack of speed/agility on the FBs part by the time he passes his vision check.

In your situation, I think that deals with more of a pathing issue for tackling. Mind making a new post for this and titling it something like "Tackling Pathing Issue"? Thanks!


It seems to me that in both cases, the player suddenly decides that he doesn't have the speed/agility for the angle he was going at, and takes a backwards angle instead.

I understand what you're saying about this being due to the FB's speed/agility but there is still NO advantage for him to move backwards and out of the way of the HB like that.
Edited by TrevJo on Sep 10, 2009 15:25:24
 
Captain Kaos
offline
Link
 
Originally posted by TrevJo
Originally posted by cwisler

Cincinnati Terror was set to run it 100%. I noticed 1 play where that same exact thing was noticeable: http://test.goallineblitz.com/game/replay.pl?game_id=1401&pbp_id=304553

To me, it looks more like a speed/agility issue and not a bug. The rest of the game, the FB seemed to make the blocks every time.

Input is welcome.


It's a bug. It's triggered by a speed/agility issue, but it's a bug. There is no way in hell the player should be doing that.


I can see how one can interpret it as a bug. If we could find more instances of this with a FB that has higher speed, agility, and vision -- that'd be great. The more examples I have, the better of an idea I have on what to test to see how the blocking pathing could be fixed to not go in reverse. I think a lot of stuff at Pee Wee looks sloppy to begin with because of how under-developed the players are.

I don't know how the blocking is coded, so I don't know how major a change like that would be. The play looks horrible, but I personally think the only effect it would have on the play is if the HB broke the first tackle.

This is how I see the play break down:
FB begins vision check for 'top threat' to lead block. By the time he passes that vision check, his lead block is out of reach. Therefore his pathing is towards his own endzone because that would be the ideal 'block' intersection. The FB didn't have enough speed and agility to block ahead of the HB because he couldn't meet up with the SS any time before that intersection spot behind the HB. The SS could have continued moving left to avoid the FB's block.

tl;dr version
Could be considered a bug. Would be nice to have blocking paths fixed to not go behind the ball carrier. I'm unsure how much of an effect it would have on other blocking logic.
 
TrevJo
offline
Link
 
Originally posted by cwisler
I don't know how the blocking is coded, so I don't know how major a change like that would be. The play looks horrible, but I personally think the only effect it would have on the play is if the HB broke the first tackle.


On the test server play, it probably didn't matter what the FB did.
On the play in the OP, the only reason the HB got hit in the first place was because the FB moved out of the SS's way.

Originally posted by cwisler
This is how I see the play break down:
FB begins vision check for 'top threat' to lead block. By the time he passes that vision check, his lead block is out of reach. Therefore his pathing is towards his own endzone because that would be the ideal 'block' intersection. The FB didn't have enough speed and agility to block ahead of the HB because he couldn't meet up with the SS any time before that intersection spot behind the HB. The SS could have continued moving left to avoid the FB's block.


Yes, I think that is probably what happened on the play. Thinking about it further, I suppose maybe you could argue that a really dumb FB (i.e. 10 vision) might be stupid enough to do that in a real game.
 
Captain Kaos
offline
Link
 
Originally posted by TrevJo
Yes, I think that is probably what happened on the play. Thinking about it further, I suppose maybe you could argue that a really dumb FB (i.e. 10 vision) might be stupid enough to do that in a real game.


I lol'd. But yeah, the more examples the better. Once we collect more examples of it, we can deem it as a 'bug' and do what's needed. I hate telling you guys that there's not enough info, but you have to understand that it could be due to a build problem or failed vision check -- so to rule that out for sure we need more examples.
 
Page:
 


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