Matrix Games Forums

after playing several games today, i too have noticed this too.  i have checked my playbooks and plays and they are working as they should.  i'm guessing this is a problem with the game.

ORIGINAL: Marauders

The only way to guard against this 100% is to have all 5 M2M coverage guys set as EITHER.

Yes, that is what I do for nickel and dime defenses.

Hack, have you tried this? Have you noticed if it fixes the problem?

i used to do that.  i don't think it matters though.  it appears that the CPU doesnt' always go with the situation play group.  i've done several test games and it still happens.  i've ensured that my playbooks are not the problem.  i even added an "Any, Any" to all possible formations that DEF will face.  still, it has some issues.  i'm not sure if it is because i made plays in 2.2 then got converted to 2.2.9. 

i'm still working on it.

Ok. I see. Thanks for taking a look at this.

however, i don't see how convertion from 2.2 to 2.2.9 should create this problem.  in 2.2 i never saw this.

part of the problem is because WR have equal speed.  M2M coverage is based on speed.

to fix this, i am working on changing some M2M that is based on CAT.

This is only part of the issue.

to fix this, i will be making zone plays that are not disguised.  i've tried everything, but have no idea why this is happening.  Also, make sure WRs SPD, CAT do not match on a team.  if they are equal that will cause a double team.

ORIGINAL: hack153

to fix this, i will be making zone plays that are not disguised.  i've tried everything, but have no idea why this is happening.  Also, make sure WRs SPD, CAT do not match on a team.  if they are equal that will cause a double team.

Not sure how you mean this, Hack. Are you saying make sure two receivers on the same team do not have the exact same spd, cat ratings? Or are you saying make sure that a single reciever does not have the same spd, cat ratings? For example: spd = 99 and ca = 99. Please explane a little further.

sure. 
 
yes, WRs & TEs can't have the same SPD or CAT rating depending on how you set up the M2M variable.  If you have 2 WRs with SPD 80 and 80 is the highest ranking, one of the WR or TE may be left wide open. 

Ok. Looks like I have some editing to do. hate that i have to keep an eye on this as the maintenance of this game is starting to become a bit much. Thanks.

ORIGINAL: hack153

sure. 

yes, WRs & TEs can't have the same SPD or CAT rating depending on how you set up the M2M variable.  If you have 2 WRs with SPD 80 and 80 is the highest ranking, one of the WR or TE may be left wide open. 

Wow! That worked pretty good. The majority of the time receivers were covered. Quite an improvement. Thanks for the tip, Hack.

no problem.  i guess i could have added this to my "tip thread"...

part of the problem is because WR have equal speed. M2M coverage is based on speed.

This is not the problem. In my test league all WR have identical ratings and they are still all covered. I think it can be a logical problem in the team profile (i know this form coding, every should work but there is still somewhere a problem esp. when a variable overwrites an other).

Besides that i do not think it is a major problem. The vast majority of long gains were not caused in such situations (i use the Wilson.pbk) and missing or blown assignment happens in the NFL regulary.

for some reason, i never see this happen in Coach vs. CPU.  i've only seen it in CPU vs. CPU. 
 
i've also noticed that my LB that is playing M2M - Non-backfield - will ignore his assignment and will line-up over the QB.  i re-checked the play, and there was nothing wrong.  another oddity.

part of the problem is because WR have equal speed. M2M coverage is based on speed.

Tullius stated: This is not the problem. In my test league all WR have identical ratings and they are still all covered. I think it can be a logical problem in the team profile (i know this form coding, every should work but there is still somewhere a problem esp. when a variable overwrites an other).

I tested this several times and did not see the problem either.

I reported it to Matrix Games, so they could do a follow up, but they didn't get back to me.