Warrior General Games

Originally posted by steinbajl
My interpretation of what he was saying is that NOT tagging is the problem. I set up my LB to man cover the TE, but the offense plays a FB out of position in the TE slot and my LB drops to a zone because he does not see a TE in the formation even though the FB is lined up at the TE spot. If that is the situation it makes an easy loophole for dropped coverages, so I think that situation is unlikely unless it is a bug.... but I have seen my players fail to cover the man they are assigned too so????

QB is an easy example. You'd want a set for a passing QB. You'd want a set for a running QB. What would you do if a team plays a eHB at QB? Or that pHB? Or that scat FB? Or one of the 4 speed WRs? Or that speed TE? There's too many possibilities.

So what you'd do is have a p QB tag set, a r QB tag set, and then a set with no tag, to tell the Ai that if there is no tagged QB then you need to use these X plays to protect against gimmick QB stuff.

Originally posted by Theo Wizzago

#2 is Tagging. Here you assign each offensive dot (that you wish to tag) a particular 'offensive outlook' so to speak. If you see a BTE and you tag him as a Blocker... and then he goes out for a pass... he's likely not to get covered if he's playing at the FB or WR slot. If he's playing the TE slot, you should be fine...

This is simply not correct. If you tag 2 players as receivers - no matter who they are - when that player lines up in the TE slot, or the WR slot, or the FB slot, etc, the D you have set up to cover a receiver out of whatever slot will run. No matter what.

Where people get into trouble is making it over complicated by tagging rec TEs & rec FB (for example) differently. Then you can have issues with oop players.

Trust me - if oop stuff like that actually worked you'd see it in WL all the time, and you don't.

Originally posted by TJ Spikes
QB is an easy example. You'd want a set for a passing QB. You'd want a set for a running QB. What would you do if a team plays a eHB at QB? Or that pHB? Or that scat FB? Or one of the 4 speed WRs? Or that speed TE? There's too many possibilities.

So what you'd do is have a p QB tag set, a r QB tag set, and then a set with no tag, to tell the Ai that if there is no tagged QB then you need to use these X plays to protect against gimmick QB stuff.


it all depends. if its a WR usually u can just give him the rushing tag u use for the rushing QB. unless he plays TE too and needs a reciever tag then u will have to make extra inputs for the WR at QB. Thats if its even necessary. If a player is so far out of position that they are not a real running threat why bother. Also if its a RB or FB at least in our AI we use the same tags for power runner or elusive runner regardless of its a RB QB or FB so if its a HB or FB there tag will already work if they are at QB. I would say its always a good idea to have a default like you said tho. just in case some team puts an unexpected player in at QB. Yeah a default that is just to stop run and maybe screen plays. Otherwise you should always be running plays from the passer tagged inputs or the inputs with rQB tags

i see lots of stuff said here that doesnt make sense. some positions are nearly interchangable. for safeties it makes no difference whether free or strong safety. CB can play at safety too or safety at DB too with little penalty. DBs are mainly just DBs. A FB can play at TE with out any noticable difference either. A G can slide in to C with little notable change as well. An OT to C, not so good. Occasionally nearly every team is better using a player out of position. i mean, go ahead keep using your rTEs at TE in goaline formation because you don't have 3 BTEs. It makes a lot of sense. I don't know why i'm telling you ppl otherwise. please, keep doing what you been doin

let me clarify that if u have 2 Cs obviously u have no need to play a G at back up C. however most Cs are made for their team its probably easier to find STOP Cs in FA than normal C archetype. If a team only has 1 C they are not gonna be hurt by having a G play back up C, maybe the G will be 0.5% slower to react or whatever its not gonna make much of a difference. its far better than using a cpu or playing the C into exhaustion without a back-up. Now for some teams like us who use so many 2 TE sets it don't make sense to carry 5 WRs because then none of them getting enough snaps and the team could use that spot on a player who'd be playing much more. So on those rare occasions we go 5WR we have to use a TE as 5th WR, but you know what? It often seems to be TE playing out of position who gets open on the play anyhow. I agree for the most part not to play guys out of position but there are certain common sense situations where its not a big deal or it might even be better in that instance.

Originally posted by TJ Spikes
QB is an easy example. You'd want a set for a passing QB. You'd want a set for a running QB. What would you do if a team plays a eHB at QB? Or that pHB? Or that scat FB? Or one of the 4 speed WRs? Or that speed TE? There's too many possibilities.

So what you'd do is have a p QB tag set, a r QB tag set, and then a set with no tag, to tell the Ai that if there is no tagged QB then you need to use these X plays to protect against gimmick QB stuff.


(files that away for future use)


Originally posted by SeattleNiner
This is simply not correct. If you tag 2 players as receivers - no matter who they are - when that player lines up in the TE slot, or the WR slot, or the FB slot, etc, the D you have set up to cover a receiver out of whatever slot will run. No matter what.

Where people get into trouble is making it over complicated by tagging rec TEs & rec FB (for example) differently. Then you can have issues with oop players.

Trust me - if oop stuff like that actually worked you'd see it in WL all the time, and you don't.





TBH, I cannot remember having issues with tagging a dot as a 'receiver'... it's when the dot is tagged as something else that things go awry. Maybe I should just tag all dots as receivers?

Originally posted by SeattleNiner
Tagging is easy if you do it right. All you need to do is tag all receiving dots as receivers, and all blockers as blockers - then no matter what dot is in the TE slot (for example a TE, FB, HB, WR, G, C, etc) - if you tagged the dot as a receiver the dot will get treated as a receiver and will get covered. If you tagged the dot as a blocker it will get treated as a blocker. Any position penalties on the O by playing dots in different position are just a bonus for you. Very simple!

I tag Power and Rusher which subs in the most suited defender. I also tag WRs and OL in case they are played OOP. Positional tags are over-ridden by 3rd down and yardage inputs etc . And if all else fails and a cb pops up in the backfield theres a default