Warrior General Games

+1!

this would be a nice feature

+1

this is a great idea as a lot of times someone will be wide open but is not in the progression.

Defo a +1.

doobas™

Unlikely to add. Adds even more complexity to an already complex AI.

Originally posted by Catch22
Unlikely to add. Adds even more complexity to an already complex AI.

seems to me your customers dont mind it being added. http://goallineblitz.com/game/forum_thread.pl?thread_id=4701943

if we are forced to figure out how to build a dot, this idea fails in complexity to that.

kepping hope alive

Originally posted by Chysil
so it really depends on how it works. It could work even completely differently... to be honest I don't really know. What you are wanting might not even be possible per say

First, http://public.wsu.edu/~brians/errors/perse.html

Second, I am not sure who it would not be possible "per se" but it can be programmed to at least react something in this manner. It may be drastic change in the code though.

To the OP, +1.

I wonder if Catch's comment has to do with the complexity on the coding side as opposed to the "complexity" on the user side.

Originally posted by DTRAIN
seems to me your customers dont mind it being added. http://goallineblitz.com/game/forum_thread.pl?thread_id=4701943

if we are forced to figure out how to build a dot, this idea fails in complexity to that.
Originally posted by CDZYO
I wonder if Catch's comment has to do with the complexity on the coding side as opposed to the "complexity" on the user side.

My thought is it has to based on the responses I see here mostly. Coding it as, I mention, before could be complicated; unless, they start from scratch. Which Bort may not be willing to do.

I'd be for it, except-- what's the negative (for the offense)? There has to be a trade-off for every option. It seems like it would encourage everyone to just put "open man" for every progression.

I'd guess that because the QB scans the field faster, he might be more likely to make a mistake about who's open? It would be tough to balance that without making it unusable, but also without making it easily the best option...although if it could be done and kept balanced, it would be a good idea.

Well, perhaps the downside would be something like this: say I normally run WR2 WR2 TE TE HB from play X. I change it to WR2 WR2 blank blank HB. By progression 3, the TE is wide open, but the QB fails his blank (scan field) Vision check and doesn't see it, and throws to someone else who is in a worse position: incomplete. Or he sees another guy, slightly less open, but enough to satisfy his risk assessment, and goes for him before he ever sees the TE, and the pass is incomplete. I would guess that you could say that the Vision check is tougher than through normal progressions. In a full custom, the QB is "forced" to check the TE, but in the "blank spot", he might not even look that way.

Maybe. If scanning even works that way, of course. It doesn't seem like something that would be inevitably unbalanced, for sure. Most OCs would want to keep control of where their QB is looking and when, I would think.

+1

Originally posted by CDZYO
I wonder if Catch's comment has to do with the complexity on the coding side as opposed to the "complexity" on the user side.

if he means the code is too complexed, then i respectfully apologize to and misunderstood him. if he means its too complicated for us to figure out then i stand my ground and disagree completely.

Originally posted by Ken1
I'd be for it, except-- what's the negative (for the offense)? There has to be a trade-off for every option. It seems like it would encourage everyone to just put "open man" for every progression.

I'd guess that because the QB scans the field faster, he might be more likely to make a mistake about who's open? It would be tough to balance that without making it unusable, but also without making it easily the best option...although if it could be done and kept balanced, it would be a good idea.

i try to encourage the use of the word "blank space" instead of 'open man'.

blank space is my idea to let the qb carry on as tho no progression command is in-active for those few tics. thus using his build to try to find a favorable mismatch. NOT automatically go to 'open man'.

in other words...proceed as tho you didnt use the progression tree at all....for those few tics.