User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > This is bothering me about CB coverage.
Page:
 
jsully75
offline
Link
 
Tell me if I am wrong or off base here, the fix is not what bothered me, but made me think about how my CB's play and how they are built.

- Fix to random occasional bug where defender's max speed was limited to the speed of the player he was covering after the ball is caught by someone else

So basically, what happens now is that a CB's speed is adjusted to match that of the player he is defending. I remember when this wasn't the case and it was a problem 3 or 4 seasons ago when "fast" CB's would just run away from slow WR and leave them open, you could build really slow WR and they would be open often. This was later fixed by limiting the CB speed. I never considered this to be a problem until this season. This season it seems to be much easier for a WR to fake out a guy and gain a few steps on a CB. The problem is, if a CB has 100 speed and the WR has 70 speed it doesn't matter, the faked out CB CAN NOT catch the guy because his speed has been limited.

Now I hate to do the "In real life" comparisons since we always here the same "well, this is GLB, not real life", but in real life a really fast corner, i.e. Dion Sanders, could risk falling for a fake early in a route because he was fast enough to catch up to the guy, he speed is not limited to that of the receiver. It seems to me watching replays when a CB falls for a fake early, no matter how fast he is, he can never catch the WR, in fact, if you have a really fast CB he will stay almost the same distance back until the ball is thrown and the WR has to stop to wait for it (which is another issue entirely).
 
Hagalaz
offline
Link
 
WAS limited, not IS. I think it USED TO be limited. At least if my english isn't deceiving me...

The fix is correcting the problem, not making it.
 
5thyearcock
offline
Link
 
Originally posted by Hagalaz
WAS limited, not IS. I think it USED TO be limited. At least if my english isn't deceiving me...

The fix is correcting the problem, not making it.


 
jsully75
offline
Link
 
Originally posted by Hagalaz
WAS limited, not IS. I think it USED TO be limited. At least if my english isn't deceiving me...

The fix is correcting the problem, not making it.


actually no, the fix is ONLY when the ball is caught by another receiver. I am talking about the coverage before the ball is thrown.
 
joe
46 Defense
offline
Link
 
Originally posted by jsully75
Tell me if I am wrong or off base here, the fix is not what bothered me, but made me think about how my CB's play and how they are built.

- Fix to random occasional bug where defender's max speed was limited to the speed of the player he was covering after the ball is caught by someone else

So basically, what happens now is that a CB's speed is adjusted to match that of the player he is defending. I remember when this wasn't the case and it was a problem 3 or 4 seasons ago when "fast" CB's would just run away from slow WR and leave them open, you could build really slow WR and they would be open often. This was later fixed by limiting the CB speed. I never considered this to be a problem until this season. This season it seems to be much easier for a WR to fake out a guy and gain a few steps on a CB. The problem is, if a CB has 100 speed and the WR has 70 speed it doesn't matter, the faked out CB CAN NOT catch the guy because his speed has been limited.

Now I hate to do the "In real life" comparisons since we always here the same "well, this is GLB, not real life", but in real life a really fast corner, i.e. Dion Sanders, could risk falling for a fake early in a route because he was fast enough to catch up to the guy, he speed is not limited to that of the receiver. It seems to me watching replays when a CB falls for a fake early, no matter how fast he is, he can never catch the WR, in fact, if you have a really fast CB he will stay almost the same distance back until the ball is thrown and the WR has to stop to wait for it (which is another issue entirely).


I think you are on to something here. I agree 100%.
 
kurieg
offline
Link
 
Originally posted by Hagalaz
WAS limited, not IS. I think it USED TO be limited. At least if my english isn't deceiving me...

The fix is correcting the problem, not making it.


No, the fix is adjusting what happens after a catch is made.


The OP is talking about a CB in coverage (i.e., before a throw is made).

It's a very interesting question, actually.
 
jsully75
offline
Link
 
Originally posted by 5thyearcock
Originally posted by Hagalaz

WAS limited, not IS. I think it USED TO be limited. At least if my english isn't deceiving me...

The fix is correcting the problem, not making it.




You obviously have a lacking in the english language as well.

after the ball is caught by someone else
 
jsully75
offline
Link
 
Okay, just started to look for an example, this is incomplete, but the CB here has about 110 speed, so you would think he would be able to catch the guy, but he stays exactly the distance behind (until the ball is thrown and the WR stops of course.)

http://goallineblitz.com/game/replay.pl?game_id=356792&pbp_id=10254635
 
5thyearcock
offline
Link
 
Originally posted by jsully75
Originally posted by 5thyearcock

Originally posted by Hagalaz


WAS limited, not IS. I think it USED TO be limited. At least if my english isn't deceiving me...

The fix is correcting the problem, not making it.




You obviously have a lacking in the english language as well.

after the ball is caught by someone else


Well your post is poorly worded... by following the changelog sentence with "So basically, what happens now is that a CB's speed is adjusted to match that of the player he is defending." it appears you are making a cause and effect statement... like the change made that happen.

Anyways, now I get what you were trying to say(which was basically unrelated to the changelog entry, and could have stood on its own), but you are making an assumption that your CB is forced to move at a certain speed the entire pre-catch. If you are correct in this assumption, this is a MASSIVE flaw in the mechanics of CB coverage and needs to be dealt with, most logically by tying in vision and confidence.
Last edited Jan 26, 2009 08:36:02
 
