So R8, was there a change in coding to get the Gs to realize a blitz was happening or was it something else?
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Huge bug: Guards not blocking Safeties in Shotgun 5-wide
Raid
offline
offline
yeah they need to stop leaving that huge gap, It is not looking like a problem with blocking (those safties are pulling some agile moves only they can) it's more of a pocket form, with those DEs going all the way back and dragging those OTs as far back as they do the saefties are having lot of room to pull a quick juke and use that speed to get around the fat/slow Gs fairly easily... that's why we are seeing these kind of plays from where the safeties are starting further back from the line is the amount of time the DEs are given to shift the OT back, the Gs should be making vision checks and moving a little further back and splitting the gap better to pick up those blitzes.
It's probably the new emphasis on the pocket that bort updated, it's actually much better at picking up LB blitzes but those Safeties are having time to get to full stride and have a huge gap to shoot if they can just fein a little to the inside then do a quick cut out and around. The G's don't even see it coming.
It's probably the new emphasis on the pocket that bort updated, it's actually much better at picking up LB blitzes but those Safeties are having time to get to full stride and have a huge gap to shoot if they can just fein a little to the inside then do a quick cut out and around. The G's don't even see it coming.
Raid
offline
offline
the one major problem with having them taking the middle ground of that large gap is that then if the C gets pancaked there is nothing stopping that NT from creaming that QB, so possibly they need to move a little out and actuall back some, this collapses the pocket a little faster than we might want, but it should buy time for the now single covered WRs to find a way to get open for a big gain.
billbillson
offline
offline
Or they can just figure out how to get the guard to block the SS? If a G can't see a SS blitz from the second level and take a step or two to the right, he shouldn't even be playing. Also, the people who say the SS can throw a quick juke and use speed to get around the G is really reaching. We're talking about a difference of less than 10 agility between top tier guards and SS. This big of a difference should be completely offset in the 60+ difference in strength and the huge blocking bars of the G. It's ridiculous and completely unreaslistic that a G can't lay a finger on a SS when he's not blocking anybody and the amount of rushers is less than the amount of blockers. It's not even that the SS is getting through with an overloaded blitz.
Raid
offline
offline
Originally posted by billbillson
Or they can just figure out how to get the guard to block the SS? If a G can't see a SS blitz from the second level and take a step or two to the right, he shouldn't even be playing. Also, the people who say the SS can throw a quick juke and use speed to get around the G is really reaching. We're talking about a difference of less than 10 agility between top tier guards and SS. This big of a difference should be completely offset in the 60+ difference in strength and the huge blocking bars of the G. It's ridiculous and completely unreaslistic that a G can't lay a finger on a SS when he's not blocking anybody and the amount of rushers is less than the amount of blockers. It's not even that the SS is getting through with an overloaded blitz.
the thing is he sees him coming, every single one of those plays if you slow it down and look the G is standing directly in the path of where the SS or FS is blitzing, it is just that they change to a more outside route right before getting to the G and go around them. It's not a problem in the blocking it is a problem in pocket logic, he needs to be guarding that hoe better instead of trying to get in front of the SS since he could not possibly match up with that players speed/agility.
Edit: and on the plays where the G ends up having to help out the C take the NT it is also a problem, if they didn't it would be a sack anyhow... it's kind of a hard thing to deal with unless your C can move with the NT and leave the Gs to pick up blitzes...
it needs to be worked out somehow but this is actually very complex in how to fix it without doing a nerf to the d-linemen or safeties on blitzes... I've seen similar problems with the g trying to support the C when he needs to be picking up the blitz... so possibly they could have a higher importance placed on the blitz pickup as well (since Gs are usually responsible for it on 5wide sets) but this could also cause more sacks by the NT, though I think it would help to buy more time than helping the C out and letting a safety go by unabated to the QB.
the pocket logic needs to be reworked much deeper than you are trying to make it sound.
Or they can just figure out how to get the guard to block the SS? If a G can't see a SS blitz from the second level and take a step or two to the right, he shouldn't even be playing. Also, the people who say the SS can throw a quick juke and use speed to get around the G is really reaching. We're talking about a difference of less than 10 agility between top tier guards and SS. This big of a difference should be completely offset in the 60+ difference in strength and the huge blocking bars of the G. It's ridiculous and completely unreaslistic that a G can't lay a finger on a SS when he's not blocking anybody and the amount of rushers is less than the amount of blockers. It's not even that the SS is getting through with an overloaded blitz.
the thing is he sees him coming, every single one of those plays if you slow it down and look the G is standing directly in the path of where the SS or FS is blitzing, it is just that they change to a more outside route right before getting to the G and go around them. It's not a problem in the blocking it is a problem in pocket logic, he needs to be guarding that hoe better instead of trying to get in front of the SS since he could not possibly match up with that players speed/agility.
Edit: and on the plays where the G ends up having to help out the C take the NT it is also a problem, if they didn't it would be a sack anyhow... it's kind of a hard thing to deal with unless your C can move with the NT and leave the Gs to pick up blitzes...
it needs to be worked out somehow but this is actually very complex in how to fix it without doing a nerf to the d-linemen or safeties on blitzes... I've seen similar problems with the g trying to support the C when he needs to be picking up the blitz... so possibly they could have a higher importance placed on the blitz pickup as well (since Gs are usually responsible for it on 5wide sets) but this could also cause more sacks by the NT, though I think it would help to buy more time than helping the C out and letting a safety go by unabated to the QB.
the pocket logic needs to be reworked much deeper than you are trying to make it sound.
Last edited Mar 27, 2009 02:14:26
billbillson
offline
offline
Originally posted by Atatakakunai
the thing is he sees him coming, every single one of those plays if you slow it down and look the G is standing directly in the path of where the SS or FS is blitzing, it is just that they change to a more outside route right before getting to the G and go around them. It's not a problem in the blocking it is a problem in pocket logic, he needs to be guarding that hoe better instead of trying to get in front of the SS since he could not possibly match up with that players speed/agility.
See this bothers me. A lower level OT can easily handle a DE with higher stats but a G can't handle 5-10 more agility and 20 speed? Give me a break. It's bad coding that allows the SS to come in untouched from centerfield. If someone had to run in from centerfield which takes 2-3 seconds and they had to fit into a hole that is only 2 people wide, do you really think they can juke and jive their way right past a G without ever getting touched? It's COMPLETELY UNREALISTIC and the blocking code needs to get better.
the thing is he sees him coming, every single one of those plays if you slow it down and look the G is standing directly in the path of where the SS or FS is blitzing, it is just that they change to a more outside route right before getting to the G and go around them. It's not a problem in the blocking it is a problem in pocket logic, he needs to be guarding that hoe better instead of trying to get in front of the SS since he could not possibly match up with that players speed/agility.
See this bothers me. A lower level OT can easily handle a DE with higher stats but a G can't handle 5-10 more agility and 20 speed? Give me a break. It's bad coding that allows the SS to come in untouched from centerfield. If someone had to run in from centerfield which takes 2-3 seconds and they had to fit into a hole that is only 2 people wide, do you really think they can juke and jive their way right past a G without ever getting touched? It's COMPLETELY UNREALISTIC and the blocking code needs to get better.
VenomCoach
offline
offline
Originally posted by Mstr_October
Yep, Cover 2, no doubt.
oy the first one
http://goallineblitz.com/game/replay.pl?game_id=373855&pbp_id=13674195
may have been cover 2.
Most of those shown are Cov 0. The safety depth gives it away. Cov 2 safeties can't be that tight.
http://goallineblitz.com/game/replay.pl?game_id=373167&pbp_id=5201543
Yep, Cover 2, no doubt.
oy the first one
http://goallineblitz.com/game/replay.pl?game_id=373855&pbp_id=13674195
may have been cover 2.
Most of those shown are Cov 0. The safety depth gives it away. Cov 2 safeties can't be that tight.
http://goallineblitz.com/game/replay.pl?game_id=373167&pbp_id=5201543
Last edited Mar 27, 2009 13:24:16
neoliminal
offline
offline
In five wide you have 5 linemen. With a 4-3 Cover 2, with both safeties blitzing that's 6 on 5. They SHOULD be getting through.
However this is clearly a problem where the Gs are not even trying to fill the gaps. They should be backing up (perpendicular to the LOS) so as to protect against both the NT getting past the center and the safeties. Somewhere equal-distant from the center and tackles.
However this is clearly a problem where the Gs are not even trying to fill the gaps. They should be backing up (perpendicular to the LOS) so as to protect against both the NT getting past the center and the safeties. Somewhere equal-distant from the center and tackles.
Originally posted by Sik Wit It
the Guards all have vision over 50, and some as high as the mid 60s
I'd like to see how G's with low vision react in this situation...
the Guards all have vision over 50, and some as high as the mid 60s
I'd like to see how G's with low vision react in this situation...
islander1
offline
offline
Originally posted by neoliminal
In five wide you have 5 linemen. With a 4-3 Cover 2, with both safeties blitzing that's 6 on 5. They SHOULD be getting through.
However this is clearly a problem where the Gs are not even trying to fill the gaps. They should be backing up (perpendicular to the LOS) so as to protect against both the NT getting past the center and the safeties. Somewhere equal-distant from the center and tackles.
The Wolfpack have seen situations where a LG is completely free - not blocking a soul - having 60+ vision and 80 agility and STILL watching the FS waltz right past him.
In five wide you have 5 linemen. With a 4-3 Cover 2, with both safeties blitzing that's 6 on 5. They SHOULD be getting through.
However this is clearly a problem where the Gs are not even trying to fill the gaps. They should be backing up (perpendicular to the LOS) so as to protect against both the NT getting past the center and the safeties. Somewhere equal-distant from the center and tackles.
The Wolfpack have seen situations where a LG is completely free - not blocking a soul - having 60+ vision and 80 agility and STILL watching the FS waltz right past him.
tonynf89
offline
offline
Originally posted by Sik Wit It
Originally posted by Mat McBriar
I've always attributed it to a vision deficiency among the Gs, including when it's happened to us. The safeties just come in too fast for the Gs to pick them up. I suppose you'd remedy that with more vision, agility, and speed.
I guess what I'm saying is this should go to the test server just to see if it's consistent, even with outrageous builds. See if it's something that's build related or directly related to the blocking coding itself.
I guess that could be argued. But take this replay for instance:
http://goallineblitz.com/game/replay.pl?game_id=373162&pbp_id=12669603
The G is in perfect position to block, but but a block is never initiated. The G has 60+ vision, 60+ speed, 70+ agility. I know that's nowhere near what the Safety probably has, but should be enough to pick up a blitz. I mean asking Gs to have strength & blocking to fend off DTs, and as much speed/agility as someone in the secondary is a little much.
Edit: But yes, I agree it is definitely something to be tested on the test server.
Um, when the FS probably has 90+ spd, 80+agi, don't be surprised if he can juke around him. Don't tell me you've never seen a guard get flat out beat IRL before. Just because your G missed a block on that particular play doesn't mean he'll miss it everytime. nukka just got juked. Now if they go to the test server and find that the block is being missed an extraordinarily unusual amount of times, then yeah the coding needs to be adjusted.
Depending on the situation, I can see a play like this realistically happening IRL like 2/6 times.
It's football, you don't win every battle. Some of the plays do look fishy though, something might be up with the pathing. A lot of them it looks like the G is just too slow to react and get into position to block.
Originally posted by Mat McBriar
I've always attributed it to a vision deficiency among the Gs, including when it's happened to us. The safeties just come in too fast for the Gs to pick them up. I suppose you'd remedy that with more vision, agility, and speed.
I guess what I'm saying is this should go to the test server just to see if it's consistent, even with outrageous builds. See if it's something that's build related or directly related to the blocking coding itself.
I guess that could be argued. But take this replay for instance:
http://goallineblitz.com/game/replay.pl?game_id=373162&pbp_id=12669603
The G is in perfect position to block, but but a block is never initiated. The G has 60+ vision, 60+ speed, 70+ agility. I know that's nowhere near what the Safety probably has, but should be enough to pick up a blitz. I mean asking Gs to have strength & blocking to fend off DTs, and as much speed/agility as someone in the secondary is a little much.
Edit: But yes, I agree it is definitely something to be tested on the test server.
Um, when the FS probably has 90+ spd, 80+agi, don't be surprised if he can juke around him. Don't tell me you've never seen a guard get flat out beat IRL before. Just because your G missed a block on that particular play doesn't mean he'll miss it everytime. nukka just got juked. Now if they go to the test server and find that the block is being missed an extraordinarily unusual amount of times, then yeah the coding needs to be adjusted.
Depending on the situation, I can see a play like this realistically happening IRL like 2/6 times.
It's football, you don't win every battle. Some of the plays do look fishy though, something might be up with the pathing. A lot of them it looks like the G is just too slow to react and get into position to block.
Last edited Apr 15, 2009 12:15:21
islander1
offline
offline
Originally posted by tonynf89
Originally posted by Sik Wit It
Originally posted by Mat McBriar
I've always attributed it to a vision deficiency among the Gs, including when it's happened to us. The safeties just come in too fast for the Gs to pick them up. I suppose you'd remedy that with more vision, agility, and speed.
I guess what I'm saying is this should go to the test server just to see if it's consistent, even with outrageous builds. See if it's something that's build related or directly related to the blocking coding itself.
I guess that could be argued. But take this replay for instance:
http://goallineblitz.com/game/replay.pl?game_id=373162&pbp_id=12669603
The G is in perfect position to block, but but a block is never initiated. The G has 60+ vision, 60+ speed, 70+ agility. I know that's nowhere near what the Safety probably has, but should be enough to pick up a blitz. I mean asking Gs to have strength & blocking to fend off DTs, and as much speed/agility as someone in the secondary is a little much.
Edit: But yes, I agree it is definitely something to be tested on the test server.
Um, when the FS probably has 90+ spd, 80+agi, don't be surprised if he can juke around him. Don't tell me you've never seen a guard get flat out beat IRL before. Just because your G missed a block on that particular play doesn't mean he'll miss it everytime. nukka just got juked. Now if they go to the test server and find that the block is being missed an extraordinarily unusual amount of times, then yeah the coding needs to be adjusted.
Depending on the situation, I can see a play like this realistically happening IRL like 2/6 times.
It's football, you don't win every battle. Some of the plays do look fishy though, something might be up with the pathing. A lot of them it looks like the G is just too slow to react and get into position to block.
It's definitely a pathing issue. I'd understand if the safety got around the guard pretty quickly (shakes the block in a second), but the way it happens with hyper fast safeties is clearly (to me) a pathing issue. I know someone who experimented with like 90 agility on a guard and that seemed to 'stop' the safety from cleanly going around - but to me that's utterly ridiculous and more of a break fix then something that should be a realistic requirement of a guard.
Originally posted by Sik Wit It
Originally posted by Mat McBriar
I've always attributed it to a vision deficiency among the Gs, including when it's happened to us. The safeties just come in too fast for the Gs to pick them up. I suppose you'd remedy that with more vision, agility, and speed.
I guess what I'm saying is this should go to the test server just to see if it's consistent, even with outrageous builds. See if it's something that's build related or directly related to the blocking coding itself.
I guess that could be argued. But take this replay for instance:
http://goallineblitz.com/game/replay.pl?game_id=373162&pbp_id=12669603
The G is in perfect position to block, but but a block is never initiated. The G has 60+ vision, 60+ speed, 70+ agility. I know that's nowhere near what the Safety probably has, but should be enough to pick up a blitz. I mean asking Gs to have strength & blocking to fend off DTs, and as much speed/agility as someone in the secondary is a little much.
Edit: But yes, I agree it is definitely something to be tested on the test server.
Um, when the FS probably has 90+ spd, 80+agi, don't be surprised if he can juke around him. Don't tell me you've never seen a guard get flat out beat IRL before. Just because your G missed a block on that particular play doesn't mean he'll miss it everytime. nukka just got juked. Now if they go to the test server and find that the block is being missed an extraordinarily unusual amount of times, then yeah the coding needs to be adjusted.
Depending on the situation, I can see a play like this realistically happening IRL like 2/6 times.
It's football, you don't win every battle. Some of the plays do look fishy though, something might be up with the pathing. A lot of them it looks like the G is just too slow to react and get into position to block.
It's definitely a pathing issue. I'd understand if the safety got around the guard pretty quickly (shakes the block in a second), but the way it happens with hyper fast safeties is clearly (to me) a pathing issue. I know someone who experimented with like 90 agility on a guard and that seemed to 'stop' the safety from cleanly going around - but to me that's utterly ridiculous and more of a break fix then something that should be a realistic requirement of a guard.
Last edited Apr 15, 2009 12:21:21
Raid
offline
offline
Testing currently shows this to be of little problem anymore and the blocking has had an overhaul this season really.
Thanks for reminding us of something we fixed a while ago though.

