User Pass
Home Sign Up Contact Log In
Forum > Suggestions > Epic Suggestions > New Package Screen
Page:
 
Gongadan
offline
Link
 
Originally posted by Kirghiz
The Left, Middle, and Right would be alright with me as an option, but I still think the specific players should be in there too.

Agreed 100%. I just wanted to make sure there was also an option to block based on where the potential blitzer is on the field rather than only based on who the defender is.
 
Link
 
great suggestion kirqhiz. may we have this please bort?
Edited by animusmax on Jan 8, 2010 00:37:58
 
Tlik
offline
Link
 
we'll probably see coaching before we see this

this would be a huge step in the right direction
 
Link
 
This would be an awesome idea. +!000000000000000000000000000000
 
Mo_The_Man
offline
Link
 
+1 million
 
Sal Basss
offline
Link
 
Love it. +1
 
mbinger
Playoffs?
offline
Link
 
+1
great idea

Should be at the top of the priority list.
 
SeattleNiner
NINERS
offline
Link
 
Another thing this could use is the "QB drop" (none, 3 step, 5 step, 7 step, etc), which is basically the time delay after the snap and before the QB tries to throw to his first WR.

This would make sure that on plays where the play needed to go long, enough pause (7 step drop) would be present to allow the play to develop - and conversely if you wanted a quick-hitting play (none) the QB would essentially be looking to throw immediately after getting the snap.
 
Sal Basss
offline
Link
 
Originally posted by SeattleNiner
Another thing this could use is the "QB drop" (none, 3 step, 5 step, 7 step, etc), which is basically the time delay after the snap and before the QB tries to throw to his first WR.

This would make sure that on plays where the play needed to go long, enough pause (7 step drop) would be present to allow the play to develop - and conversely if you wanted a quick-hitting play (none) the QB would essentially be looking to throw immediately after getting the snap.


-1... I actually like the idea, but let's take it one step at a time.
 
LithoMan
offline
Link
 
First, this isn't thought out well, if I have read it right. Maybe I am wrong, I read the important snip-its posted in the OP.

1. If I have a scrambling QB, I must pass a vision check now to get him to move out of the pocket? That is a huge handicap for teams that run a scrambling QB. If I want my QB to run, I want him to run.... period. I don't want him to have a vision check to run. If you've built your QB well, it don't matter if there is a would-be tackler in the way. Maybe I am thinking of this wrong, but you need to have a priority indicator on the play's direction. Like 100% run (no matter what), 80% if all WR's are covered, something of that nature. All you will do is handicap Scrambling QB's, maybe that is your intent though....

2. I don't run packages, because they are fatally flawed. SO, if this OAI style was to go into effect, it should definitely be per-play based, not package based. Drill it down to base level, so the people who like intricate OAI's, have that option. That has always been the style of the game, not a broad based style of play. You have always left it to the agent to be as intricate as they wanted to be. Why change now?

3. Other then that, I truely think you should implement this style of play for the O. I definitely like the interface. That is great. Just what I have been waiting for. Many possibilities for it!

4. Have you thought of implementing multi-routes for a WR based on voids? Fly route if the CB is trailing, or if he is bracketed he turns it into a In/Out route. Something to create seperation to get open. What about hot routes? I'd like to see the WR's get a bit smarter in the game. Along with a bit more option of comeback routes.

All in all, a very good bump up in O planning. I like it!
 
PackMan97
offline
Link
 
Originally posted by LithoMan
First, this isn't thought out well, if I have read it right. Maybe I am wrong, I read the important snip-its posted in the OP.

1. If I have a scrambling QB, I must pass a vision check now to get him to move out of the pocket? That is a huge handicap for teams that run a scrambling QB. If I want my QB to run, I want him to run.... period.


Then call a running play



 
DiMo28
offline
Link
 
How about a way to send a RB out into a pattern if no one is blitzing (or he fails the vision check)?
 
Redass Ranch
offline
Link
 
Originally posted by DiMo28
How about a way to send a RB out into a pattern if no one is blitzing (or he fails the vision check)?


from page 2: Originally posted by Octowned
1) make all plays have a HB/FB/TE route (plz)
 
SeattleNiner
NINERS
offline
Link
 
Originally posted by Sal Basss
-1... I actually like the idea, but let's take it one step at a time.


Not really, without the correct QB pause before throwing there will be all kinds of F ups, my QB threw the ball too soon, too late, etc. Providing this pause should be very simple and integral to getting the play timing to work correctly.
 
Kirghiz
offline
Link
 
Originally posted by SeattleNiner
Another thing this could use is the "QB drop" (none, 3 step, 5 step, 7 step, etc), which is basically the time delay after the snap and before the QB tries to throw to his first WR.

This would make sure that on plays where the play needed to go long, enough pause (7 step drop) would be present to allow the play to develop - and conversely if you wanted a quick-hitting play (none) the QB would essentially be looking to throw immediately after getting the snap.


There are a few plays in which I believe that the QB's drop could be adjusted to make the play flow better. Having said that, that is another issue entirely, and would really need extensive research and testing. It could certainly be added later, but the amount of work it would take get custom drops to work correctly would take a while imo. Certainly longer than it would take to get most of the aspects of the proposal working correctly.

Originally posted by LithoMan

1. If I have a scrambling QB, I must pass a vision check now to get him to move out of the pocket? That is a huge handicap for teams that run a scrambling QB. If I want my QB to run, I want him to run.... period. I don't want him to have a vision check to run. If you've built your QB well, it don't matter if there is a would-be tackler in the way. Maybe I am thinking of this wrong, but you need to have a priority indicator on the play's direction. Like 100% run (no matter what), 80% if all WR's are covered, something of that nature. All you will do is handicap Scrambling QB's, maybe that is your intent though....


I am not sure what game you are playing to be honest. Too many times I see a 3 man rush with 8 defenders in coverage, 15 yards away, and the QB could easily run for a first down, but instead he throws long into double coverage. Scrambling QB's don't scramble on pass plays in the current sim, or rather maybe once in 50 play calls. The reason is that the sim has the QB go from receiver to receiver through his progressions, and only thinks about scrambling when there is pressure. If you actually have a "look to run" progression, taking off on a scramble would be a viable option if the QB has a running lane, and one would think he would do it if it was actually part of his progressions. You could set up the plays to encourage your QB to scramble for yards, and that would force defenses to keep a man up to defend the scramble.

I absolutely do not see how you think that hurts scrambling QB's honestly.

Edited by Kirghiz on Jan 8, 2010 10:43:45
 
Page:
 


You are not logged in. Please log in if you want to post a reply.