- Generated by
1.8.17
|
Crossfire Server, Trunk
|
Functions | |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event | occurs (global events are 'shout', 'login', 'death', and so on). A complete list of events is available in the include/plugin.h file. Specific notes related to the Python plugin. -------------------------------------------- The Python plugin supports all global events. The const ant PYTHON_DEBUG defined at the start of the plugin_python.c file increases the verbosity of the plugin. Global event scripts go into SHARE/maps/python/events/< event name > |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin | path (SHARE/plugins). Console messages. ----------------- When Crossfire starts |
| pluglist shows those as well as a short text describing each | plugin (usually a version string). If no plugin is loaded |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen< event name > can be the right part of the EVENT_xxx defines Some problems have already been reported about the autodetection of the Python libraries Don t forget that you need the development files of | Python (it means the 'libpython2.x.a' and some header files, including 'Python.h'). If configure fails whatever you try |
Variables | |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t | exist |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus | gives |
| Plugin | Information |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen< event name > can be | init |
| pluglist shows those | keywords |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been | loaded |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen< event name > can be | login |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given | plugin |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing | plugins |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus | PoisonedDagger |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of | Python |
| Add your Python library path to the | PYTHON_LIB |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen< event name > can be the right part of the EVENT_xxx defines Some problems have already been reported about the autodetection of the Python libraries Don t forget that you need the development files of you can still try to edit the plugin Makefile by hand You need | to |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event occurs | ( | global events are 'shout' | , |
| 'login' | , | ||
| 'death' | , | ||
| and so | on | ||
| ) | const |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin path | ( | SHARE/ | plugins | ) |
Referenced by inja::Parser::add_to_template_storage(), CREMainWindow::browsingMap(), check_normalize(), check_zone(), CREMapInformationManager::checkEvent(), command_reset(), dead_player(), nlohmann::basic_json::diff(), do_parameters(), dump_unused_maps(), enter_fixed_template_map(), enter_unique_map(), find_help_file(), find_help_file_in(), find_maps(), MessageManager::findMessage(), generate_picture_path(), get_map_id(), get_map_info(), getEventFiles(), ScriptFileManager::getFile(), CREMapInformationManager::getOrCreateMapInformation(), init_regions(), list_map(), load_and_link_tiled_map(), load_citylife(), CREMapInformationManager::loadCache(), MessageManager::loadDirectory(), MessageManager::loadScriptComment(), map_remove_unique_files(), inja::open_file_or_throw(), inja::Parser::parse(), inja::Parser::parse_into(), inja::Parser::parse_into_template(), inja::Parser::parse_statement(), nlohmann::basic_json::patch(), path_combine(), path_combine_and_normalize(), path_from_current(), path_normalize(), postInitPlugin(), CREMapInformationManager::process(), python_command_function(), readDirectory(), SoundFiles::refreshSounds(), remove_directory(), resurrect_player(), set_confdir(), set_datadir(), set_localdir(), set_mapdir(), set_playerdir(), set_regions(), set_templatedir(), set_tmpdir(), set_uniquedir(), spellpath_msg(), AssetFieldCompleter::splitPath(), START_TEST(), CREMapInformationManager::storeCache(), CREMapPanel::updateItem(), write_pictures_from_real_size(), and write_world_info().
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen<event name> can be the right part of the EVENT_xxx defines Some problems have already been reported about the autodetection of the Python libraries Don t forget that you need the development files of Python | ( | it means the 'libpython2.x.a' and some header | files, |
| including 'Python.h' | |||
| ) |
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t exist |
Definition at line 53 of file plugins.txt.
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus gives |
Definition at line 40 of file plugins.txt.
| Plugin Information |
Definition at line 9 of file plugins.txt.
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen<event name> can be init |
Definition at line 54 of file plugins.txt.
Referenced by nlohmann::basic_json::basic_json(), nlohmann::basic_json::binary(), main(), nlohmann::basic_json::operator+=(), nlohmann::ordered_map< Key, T, IgnoredLess, Allocator >::ordered_map(), nlohmann::basic_json::push_back(), server_main(), setup(), and START_TEST().
| pluglist shows those keywords |
Definition at line 9 of file plugins.txt.
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been loaded |
Definition at line 42 of file plugins.txt.
Referenced by START_TEST().
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen<event name> can be login |
Definition at line 54 of file plugins.txt.
Referenced by checkbanned().
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout< keyword > Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin< libname > Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python plugin |
Definition at line 15 of file plugins.txt.
Referenced by CREMapInformationManager::loadCache(), plugins_find_plugin(), and plugins_remove_plugin().
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing plugins |
Definition at line 28 of file plugins.txt.
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus PoisonedDagger |
Definition at line 40 of file plugins.txt.
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of Python |
Definition at line 20 of file plugins.txt.
| pluglist shows those as well as a short text describing each the list will simply appear empty The keyword for the Python plugin is Python plugout<keyword> Unloads a given identified by its _keyword_ So if you want to unload the Python you need to do plugout Python plugin<libname> Loads a given whose _filename_ is libname So in the case of you d have to do a plugin cfpython so Note that all filenames are relative to the default plugin it tries to load all available files in the SHARE plugins directory as plugin libraries It first displays the Initializing the plugin has the opportunity to signal itself by a message on the console Then the server displays an informative message containing both the plugin content and its keyword For the Python the standard load process thus GreenGoblin When a plugin has been it can request to be warned whenever a global event and are named freely by the developer If the directory doesn t nothing will happen<event name> can be the right part of the EVENT_xxx defines Some problems have already been reported about the autodetection of the Python libraries Don t forget that you need the development files of you can still try to edit the plugin Makefile by hand You need to |
Definition at line 62 of file plugins.txt.
1.8.17