If i may but in here for a quick question that''s been on my mind that i''d like to bounce off you peoples. In terms of a game development mechanism, how do we now seperate Intution from intelligence? I''m thinking that intelligence is about learning and intuition is about guessing? That''s my opinion and i think that the computer could be made to guess by balancing up the odds such as time and distance a player is away from the computers home base if you get my point. Where as learning is more about gathering and using information.

I love Game Design and it loves me back.

Our Goal is "Fun"!

If you want to know what intuition is, read the celestinion promise (if I spelled it correctly), the first 9 insights.

Do you want to emulate it? You have to play for God/soul team

OK, it looks like it''s about time to try to fuse everyone''s best ideas into one stagedy and call it my own...

What IMHO would be the most efficient way to implement a system that learns, using some form on fuzzy logic (or intuition) would be this:

Start the AI with a general stragedy template. This is no different from most games today. Next, from this general AI, it passes commands down to the Commander AI level (let''s say that there are n commnaders), they have a preset way to deal with these high-level commands. Then the commanders will pass mid-level commands to the units. The units have a template of responses as well.

Each of these levels of input -> responses/subcommands is stored in script.

Whenever there is excess processing power (perhaps between levels), then starting with the lowest level, they process a NN with their new inputs and come up with some generalizations/observations. These get passed up to the next level of command. Then, command would pass changes to that lower level''s scripts.

Here''s how that would work. You have 3 harvesters in a field. They get attacked by a tank, which kills two of the tanks. The third tank escapes due to a misaimed shot. The surviving harvester returns to base and runs it''s debriefing while being repaired (if injured, then get repaired is a predefined script fo the Harvester). It comes up with the observation that if a tank appears then you''ll lose 3/4ths of your harvesters (2 dead + 1 injured). That observation gets queued up for the harvester''s commander.

At the end of the level, the commander get the time to go through it''s queue of observations and sees the one about Harvesters getting killed by Tanks. He in return issues a new command to all Harvesters: If you see an enemy tank, then head home. The commander also passes up a message that the enemy tanks can do at least 20 HP damage (the HP of the harvester).

The Game AI sees the mesage about the tanks capabilities and tells all commanders that they need to increase the armor on all units. The next level, the game AI may realize that it''s had an increase in killings of it''s light units (like scouts), and order their armor lessened to increase their speed.

This could limit your loss of processing time by using the NNs, by using low stress time to do that processing. Then dynamically determine when there''s not a lot going on.