43 typedef std::multimap<map_location, map_location>
move_map;
46 typedef std::map<map_location, pathfind::paths>
moves_map;
77 class move_and_attack_result;
std::set< map_location > recent_attacks
A small explanation about what's going on here: Each action has access to two game_info objects First...
std::shared_ptr< engine > engine_ptr
std::vector< attack_analysis > attacks_vector
std::shared_ptr< recruit_result > recruit_result_ptr
std::shared_ptr< move_and_attack_result > move_and_attack_result_ptr
std::shared_ptr< typesafe_known_aspect< T > > typesafe_known_aspect_ptr
std::shared_ptr< typesafe_aspect< T > > typesafe_aspect_ptr
std::map< std::string, known_aspect_ptr > known_aspect_map
std::shared_ptr< aspect > aspect_ptr
std::shared_ptr< attack_result > attack_result_ptr
std::shared_ptr< stopunit_result > stopunit_result_ptr
std::multimap< map_location, map_location > move_map
The standard way in which a map of possible moves is recorded.
std::vector< typesafe_known_aspect_ptr< T > > typesafe_known_aspect_vector
std::shared_ptr< goal > goal_ptr
std::shared_ptr< stage > stage_ptr
std::shared_ptr< synced_command_result > synced_command_result_ptr
std::map< map_location, pathfind::paths > moves_map
The standard way in which a map of possible movement routes to location is recorded.
std::shared_ptr< candidate_action > candidate_action_ptr
std::shared_ptr< move_result > move_result_ptr
std::shared_ptr< known_aspect > known_aspect_ptr
std::shared_ptr< action_result > action_result_ptr
std::shared_ptr< recall_result > recall_result_ptr
std::map< std::string, aspect_ptr > aspect_map
std::unique_ptr< ai_composite > composite_ai_ptr
std::vector< typesafe_aspect_ptr< T > > typesafe_aspect_vector