Warrior General Games

Originally posted by Dr. E
Ahh, I see. Instead of using several 1st & 10 inputs for every tag combo we have, we would nest the outputs. Would save a little time, but would also be less flexible.

How so.

A current AI would still fit within this structure. That's the beauty of it. There's no conversion necessary if you don't want to nest your inputs.

A HUGE +1 to this.

I suggested a similar concept to enable the outputs to have the same capabilities as the inputs but this suggestion takes that to a whole new level. I love it.

Originally posted by TruthHammer
How so.

A current AI would still fit within this structure. That's the beauty of it. There's no conversion necessary if you don't want to nest your inputs.

Because of how I sub categorize my DAI.

+1

+1 to Idea

-1 to the suggestor

+1 ldo

I still say the whole AI (O and D) needs to be more user friendly and graphical... I totally don't understand 75% of what's been posted in this thread and I think the average GLB user would agree.

What I don't get about "nesting" is how you would prioritize.... what if I have a nested set of inputs for X (1,2,3) and for Y (1,2,3) and I want Y2 to come before X1 during the last two minutes of a game, but X1 to always come before Y2, but for Y3 to override them all if a certain tagged FB is in?

Bumping as there is a similar type of suggestion once again.

This really gives DCs all of the organizational & flexibility options that are constantly requested in small snippets & needed to more quickly adapt without having it be forced on you. It really does enable you to manage your AI in any way you choose.

You could manage your AI Inputs any of the following ways:

Formation>>Tags//Game Situation
Tags>>Game Situation//Formation
Game Situation>>Tags//Formation

or even

Game SituationA>>Game SituationB//Formation//Tags

The key would be treating the Nested AI Inputs just like you treat your current Inputs. Meaning...once you find the first "Top Level" matching AI Input, you then go sequentially down on the nested AI Inputs until you find a match. Outputs are still handled the same way so packages & the like are unaffected.

bump

+1

+1

This would be very useful to me. I imagine the AI page would load faster as well if only a quarter of my inputs need to load initially.

+1