jsully75
offline
Link
 
Originally posted by 5thyearcock
Originally posted by jsully75

Originally posted by 5thyearcock


Originally posted by Hagalaz



WAS limited, not IS. I think it USED TO be limited. At least if my english isn't deceiving me...

The fix is correcting the problem, not making it.




You obviously have a lacking in the english language as well.

after the ball is caught by someone else


Well your post is poorly worded... by following the changelog sentence with "So basically, what happens now is that a CB's speed is adjusted to match that of the player he is defending." it appears you are making a cause and effect statement... like the change made that happen.

Anyways, now I get what you were trying to say(which was basically unrelated to the changelog entry, and could have stood on its own), but you are making an assumption that your CB is forced to move at a certain speed the entire pre-catch. If you are correct in this assumption, this is a MASSIVE flaw in the mechanics of CB coverage and needs to be dealt with, most logically by tying in vision and confidence.


Think about this next game you watch and you will see what I am talking about, you can see LB's with 100 speed following a slow TE up the field in coverage and never catching him. Watch how the LB stays exactly the same distance away until the ball is throw and the TE slows down:

http://goallineblitz.com/game/replay.pl?game_id=309954&pbp_id=8353035

that LB has 65 agility and 100 speed, in theory, he should be able to catch that LB pretty easily.. I don't know what the TE has, but just watching the play tells me otherwise.
 
5thyearcock
offline
Link
 
Yeah, at the very least, the speed cap should be released when the ball is thrown, or set on a timer based on the CB's vision.

Or if the CB bites on a fake and the WR is going deep, almost all CB's would start full speed for the WR.
 
Guppy, Inc
offline
Link
 
a great example of what really annoys me about any coverage is that the receivers just run by the defenders, stop making the defenders overrun the receivers. players should be "smart" enough to know that they are blind and therefore would keep the receiver in front of them, not rush up and let the receiver run free.
 
mantisman116
offline
Link
 
Originally posted by jsully75
Tell me if I am wrong or off base here, the fix is not what bothered me, but made me think about how my CB's play and how they are built.

- Fix to random occasional bug where defender's max speed was limited to the speed of the player he was covering after the ball is caught by someone else

So basically, what happens now is that a CB's speed is adjusted to match that of the player he is defending. I remember when this wasn't the case and it was a problem 3 or 4 seasons ago when "fast" CB's would just run away from slow WR and leave them open, you could build really slow WR and they would be open often. This was later fixed by limiting the CB speed. I never considered this to be a problem until this season. This season it seems to be much easier for a WR to fake out a guy and gain a few steps on a CB. The problem is, if a CB has 100 speed and the WR has 70 speed it doesn't matter, the faked out CB CAN NOT catch the guy because his speed has been limited.

Now I hate to do the "In real life" comparisons since we always here the same "well, this is GLB, not real life", but in real life a really fast corner, i.e. Dion Sanders, could risk falling for a fake early in a route because he was fast enough to catch up to the guy, he speed is not limited to that of the receiver. It seems to me watching replays when a CB falls for a fake early, no matter how fast he is, he can never catch the WR, in fact, if you have a really fast CB he will stay almost the same distance back until the ball is thrown and the WR has to stop to wait for it (which is another issue entirely).



There's way too much truth in all of this post, IMO.
 
jsully75
offline
Link
 
Originally posted by mantisman116
Originally posted by jsully75

Tell me if I am wrong or off base here, the fix is not what bothered me, but made me think about how my CB's play and how they are built.

- Fix to random occasional bug where defender's max speed was limited to the speed of the player he was covering after the ball is caught by someone else

So basically, what happens now is that a CB's speed is adjusted to match that of the player he is defending. I remember when this wasn't the case and it was a problem 3 or 4 seasons ago when "fast" CB's would just run away from slow WR and leave them open, you could build really slow WR and they would be open often. This was later fixed by limiting the CB speed. I never considered this to be a problem until this season. This season it seems to be much easier for a WR to fake out a guy and gain a few steps on a CB. The problem is, if a CB has 100 speed and the WR has 70 speed it doesn't matter, the faked out CB CAN NOT catch the guy because his speed has been limited.

Now I hate to do the "In real life" comparisons since we always here the same "well, this is GLB, not real life", but in real life a really fast corner, i.e. Dion Sanders, could risk falling for a fake early in a route because he was fast enough to catch up to the guy, he speed is not limited to that of the receiver. It seems to me watching replays when a CB falls for a fake early, no matter how fast he is, he can never catch the WR, in fact, if you have a really fast CB he will stay almost the same distance back until the ball is thrown and the WR has to stop to wait for it (which is another issue entirely).



There's way too much truth in all of this post, IMO.


sorry, last time I swear.
 
FBGBullDozier
offline
Link
 
Originally posted by 5thyearcock
Yeah, at the very least, the speed cap should be released when the ball is thrown, or set on a timer based on the CB's vision.

Or if the CB bites on a fake and the WR is going deep, almost all CB's would start full speed for the WR.


IMO, the CBs speed should only be limited when the distance between the CB and the WR is less than or equal to his distance setting for his coverage style. If he's playing close coverage, if his distance from the WR is greater than "close" his running speed should be full. Once within the "close" range, he speed should be limited to the speed of the WR.

Seems logical to me.
 
Page:
 


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