Thanks for reminding us of something we fixed a while ago though.

Modok
offline
offline
Originally posted by billbillson
Or they can just figure out how to get the guard to block the SS? If a G can't see a SS blitz from the second level and take a step or two to the right, he shouldn't even be playing. Also, the people who say the SS can throw a quick juke and use speed to get around the G is really reaching. We're talking about a difference of less than 10 agility between top tier guards and SS. This big of a difference should be completely offset in the 60+ difference in strength and the huge blocking bars of the G. It's ridiculous and completely unreaslistic that a G can't lay a finger on a SS when he's not blocking anybody and the amount of rushers is less than the amount of blockers. It's not even that the SS is getting through with an overloaded blitz.
The bolded part is what is wrong with this game.
Or they can just figure out how to get the guard to block the SS? If a G can't see a SS blitz from the second level and take a step or two to the right, he shouldn't even be playing. Also, the people who say the SS can throw a quick juke and use speed to get around the G is really reaching. We're talking about a difference of less than 10 agility between top tier guards and SS. This big of a difference should be completely offset in the 60+ difference in strength and the huge blocking bars of the G. It's ridiculous and completely unreaslistic that a G can't lay a finger on a SS when he's not blocking anybody and the amount of rushers is less than the amount of blockers. It's not even that the SS is getting through with an overloaded blitz.
The bolded part is what is wrong with this game.
You are not logged in. Please log in if you want to post a reply.





























