User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > OL Blocking - We need to get this right! - ARCHIVED #140
Page:
 
rjssob
HOOD
offline
Link
 
Originally posted by Cryptotich
In this case, you don't know the blocking, speed, agility, str of the Center. We have no idea what his capabilities are. We can only see what he did.


Totally irrelavant when you are leaving a DT uncovered. A chip block example would be a RB hitting a DE before he went out on a route, a TE doing the same. For a center it might be chipping a down DL before going to a backer, but nowhere in football would you leave a DL uncovered unless Midline Option was added to the game....
 
suske127
offline
Link
 
Originally posted by rjssob
Originally posted by Cryptotich

In this case, you don't know the blocking, speed, agility, str of the Center. We have no idea what his capabilities are. We can only see what he did.


Totally irrelavant when you are leaving a DT uncovered. A chip block example would be a RB hitting a DE before he went out on a route, a TE doing the same. For a center it might be chipping a down DL before going to a backer, but nowhere in football would you leave a DL uncovered unless Midline Option was added to the game....


it seems like a bug to me
there is a chanse it isnt but it seems likley it is
stillneed a couple more plays though
 
Cryptotich
offline
Link
 
Originally posted by rjssob
The whole premise of the Chip Block would be that the center chipped and went to another defender while the LG stayed home on the NT. You don't chip block a down lineman and then let him go free. This may be working as intended and not a bug, but the principles behind it are not sound football logic for blocking.


You are assuming that the Center has a build that would support the ability to do that.

If the code says chip block, and the center has a 50 agility, he isn't going to make it back to his other block.
 
suske127
offline
Link
 
Originally posted by Cryptotich
Originally posted by rjssob

The whole premise of the Chip Block would be that the center chipped and went to another defender while the LG stayed home on the NT. You don't chip block a down lineman and then let him go free. This may be working as intended and not a bug, but the principles behind it are not sound football logic for blocking.


You are assuming that the Center has a build that would support the ability to do that.

If the code says chip block, and the center has a 50 agility, he isn't going to make it back to his other block.


 
rjssob
HOOD
offline
Link
 
Originally posted by Cryptotich
You are assuming that the Center has a build that would support the ability to do that.

If the code says chip block, and the center has a 50 agility, he isn't going to make it back to his other block.


You are missing the point Crypt, it isn't about the center getting to his next block. It is the fact that on a run to the right you have a LG double teaming a backside end and a center who in your mind is chipping and coming off the DT. The entire point here is that the OL is leaving the DT unblocked...In this example the center had 81 Agility, 131 Strength, 102 Blocking and he was sleeping with the other teams cheerleaders...
 
Cryptotich
offline
Link
 
Originally posted by rjssob
You are missing the point Crypt, it isn't about the center getting to his next block. It is the fact that on a run to the right you have a LG double teaming a backside end and a center who in your mind is chipping and coming off the DT. The entire point here is that the OL is leaving the DT unblocked...In this example the center had 81 Agility, 131 Strength, 102 Blocking and he was sleeping with the other teams cheerleaders...


I can tell you exactly what is happening, but you won't like it. The LG is going to block the nearest defender, who in the case of all your examples is the RDE.

That is what he is doing.

So that brings us to the play definition. In your mind, and I do not dispute this, because the play is going to the right, the LG should block the Center, and not the RDE.. The back side pursuit is irrelevant(at least hopefully).

Good call, I agree. A change would make this play better.



Edited by Cryptotich on Apr 28, 2010 17:59:56
 
suske127
offline
Link
 
Originally posted by Cryptotich
Originally posted by rjssob

You are missing the point Crypt, it isn't about the center getting to his next block. It is the fact that on a run to the right you have a LG double teaming a backside end and a center who in your mind is chipping and coming off the DT. The entire point here is that the OL is leaving the DT unblocked...In this example the center had 81 Agility, 131 Strength, 102 Blocking and he was sleeping with the other teams cheerleaders...


I can tell you exactly what is happening, but you won't like it. The LG is going to block the nearest defender, who in the case of all your examples is the RDE.

That is what he is doing.

So that brings us to the play definition. In your mind, and I do not dispute this, because the play is going to the right, the LG should block the Center, and not the RDE.. The back side pursuit is irrelevant(at least hopefully).

Good call, I agree. A change would make this play better.





 
rjssob
HOOD
offline
Link
 
Yup, I am saying it isn't necessarily a bug because the code is most likely working as designed, it is more a flaw in the requirements as to how the play should be blocked. If I was attempting what is being done here I would do something like this:

LOT - Blocks DE solo
LOG - Pulls around the Center and gets upfield or hits the first defender he sees
Center - Blocks Back to the DT on his left and stays on him
ROG - Takes on NT solo
ROT - Takes on DE to LB

More realistic maybe:
LOT - Blocks DE solo
LOG - Blocks DT solo
Center - Chip DT or NT depending on which way the play is going and get to the 2nd level
ROG - Takes on NT solo
ROT - Takes on DE to LB (depending on where the TE is)

Basically you want your 5 OL to secure the D Line first....Something to think about, hope it helps! Thanks everyone....
 
AngryDragon
offline
Link
 
Is there enough information yet?
 
rjssob
HOOD
offline
Link
 
I can add this twist to it - How do we expect a ROT come all the way across the line of scrimmage to block a blitzing OLB on the opposite side of the field? This is just ridiculous conceptually, maybe it is time to have someone work with the developers that have a strong understanding of OL play and can transform that knowledge into a business requirement.

http://goallineblitz.com/game/replay.pl?game_id=1118602&pbp_id=12988977
 
Cryptotich
offline
Link
 
I think I might understand what is happening. Assuming that everyone on the O-Line makes their vision roll...

Since blocking assignments go inside out... The Center takes the first person across the line. Maybe the DT has more agility, or more first step... but the Center thinks he is the biggest threat, so he moves to block the DT. The LG gets the message that the DT is blocked(or going to be) blocked, and this moves on to the next biggest inside threat, who is the NT(who is slower than the DT). Thus causing a cross between the two.

I think that would explain what happened. The question is that what we should expect? To me, it seemed to work as it should. At least in these plays.


 
rjssob
HOOD
offline
Link
 
The question is that what we should expect?

We should expect that a ROT never, never, never has to block all the way to other side on a pass play!
 
Cryptotich
offline
Link
 
Originally posted by rjssob


http://goallineblitz.com/game/replay.pl?game_id=1118602&pbp_id=12988977


On this play, this is what I see happening. The ROT, thinks for whatever reason that the RG has the LDE blocked. The NT is blocked by the Center, so he looks for the first unblocked man. Which ends up being the RDE because the LG and LOT are moving backwards by the play definition, and have not assigned a block yet.

Right or wrong in the best way to handle it, that is what I see happening.



 
rjssob
HOOD
offline
Link
 
Originally posted by rjssob
The question is that what we should expect?

We should expect that a ROT never, never, never has to block all the way to other side on a pass play! I am agreeing that it may not be a bug, but whoever handed the developer requirements to create blocking schemes should think about getting a book on line blocking schemes.


 
Enkidu98
offline
Link
 
Since this thread is active and I don;t want to create another O-Line blocking thread, just wanted to add this here.

http://goallineblitz.com/game/replay.pl?game_id=1177392&pbp_id=13191555

The OT shouldn;t ever leave a DE unblocked like this, especially when the play call is going their direction. This is casuals, so there is no excuse for this one. Its not an overload, its not a DPC play. Its just bad blocking logic.
 
Page:
 


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