Fritz Heckel

Some of these I can fix now, others will be trickier

• When using a path planner, need to make sure that the current path gets invalidated if a behavior other than the one that created that path takes over and moves the agent around. Really, each agent should probably have a single action model– at present, for ease, each behavior has a separate action model instance.
• Action model also needs to take into account the behavior parameters. At the moment, the USAR victim wanders the world looking for a hiding place, and will move away from it if another agent comes near. However, during the wander, the agent does not attempt to move away from other agents which may be wandering nearby. It may be that there should just be a “move away from agents” behavior which picks a new goal, but the behavior parameters/moods are going to be important to integrate here.
• Action model needs sensible defaults for certain things, like the ranges at which actions can be perceived. In some cases, these are provided as options to the behavior, but not all.
• Rotation issue has to be dealt with. Perhaps once within particular range, send a goto command on the rotate?
• Wishlist for FI3RST: Minimap, text labels over agents, semi-transparent circles representing visibility ranges on objects, affordances, etc.