11-04-2013, 03:38 AM
Hey, I've just been looking over this thread, and it has got quite a few good ideas.
First, I believe that having two levels of AI adds a great deal of flexibility. The higher level handles the selecting of which behavior/task to execute, and the lower level is the actual running of that behavior.
I personally think that we should only run one behavior at a time, but if a behavior is put back into the priority queue it should hold its state. So if, for example, a villager is busy building a house and is attacked by a player, the upper level AI generates a new RunAway behavior and puts it in the priority queue.
On the next tick, it checks to see if the next behavior in the queue has a higher priority than the current task does. Since running away from being hurt has a higher priority than building the house, the BuildHouse gets put back into the queue and the RunAway gets set as the current behavior.
Once the villager escapes the player, we delete the RunAway behavior and pull the next behavior out of the queue, which just happens to be the BuildHouse task. The villager then returns to where he was building the house, and continues from where he left off.
Does that make sense? Did I explain it alright? I've been thinking about the AI for quite a while, and really want to implement it/see it implemented
First, I believe that having two levels of AI adds a great deal of flexibility. The higher level handles the selecting of which behavior/task to execute, and the lower level is the actual running of that behavior.
I personally think that we should only run one behavior at a time, but if a behavior is put back into the priority queue it should hold its state. So if, for example, a villager is busy building a house and is attacked by a player, the upper level AI generates a new RunAway behavior and puts it in the priority queue.
On the next tick, it checks to see if the next behavior in the queue has a higher priority than the current task does. Since running away from being hurt has a higher priority than building the house, the BuildHouse gets put back into the queue and the RunAway gets set as the current behavior.
Once the villager escapes the player, we delete the RunAway behavior and pull the next behavior out of the queue, which just happens to be the BuildHouse task. The villager then returns to where he was building the house, and continues from where he left off.
Does that make sense? Did I explain it alright? I've been thinking about the AI for quite a while, and really want to implement it/see it implemented