Warrior General Games

I'm not 100% sure how I feel on this topic. Seems we've got a wide variety of what can occur on a screen.

The Defensive play used is definitely causing this issue..

Originally posted by Pwned IRL
I'm not 100% sure how I feel on this topic. Seems we've got a wide variety of what can occur on a screen.

The Defensive play used is definitely causing this issue..

You mean it's causing the issue because CB #1 isn't blocked?

If a player doesn't move because he expects to be blocked when no one is blocking him, wouldn't that be a crystal clear case of a bug?

Originally posted by Rage Kinard
You mean it's causing the issue because CB #1 isn't blocked?

If a player doesn't move because he expects to be blocked when no one is blocking him, wouldn't that be a crystal clear case of a bug?

I think we're on the same page.

Then again we have 0 links of a CB reacting to a screen any differently than what he does in the OP links.

Seems the CB's react slower to screens for whatever reason I don't know, I didn't code it.

I'm going to look into this a bit more tonight when I get home from work and then I'll classify it to get going on this matter.

Rage..

I need the CB tactics and general build. Vision, Agility, etc.

Just need to get as much info as I can for the file so when they test it they have all that they need.

Okay, thanks for submitting that info Rage.

I will file this when I get home as I cannot access Bugzilla from my work computer.

Marking LIKELY A BUG.

FYI - Build information and tactics are in the Bugzilla file.

Mar 28, 2011
- Fix coverage bug causing unintended overpersuing vs FB screen weak and WR screen plays

Only 1 of these replays comes from the 28th and I'm not sure if this went in early or late. I'm thinking we need to see some new ones before we say it is a bug.

Originally posted by Androth
Mar 28, 2011
- Fix coverage bug causing unintended overpersuing vs FB screen weak and WR screen plays

Only 1 of these replays comes from the 28th and I'm not sure if this went in early or late. I'm thinking we need to see some new ones before we say it is a bug.

The CB in question is NOT pursuing his assignment, instead he is waiting to be blocked.

That's why I made the determination of it being a bug.

I have battled this issue some too

Can it be the way the vision checks work?

CB1 in Rages plays, is set to cover wr1 - but reads the screens as "receiver not going into route" - hence defaults to zone?

Not saying this is desirable - actually quite the opposite - but could it be the mechanics of it??

Originally posted by jakobnielsen
I have battled this issue some too

Can it be the way the vision checks work?

CB1 in Rages plays, is set to cover wr1 - but reads the screens as "receiver not going into route" - hence defaults to zone?

Not saying this is desirable - actually quite the opposite - but could it be the mechanics of it??



That's a good point, and something I didn't think about.

It could be what is occurring, but his assignment isn't blocking or doing anything that would warrant moving to his next progression in my opinion. I dunno though I don't have the exact answer for your question.

That is something odd I have noticed from time to time on these type of plays. For example: Defender set to cover HB and then zone.

HB left in to block, or blocks by design on a screen, so defender reads pass, starts to move to zone, but then heads towards the player he was originally intended to cover instead of the intended target if that makes sense.

Originally posted by Mightyhalo
That is something odd I have noticed from time to time on these type of plays. For example: Defender set to cover HB and then zone.

HB left in to block, or blocks by design on a screen, so defender reads pass, starts to move to zone, but then heads towards the player he was originally intended to cover instead of the intended target if that makes sense.

But in this case the person the defender was set to cover was the intended target.

Originally posted by Rage Kinard
But in this case the person the defender was set to cover was the intended target.

And instead of pursuing him, he stands there waiting to be blocked because the WR3 who by design should be blocking him, felt that another player was higher risk, so the WR3 blocked elsewhere and CB1 just stood there..

This is what I feel this thread correlates to and is why I classified it like I did.

I'm not sure if this is a bug or not. I see how it could potentially cause problems if the defender charged the receiver as well.

But it does look suspicious, you've provided a lot of examples, and this has been sitting for too long not going anywhere. So I'm going to verify it just to keep it moving.