Warrior General Games

The chipping thing is only supposed to occur when the TE, FB &/or HB is running right past the blitzer/free DE. Sorry I didn't explain better, but I just copied the post I made in the testers forum. Since Bort had already added the chipping to the test server's code (not on the live server) and explained that they only chip those in their route, everyone there knows.

IMO, there is really 3 ways to skin that cat:
Have the QB dump it over the free rusher's head to the HB
Have the HB break off his route fully engage the blitzer
Have the HB's chip mean something

I can live with any or all of those options, myself. My real point was, since they are chipping under those conditions, make it so that it's at least noticeable. If not, may as well remove it.

Thanks for the info. I still cannot imagine how the FB is suppose to react to the FS here
http://test.goallineblitz.com/game/replay.pl?game_id=1602&pbp_id=347736

Warning wise word ahead:
Originally posted by PP

My real point was, since they are chipping under those conditions, make it so that it's at least noticeable. If not, may as well remove it.

Originally posted by PP
This blitz does work p much every time against a 5 WR set
http://test.goallineblitz.com/game/replay.pl?game_id=1602&pbp_id=347759

Is that bad though? I mean, they are sending 6 against 5. Someone has to go free...it's better the LDE who is further out goes free than an MLB, DT, etc.

Originally posted by Deathblade
Is that bad though? I mean, they are sending 6 against 5. Someone has to go free...it's better the LDE who is further out goes free than an MLB, DT, etc.

I don't think the blking is bad, just the QB's & WRs' reaction to it. IMO, either the WRs should recognize it and cut off their route, the QB should just throw the ball away, roll away from the free blitzer or just plain tuck and run. None of those options should work every time, but neither should that blitz, IMO.

Edit: If I wanted to pimp the system, when the blocking code on the test server went live, I'd just play man against every 5 WR set and send 6 every time. Unless against a rushing QB, from what I've seen in my tests, God pitty the fool going 5 WRs against a D like that. It's almost no win for the O. I'd have to do more testing before I swore that was the case, but it sure looks that way to me.

Quote accident, when meaning to edit instead

*mindblown*

but yeah, the QB/WRs should be able to make some kind of read.

Also, maybe unrelated...but I've always liked the idea of agility playing a role to help reduce the time it takes to throw a pass, or something along those lines.

Maybe a slider for throwing position "Always flatfooted" to "No hesitation to pass on the run"...with agility being a large factor in passing on the run.

i dunno

Originally posted by PP
I don't think the blking is bad, just the QB's & WRs' reaction to it. IMO, either the WRs should recognize it and cut off their route, the QB should just throw the ball away, roll away from the free blitzer and just plain tuck and run. None of those options should work every time, but neither should that blitz, IMO.

- The WRs cannot really react since their is not CB blitz (they can only react for a pre-snap call).
- It would be nice to see the QB move better in the pocket he had room to move forward and earn some time. I agree that throwing away/ running are good options too.
- The blocking is good. However the WR5 comeback has WR5 has primary. In principle you like the OL to shift such the RDE will be the free man. This will allow the QB to roll to the playside. However with this overload blitz I do not know if it is possible.

There would be no way that the LG could block the NT

Originally posted by Deathblade
Also, maybe unrelated...but I've always liked the idea of agility playing a role to help reduce the time it takes to throw a pass, or something along those lines.

Maybe a slider for throwing position "Always flatfooted" to "No hesitation to pass on the run"...with agility being a large factor in passing on the run.

i dunno

