User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Medium Coverage pushes me over the edge
Page:
 
Bukowski
offline
Link
 
Originally posted by Bort
Now that I think about it, It really sounds like people want to be able to go in and try to break up passes every time without the risk of getting beat, which isn't necessarily the best option for game balance. There does need to be a risk/reward kinda thing.


Well.. But it should be less of a risk than going for the INT.

There should be two different levels of a penalty.

But how many times do you see a CB, attempt to just break up a pass, but still get beat? Not often.

CBs often whiff on picking off the pass, but not so much in going for the PD. The CB can usually tell whether or not he can knock the pass down, without letting himself be put in a position to get beaten.

It will happen sometimes, I know, but it should happen less when going for the PD.
Last edited Nov 28, 2008 21:03:23
 
tautology
offline
Link
 
Originally posted by Bort
Originally posted by tautology

So just to be clear, you are saying that was foremrly no essential difference between Aggressive and Medium settings? (I ask because it seemed to me that there was...)


As far as deciding when to go for the ball, yep, it was the same code block getting activated. I'm not sure if that bug has been there all along or not, but it definitely was not working as intended.

There's a couple other differences relating to reaction time and bonuses/penalties, etc, but as far as the AI logic for player movement it was doing the same thing.


Hmmm, well after several seasons of experimenting, it seems that I had my CBs very well tuned for what was formerly the Medium setting. They do not seem to perform as well under the Aggressive setting.

Others seem to be experiencing the same issue...

The behavior that we (or I) are seeking, seemed to have found, was having the CB contest every catch, but not take a big risk by jumping way in front of the coverage...Aggressive seems from experience much more likely to leave you hanging in the breeze 4 yards in front of the WR. I want my guy to basically try to go up for every ball and deflect it, but not leave the WR in his attempt to do so.

Possible?
 
Link
 
Originally posted by Bort
Originally posted by vrshah

Bort, it seems like right now there are 9 combined coverage options for DBs as is (3 coverage x 3 INT aggressiveness).

What would a fourth option add that the other three do not?

It seems like you are making coverage more relatable to INT aggressiveness and that is not correct. Coverage should be how tight a CB sticks to a WR not how much he wants to make a play on the ball.

Coverage (loose,medium,tight) should be based on agility and somewhat vision whereas INT aggressiveness should be vision,jumping et. al.

Your definition of coverage as is, is overlapping with INT aggressiveness too much, no?


I suppose I could "create" that fourth option by making it so if you're set to "close" and "aggressive" it would do what I was thinking with a "move to just above the receiver" action or something.


What I think everyone wants is a perfect system where if there is help over the top they will go for the pick and if they miss the pick its a PD.
And if there isn't help over the top then they only go for the PD.

Basically they want a system where the WR is guaranteed to always have a CB right on him.

Then when this gets done you will have a ton of WRs on here yelling that they can never get open.

 
Dacolts
offline
Link
 
Couldn't the style be simplified to:

-Go for the Int
-Go for the Int when help over the top
-Go for the PD
 
islander1
offline
Link
 
Originally posted by Bukowski
Originally posted by islander1

Originally posted by Bukowski


Originally posted by islander1



Originally posted by Bort




Buk, I know what I changed. It was one line of an if statement.

If the defender doesn't go right for the ball, he continues to play as if he were playing coverage on the player, which includes having to have reaction time, etc.

Going for the ball is the same no matter if you're going for a PD or int - he still has to turn and head right at the receiver, which means if he doesn't knock it down he'll likely get beat since he would then have to turn around again as the receiver catches it behind him. Thus the "help over the top" part for medium.


We all know this Bukowski is a serial whiner. Appreciate you posting an explanation.


Is that fucking necessary?

We're trying to get something done.

If you don't like it, get out of the thread.


How about you stop crying about something new every other day. Crying about leaving, crying about not buying more flex, blah blah blah blah blah.

Everything that doesnt go your way ends up in a bug thread. It's comical.


And everything that is a bug, turns into you bashing everyone that tries to get the SIM fixed.

