User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Tight coverage isn't tight at all
Page:
 
musky5
offline
Link
 
Originally posted by SteelersInsider
Originally posted by musky5

bump-and-run coverage needs to be added



Agreed. Tight should = bump and run.


If the CB has higher strength than the WR and higher agility (with equal or higher speed than the agility number), then the CB should cause a 1 or 2 second delay to the route.

Likewise, if the WR has higher strength and higher agility (with equal or higher speed than the agility number), then the WR should bump the CB out of the way and be given a 3 yard head start a decent % of the time (say 10-15%).


Example:

CB: 25 strength, 70 speed, 60 agility
WR: 15 strength, 90 speed, 50 agility

This receiver should get bumped a good % of the time if the CB playing tight


Likewise:

CB: 25 strength, 90 speed, 60 agility
WR: 35 strength, 70 speed, 70 agility

This CB should get bumped out of the way a good % of the time if playing the WR tight.


This is a way you could counter pure speed receivers or WEAK CB's



Perfect.
 
NotRippedYet
offline
Link
 
Originally posted by skibodragula
I still say its in the build...I have seen my CB crew stick like white on rice and somedays not..I also have seen monster cb's get roasted by my WR's...its a little of both I think..good idea though


Look back at my post earlier.

My guy:
Speed: 83
Agility: 65
Vision: 51
Jumping: 33

The guy he's covering:
Speed: 46
Agility: 34
Vision: 30
Jumping: 27

If it's build, then I'm not sure exactly what you need to do to keep someone covered.
 
PaqMarq11
makes sense
offline
Link
 
Originally posted by NotRippedYet
Originally posted by skibodragula

I still say its in the build...I have seen my CB crew stick like white on rice and somedays not..I also have seen monster cb's get roasted by my WR's...its a little of both I think..good idea though


Look back at my post earlier.

My guy:
Speed: 83
Agility: 65
Vision: 51
Jumping: 33

The guy he's covering:
Speed: 46
Agility: 34
Vision: 30
Jumping: 27

If it's build, then I'm not sure exactly what you need to do to keep someone covered.


i feel for ripped.

sucks big time to have that matchup and not own the wr

 
NotRippedYet
offline
Link
 
Originally posted by PaqMarq11
Originally posted by NotRippedYet

Originally posted by skibodragula


I still say its in the build...I have seen my CB crew stick like white on rice and somedays not..I also have seen monster cb's get roasted by my WR's...its a little of both I think..good idea though


Look back at my post earlier.

My guy:
Speed: 83
Agility: 65
Vision: 51
Jumping: 33

The guy he's covering:
Speed: 46
Agility: 34
Vision: 30
Jumping: 27

If it's build, then I'm not sure exactly what you need to do to keep someone covered.


i feel for ripped.

sucks big time to have that matchup and not own the wr



Actually that's my LB, so he was on the TE, but thanks. It's just kind of a "what's the point?" moment I guess.
 
Bort
Admin
offline
Link
 
Update: I put in a couple changes on the logic for finding the middle ground for coverage last night. Looks better from what I've seen?
 
DM
offline
Link
 
hi Bort
 
UmYeah
offline
Link
 
Originally posted by musky5
Originally posted by SteelersInsider

Originally posted by musky5


bump-and-run coverage needs to be added



Agreed. Tight should = bump and run.


If the CB has higher strength than the WR and higher agility (with equal or higher speed than the agility number), then the CB should cause a 1 or 2 second delay to the route.

Likewise, if the WR has higher strength and higher agility (with equal or higher speed than the agility number), then the WR should bump the CB out of the way and be given a 3 yard head start a decent % of the time (say 10-15%).


Example:

CB: 25 strength, 70 speed, 60 agility
WR: 15 strength, 90 speed, 50 agility

This receiver should get bumped a good % of the time if the CB playing tight


Likewise:

CB: 25 strength, 90 speed, 60 agility
WR: 35 strength, 70 speed, 70 agility

This CB should get bumped out of the way a good % of the time if playing the WR tight.


This is a way you could counter pure speed receivers or WEAK CB's



Perfect.


I think the problem with this is that bump and run isnt a tactic used throughout the game. It is used on a play by play basis. If a CB is playing bump and run all game, in most cases he is going to get burned a few times.
 
markhehe
offline
Link
 
exactly i seen this same thing...let our Corners play close.....

lol....he said, i "seen" the same thing.
 
NotRippedYet
offline
Link
 
Originally posted by UmYeah
Originally posted by musky5

Originally posted by SteelersInsider


Originally posted by musky5



bump-and-run coverage needs to be added



Agreed. Tight should = bump and run.


If the CB has higher strength than the WR and higher agility (with equal or higher speed than the agility number), then the CB should cause a 1 or 2 second delay to the route.

Likewise, if the WR has higher strength and higher agility (with equal or higher speed than the agility number), then the WR should bump the CB out of the way and be given a 3 yard head start a decent % of the time (say 10-15%).


Example:

CB: 25 strength, 70 speed, 60 agility
WR: 15 strength, 90 speed, 50 agility

This receiver should get bumped a good % of the time if the CB playing tight


Likewise:

CB: 25 strength, 90 speed, 60 agility
WR: 35 strength, 70 speed, 70 agility

This CB should get bumped out of the way a good % of the time if playing the WR tight.


This is a way you could counter pure speed receivers or WEAK CB's



Perfect.


I think the problem with this is that bump and run isnt a tactic used throughout the game. It is used on a play by play basis. If a CB is playing bump and run all game, in most cases he is going to get burned a few times.


Yeah, if you play and try to bump every single time you're going to get burned on it.
 
bootyslayer4
offline
Link
 
Originally posted by Bort
Update: I put in a couple changes on the logic for finding the middle ground for coverage last night. Looks better from what I've seen?


Still a little far for me...
http://goallineblitz.com/game/replay.pl?game_id=267529&pbp_id=704142
Should be dot on dot when "Sticking to man like glue" because if choosing that there has to be the risk of getting beat. Thats what should happen.
Last edited Nov 9, 2008 13:18:27
 
TtD
offline
Link
 
Best performance i've seen from my CB in seasons, so fairly happy here. Curious to know how others are doing, as neither team has thrown above 50% against my teams today.
 
TCR
offline
Link
 
I agree todays game was like night and day.This was the best I have seen my CB's perform in two seasons.
 
cornerbackX24
offline
Link
 
So GT-Texans and TtD you both played on close/agressive?

My guy got torched in the first scrimmage game with these settings, therefor I decided to switch to close/medium. Worked out pretty well.
 
Modok
offline
Link
 
I agree, was much better.
 
Joebarber
offline
Link
 
I feel like the CBs aren't making a break on the ball like they were last season
 
Page:
 


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