Originally posted by Bort
That's a pretty good rundown I think, Kirghiz, thanks for that input.
Would you have these options as a per-output option as well, or just on packages? Seems like you'd need them in the output as well, since packages are basically a collection of outputs.
For the QB progression idea, it might also make sense to somehow add that at the playbook level, so that you could set a particular play to have a different progression all the time, as opposed to having to set it every time in your package. Also, with your interface, there's no way to select "use play default." That would need to show up somehow.
The play default would have to be in there, I agree. I figured it would be in there somehow, by not designating anything in the drop down boxes perhaps. It would probably have to be in playbook and output selections too, but tbh the easiest way for me to explain what I had in mind was to paint a picture, and that was easiest for me to do with the package screen's layout. It does seem like something that you wouldn't really want to do from the output screen, because that would be a lot of tweaking from output to output and game to game. At least from the package screen you could designate pass protection packages and only load that particular protection package as needed.
The Playbook idea would work too, but you would be making an adjustment to that play every time you run it, where from a package you could run several variations of the same play, with different receiver progressions and protection assignments.
As I said, it probably needs to be usable from the playbook and output level, but the best practical application seems to me like would be from a package. That is how I would use it anyway.
That's a pretty good rundown I think, Kirghiz, thanks for that input.
Would you have these options as a per-output option as well, or just on packages? Seems like you'd need them in the output as well, since packages are basically a collection of outputs.
For the QB progression idea, it might also make sense to somehow add that at the playbook level, so that you could set a particular play to have a different progression all the time, as opposed to having to set it every time in your package. Also, with your interface, there's no way to select "use play default." That would need to show up somehow.
The play default would have to be in there, I agree. I figured it would be in there somehow, by not designating anything in the drop down boxes perhaps. It would probably have to be in playbook and output selections too, but tbh the easiest way for me to explain what I had in mind was to paint a picture, and that was easiest for me to do with the package screen's layout. It does seem like something that you wouldn't really want to do from the output screen, because that would be a lot of tweaking from output to output and game to game. At least from the package screen you could designate pass protection packages and only load that particular protection package as needed.
The Playbook idea would work too, but you would be making an adjustment to that play every time you run it, where from a package you could run several variations of the same play, with different receiver progressions and protection assignments.
As I said, it probably needs to be usable from the playbook and output level, but the best practical application seems to me like would be from a package. That is how I would use it anyway.
