The problem with this approach is:
- You must determine all of the possible moves an element can make, then calculate each score to determine which to make.
- You must determine all of the moves all elements could make, and compare each's best score to determine which would be first.
- A group of n elements has, at a minimum, n number of moves (one as a group of n, one as a group of n-1, one as a group of n-2, etc. and one as a single element).
So, what is the purpose of the TE? Originally, it was to point you, the player, to the move to be made by an element or a group. That caused me to re-think the process. Currently you could say that my process is to:
- Think of all the possible moves. (Or think of all of the probable moves.)
- Score each of those moves.
- Execute the moves in order from highest score to lowest, until you run out of PIPs.
So, if you want a solo system where the Non-Player General (NPG) presents the moves to you, you need a system of movement rules where you run down the list and when a triggering condition is met, you execute the move that it indicates. A "simple" IF-THEN rule base. That is the approach I am going to use for the TE in DBAS. If that is not the approach you want for your solo gaming, you might look at Richard Lee's Solo DBA on the Solo DBA Development forum on Yahoo.
More on this subject next time.