#include "engine.hpp"#include "stage.hpp"#include "../manager.hpp"#include "../../terrain_filter.hpp"#include "../../util.hpp"#include "../../serialization/string_utils.hpp"#include "../../resources.hpp"
Include dependency graph for value_translator.hpp:
This graph shows which files directly or indirectly include this file:
Go to the source code of this file.
Classes | |
| class | ai::config_value_translator< T > |
| class | ai::config_value_translator< bool > |
| class | ai::config_value_translator< std::vector< std::string > > |
| class | ai::config_value_translator< config > |
| class | ai::config_value_translator< ministage > |
| class | ai::config_value_translator< terrain_filter > |
| class | ai::variant_value_translator< T > |
| class | ai::variant_value_translator< ministage > |
| class | ai::variant_value_translator< int > |
| class | ai::variant_value_translator< bool > |
| class | ai::variant_value_translator< std::string > |
| class | ai::variant_value_translator< attacks_vector > |
| class | ai::variant_value_translator< terrain_filter > |
Namespaces | |
| namespace | ai |
A small explanation about what's going on here: Each action has access to two game_info objects First is 'info' - real information Second is 'subjective info' - AIs perception of what's going on So, when we check_before action, we use 'subjective info' and don't touch real 'info' at all. | |
Detailed Description
Definition in file value_translator.hpp.