Why do you troll this forum, if you despise it so much?

Why are you even wasting your time in this thread, if you're so much against it?

You bash anyone that ever has anything to say, other than GLB is perfect. You really should apply for moderator status, you would fit right in.


Not everyone. Just you atm. Here's an idea. How about you improve your own understanding of the game, because in my experience the more one whines, the more clueless they generally are because they can't figure out workarounds.

Like the babies about screen passes. Wah wah wah. I had like 20 screen passes thrown against me today. At least 15 of them went for 5 yards or less.
But wait! It's gamebreaking. No, DC stupidity is gamebreaking.
 
vrshah
offline
Link
 
Originally posted by Bort
Originally posted by vrshah

Bort, it seems like right now there are 9 combined coverage options for DBs as is (3 coverage x 3 INT aggressiveness).

What would a fourth option add that the other three do not?

It seems like you are making coverage more relatable to INT aggressiveness and that is not correct. Coverage should be how tight a CB sticks to a WR not how much he wants to make a play on the ball.

Coverage (loose,medium,tight) should be based on agility and somewhat vision whereas INT aggressiveness should be vision,jumping et. al.

Your definition of coverage as is, is overlapping with INT aggressiveness too much, no?


I suppose I could "create" that fourth option by making it so if you're set to "close" and "aggressive" it would do what I was thinking with a "move to just above the receiver" action or something.


Originally posted by Bort
Now that I think about it, It really sounds like people want to be able to go in and try to break up passes every time without the risk of getting beat, which isn't necessarily the best option for game balance. There does need to be a risk/reward kinda thing.


That's exactly right. If someone wants a PBU or INT on every play, then by all means, set your guys that way but you're liable to get beat. Right now, there isn't a middle ground between receivers getting too open and receivers getting open because the CB is going for the INT. There should be a middle where the CB isn't going for the INT and the WR just can't shake him.

Maybe there is too much overlap between the coding that dictates coverage distance and coverage style? I don't know.
 
Tmracht
offline
Link
 
It more sounds like they want go for the deflection with or without help, rather than go for the INT, which is somewhere between medium and aggressive, you might deflect more but int less but still give up the chance to get beat for a big gain. Not sure how you work that out in the coding, but I think people want more chances to break up the play rather than be forced to go for the INT.
 
Link
 
Originally posted by Dacolts
Couldn't the style be simplified to:

-Go for the Int
-Go for the Int when help over the top
-Go for the PD


What would be the reason to ever use go for the INT or go for the PD?
 
Dacolts
offline
Link
 
Originally posted by sirallan
Originally posted by Dacolts

Couldn't the style be simplified to:

-Go for the Int
-Go for the Int when help over the top
-Go for the PD


What would be the reason to ever use go for the INT or go for the PD?


Percent success rate changes. Int is lower, PD is higher.
 
Yellow
offline
Link
 
Bort i really have to say that you're wrong on this.

Look at my CB playing on Medium/Aggressive compared to Medium/Medium, both before you changed the Medium coverage style code.

Medium/Medium:
http://goallineblitz.com/game/replay.pl?game_id=224710&pbp_id=5380381
http://goallineblitz.com/game/replay.pl?game_id=224710&pbp_id=5378031
http://goallineblitz.com/game/replay.pl?game_id=224680&pbp_id=3461400
http://goallineblitz.com/game/replay.pl?game_id=224680&pbp_id=3462990

Medium/Aggressive:
http://goallineblitz.com/game/replay.pl?game_id=224712&pbp_id=6667359
http://goallineblitz.com/game/replay.pl?game_id=224712&pbp_id=6665889


My CB behaves entirely different under each setting. On Medium/Medium, he hangs back on the ball and stays close to the WR, to get the PD, whereas on Medium/Aggressive, he darts forward to make a play on the ball, often leaving separation between himself and the WR.

I really don't see how you can say that CBs were behaving the same on Aggressive as they were on Medium, as i've seen a ton of evidence to prove otherwise. I have 3 CBs and i have experimented with just about every different coverage combination, and Aggressive and Medium have always performed differently.
 