I could see something like that....maybe start with a penalty to pass quality at 50%(just throwing that # out there for example) and then use agility as a reduction factor, when set to "No hesitation" Make it so some ungodly # (100 agility, maybe) =0 pass quality penalty, 50 agility would be 25% 0 would be the full 50 (I know you can't have 0 agility, just making it easy to illustrate) and scale it between those #s. That or some other system could make it workable easy enough.

Originally posted by Deathblade
Originally posted by
Originally posted by PP
This blitz does work p much every time against a 5 WR set
http://test.goallineblitz.com/game/replay.pl?game_id=1602&pbp_id=347759
Is that bad though? I mean, they are sending 6 against 5. Someone has to go free...it's better the LDE who is further out goes free than an MLB, DT, etc.

Yes, but in this case it should lead to a collapse of the pocket and not be a total break down and failure to block someone.

What should happen....

The C should try and shove the NT back while he steps backward to pick up a blitzing MB and try and close the gap with the RG, so if the NT wants to go around he has to do a spin and go back inside.

The RG should start by moving BACKWARDS (not forwards toward the NT as he does) and try and pick up the faster of the MLB/SS while stepping back and closing the game with the C while trying to push folks outside.

The RT should most definitely pick up the LDE.

To me, this is what pressure should look like. It's not just an instantaneous sack every time, not that I'm against those...but more often than not is should be a fight THROUGH the line.
http://goallineblitz.com/game/replay.pl?game_id=915449&pbp_id=2920005

Originally posted by tragula
- The WRs cannot really react since their is not CB blitz (they can only react for a pre-snap call).
- It would be nice to see the QB move better in the pocket he had room to move forward and earn some time. I agree that throwing away/ running are good options too.
- The blocking is good. However the WR5 comeback has WR5 has primary. In principle you like the OL to shift such the RDE will be the free man. This will allow the QB to roll to the playside. However with this overload blitz I do not know if it is possible.

The WR's can react, they switch their route. Watch a Colts game, making an audible for WR5 or WR3 to do a quick slant, in, whatever across the middle where the MLB was will allow for a proper reaction to a blitz like this.

Originally posted by TheGreatAus
The WR's can react, they switch their route. Watch a Colts game, making an audible for WR5 or WR3 to do a quick slant, in, whatever across the middle where the MLB was will allow for a proper reaction to a blitz like this.

How can a WR see anything but a CB blitz ? Unlike a Colt game the offense in GLB is not capable to call audibles, or any other pre-snap call . A player can react post snap if he see a blitz crossing his field of view, for a WR that means the DB that is lined up in-front of you. However if that is implemented you expect the offense to make mistakes changing the plays due to a misdirection by the defense. And this sim is still far away from implementing misdirections
.
After the snap there are two option for the WR to figure out there is a MLB & SS blitz:
1) When he turns to look at the QB (typically at his first cut)
2) If he see that a defender is missing. For instance if he was running a slant expecting and suddenly cannot see the MLB in the expected zone.
In both cases the WR will just try to get open quickly and look at the QB. But that is way too late for an hot route.

Originally posted by tragula
How can a WR see anything but a CB blitz ? Unlike a Colt game the offense in GLB is not capable to call audibles, or any other pre-snap call . A player can react post snap if he see a blitz crossing his field of view, for a WR that means the DB that is lined up in-front of you. However if that is implemented you expect the offense to make mistakes changing the plays due to a misdirection by the defense. And this sim is still far away from implementing misdirections
.
After the snap there are two option for the WR to figure out there is a MLB & SS blitz:
1) When he turns to look at the QB (typically at his first cut)
2) If he see that a defender is missing. For instance if he was running a slant expecting and suddenly cannot see the MLB in the expected zone.
In both cases the WR will just try to get open quickly and look at the QB. But that is way too late for an hot route.

1.)That is why plays should always have a very quick route for one WR, to help on blitzes. The first cut is within one or two steps. Its been awhile since I've been an OC, but I dont recall longer plays having a vent as such.

2.) Any WR with high vision can see a LB smashed up against the line. Granted, not all blitzes have the guys up on the line, but i would say a good portion have the guys on the line. If a WR sees that, it should be a hot route. Also, refer to #1 in case the WR doesnt see it.

Originally posted by PackMan97


The C should try and shove the NT back while he steps backward to pick up a blitzing MB and try and close the gap with the RG, so if the NT wants to go around he has to do a spin and go back inside.


PackMan, if, in real FB, the C tries to do all that, both guys will likely blow by him, as he lays on his ass. At C, you just can't shove a 300 and some odd lbs NT back, while moving backwards. It's just flat out not possible, unless you so out class him in strength and skill that he doesn't belong on the field in the first place. In pass blking, you try to absorb him (not into your body, but into your blking stance, if that makes sense) and then stand your ground (or slowly give ground while trying to pop him out, reset, pop and give a little more, but even that pop from a set position almost never really sends him backwards at all, most often getting him more upright, at best) or steer him to the side (run blking, you either fire out and try to blow him out of the hole or allow him to come to you and use his momentum to steer him away from the hole). In either case, trying to shove as you move backwards is a one way ticket to complete and utter disaster.

The best he can really try to do in that situation is try to move the NT into the hole the blitzer is shooting for, like he did. Unfortunately, That play just isn't blockable in reality. Flip side, in reality the QB has a wide open hole up the middle to run through and even the slowest real QB would gain 10 yds every time that blitz was run. The other option would be for WR3 &/or WR5 to break their route to slants, based on a call at the line, and take it for 6 20% of the time or so. Blocking isn't the answer to that one, though. If the OL can blk that play, the D is flat out done ever getting sacks.