Warrior General Games

I see blocks initiated from behind constantly (I can post examples if necessary). I see it very often against the d-line, but it happens all over the field. A DT or DE gets behind the line of scrimmage and starts going after the QB but for some reason they feel the need to turn around and be engaged in a block that was initiated by one of the O-linemen they already beat. If you get past a blocker, you should either get past them or they should be flagged for holding or clipping or whatever, and since we don't have penalties here that leaves one option. It's frustrating to have to beat the same blocker multiple times on the same play when the D-linemen clearly won the original interaction. Can we please get this fixed?!

Working as intended,

turning off blocking for certain parts of the play probably isn't easy to code.

I think this would break the game even more than DAG already does, there are already too many opportunities to create space from the blocker (elusive setting wide-arounds, those moments when the DE seems to sidestep the block moments after it started)

Spin Cycle is already pretty broken in my opinion.

Originally posted by Laggo
I think this would break the game even more than DAG already does


just stop

Code-wise I have no idea how any of that stuff works, but it seems silly that if my intended target is one way that I would turn around and fight a blocker in the opposite direction. I'm not sure how that can be considered working as intended. I agree that they shouldn't "turn off blocking" at any point. But blocking should only be effective when the positioning is correct. There's got to be a way to code the intended direction of the defensive player and the position of the blocker relative to that, and say if the blocker is not anywhere near the intended path, block effectiveness drops dramatically. After all when the block is engaged the two players seem to turn with each other as a running back moves around the field. So clearly they are already moving with the intended direction in mind.

General positioning considerations seem to be completely lost on the devs of this game (e.g. blocking, pass coverage). Either that or its really hard to code.

Some sort of gradient based on facings would be fairly easy to code. Lets say the OT and DE are hitting eachother dead on. It would be easier to make the block. If the DE was going wide around and the OT peeled back to block and was at a 90 degree difference in facing, it would be harder to block. ect.

Originally posted by Laggo
Spin Cycle is already pretty broken in my opinion.

Surprised I missed this... This is something someone who doesn't know a whole lot about DT/DEs would say.

Spin is fine.

For someone who has never even built a DE or DT or a winning team, that is ironic

Originally posted by Laggo
For someone who has never even built a DE or DT or a winning team, that is ironic

I've built both?

Originally posted by Adderfist
Some sort of gradient based on facings would be fairly easy to code. Lets say the OT and DE are hitting eachother dead on. It would be easier to make the block. If the DE was going wide around and the OT peeled back to block and was at a 90 degree difference in facing, it would be harder to block. ect.

Already in there for ball carriers at least. Since it should be added to/for blockers so they don't block people behind them, defenders should also not be able to be blocked from behind and have a much easier time breaking blocks from the side.

Originally posted by Jampy2.0
I've built both?

ADMISSION TO MULTI'S PLEASE BAN FOR LIFE