tautology
offline
Link
 
Originally posted by Bort
Now that I think about it, It really sounds like people want to be able to go in and try to break up passes every time without the risk of getting beat, which isn't necessarily the best option for game balance. There does need to be a risk/reward kinda thing.

In RL, if a CB dives in and tries to break up the pass, he could easily fall down or miss it and fly past, etc.


Well, generally speaking completion percentages seem awfully high, and good WRs are catching quite well in tight coverage.

I don't think anyone wants anything more effective or powerful than we had before...frankly I just want the exact same settings back as an option.
Other folks felt that setting was too risky, so apparently there is some inherent balance in it?
 
Bukowski
offline
Link
 
Originally posted by islander1
Originally posted by Bukowski

Originally posted by islander1


Originally posted by Bukowski



Originally posted by islander1




Originally posted by Bort





Buk, I know what I changed. It was one line of an if statement.

If the defender doesn't go right for the ball, he continues to play as if he were playing coverage on the player, which includes having to have reaction time, etc.

Going for the ball is the same no matter if you're going for a PD or int - he still has to turn and head right at the receiver, which means if he doesn't knock it down he'll likely get beat since he would then have to turn around again as the receiver catches it behind him. Thus the "help over the top" part for medium.


We all know this Bukowski is a serial whiner. Appreciate you posting an explanation.


Is that fucking necessary?

We're trying to get something done.

If you don't like it, get out of the thread.


How about you stop crying about something new every other day. Crying about leaving, crying about not buying more flex, blah blah blah blah blah.

Everything that doesnt go your way ends up in a bug thread. It's comical.


And everything that is a bug, turns into you bashing everyone that tries to get the SIM fixed.

Why do you troll this forum, if you despise it so much?

Why are you even wasting your time in this thread, if you're so much against it?

You bash anyone that ever has anything to say, other than GLB is perfect. You really should apply for moderator status, you would fit right in.


Not everyone. Just you atm. Here's an idea. How about you improve your own understanding of the game, because in my experience the more one whines, the more clueless they generally are because they can't figure out workarounds.

Like the babies about screen passes. Wah wah wah. I had like 20 screen passes thrown against me today. At least 15 of them went for 5 yards or less.
But wait! It's gamebreaking. No, DC stupidity is gamebreaking.


Funny.. The team that I co-own has been a huge success.

Go look at the teams I GM for, there is nothing but winners.

I know how to build players, which is why I notice when things get altered in the middle of the season, like this. The people that don't care, are usually the people with below-average players, that wouldn't notice a difference either way.

So just go ahead and worry about yourself. I'd rather not be harassed by you, every time I decide to come in the forums.
 
Bort
Admin
offline
Link
 
So maybe a 4th option is the best idea? It'd be easy enough to add; just adjust the same if statement to include it.

"Blanket - try to break up the pass every time, but not for the INT."

Something like that?
 
The Lurker
offline
Link
 
Originally posted by sirallan
Originally posted by Dacolts

Couldn't the style be simplified to:

-Go for the Int
-Go for the Int when help over the top
-Go for the PD


What would be the reason to ever use go for the INT or go for the PD?


+ INT bonus, - PD penalty
No bonus, no penalty
+ PD bonus, - INT penalty
 
vrshah
offline
Link
 
Originally posted by tautology
Originally posted by Bort

Now that I think about it, It really sounds like people want to be able to go in and try to break up passes every time without the risk of getting beat, which isn't necessarily the best option for game balance. There does need to be a risk/reward kinda thing.

In RL, if a CB dives in and tries to break up the pass, he could easily fall down or miss it and fly past, etc.


Well, generally speaking completion percentages seem awfully high, and good WRs are catching quite well in tight coverage.

I don't think anyone wants anything more effective or powerful than we had before...frankly I just want the exact same settings back as an option.
Other folks felt that setting w
as too risky, so apparently there is some inherent balance in it?


The problem is bad WRs are catching into double coverage, and I've seen triple coverage catches also.


 
Page:
 


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