The BZFS API (Application Programmers Interface) is a set of C++ functions, structures, and classes that is exported by BZFS to be used by Plug-ins. The API provides access to the various states and data structures of a running BZFS game and is the primary method of communication between a plug-in and the game server.
The BZFS API is defined entirely in the bzfsAPI.h header file that is part of the BZFlag Source code. The header is also included with each install of the BZFlag installer for Microsoft Windows.
Plug-ins include this file in their source code so that they may access the functions it contains.
All BZFS API code structures will begin with the prefix bz or bz_ for clarification and to prevent conflicts with names of code structures inside BZFS or any plug-ins.
The API was added in version 2.0.4 of BZFlag. While working well for many users, it was found to be lacking in a number of features that would make make it difficult for plug-ins to run when the API itself was changed.
As of version 2.1 of BZFlag, the entire API was versioned and set up to use derived classes so that plug-ins written to use an older version of the API will work in newer versions of the software. Newer data structures would be put into further derived classes and would not be seen by the older plug-in. Due to this change a large number of API functions changed in name. This change causes all older 2.0.x plug-ins to no longer work with out a source code change. Once older plug-ins are updated to the new 2.1 API they will use the new versioning system and work fine in newer versions with out any needed changes.
There are 3 primary entry points into each plug-in. These entry points are the 3 core functions that every plug-in must implement.
BZF_PLUGIN_CALL int bz_Load ( const char* command ); BZF_PLUGIN_CALL int bz_Unload ( void ); BZF_PLUGIN_CALL int bz_GetVersion ( void );
bz_Unload is called when a plug-in is no longer needed and will be shut down. This is most commonly called when bzfs is shutting down, or when a plug-in is unloaded manualy.
bz_GetVersion is called by bzfs before any other functions are called. The function should return the version of the API that it is written for. This is to prevent bzfs from attempting to load plug-ins that use a newer incompatible API.
bzfsAPI.h defines a C MACRO to help ease the implementation of this function. All a plug-in must do is put the macro;
somewhere in its sources, and then export the function. This will automatically return the API version of the current API you are using. See the sample plug-ins for examples. These will be the only 3 functions called by bzfs for non-event actions.
All entry point functions should be preceded with the BZF_PLUGIN_CALL macro. This macro will tell your compiler to export these functions so bzfs can call them after the plug-in is loaded.
Due to how Microsoft Windows handles memory access between an application and dynamically loaded Libaries(DLLs), there are a few custom data types that are used in the API. These are used for common STL style containers, for strings and lists.
Any text passed back from the API or events will come in the form of a bz_APIString. This is a class defined in the API that behaves much like a std::string. The 'c_str()' method can be used to get the text out as a normal 'const char*'. The class also supports many assignment functions for setting it's contents.
bz_APIString also includes some utility functions such as replace all and tokenize that are commonly needed by plug-ins.
→ Main article: bz_APIString
A few API functions require lists of integers, strings, or floats. For these functions the plug-in will need to use one of the following list classes. These classes are similar to the std::vector in implementation. When a plug-in needs to allocate one of these lists, it must use the appropriate allocator function, so BZFS can make a new list for the plug-in to use. These will return a pointer to a new list for the plug-in to use. When the plug-in is finished with the list, it needs to tell BZFS to delete the list with a call to the appropriate delete function. The lists types are;
|List||allocator function||delete function||contained type|
A number of enumerations exist in the API and are used by a number of API functions and events.
bz_eTeamType bz_eEventType bz_eShotType bz_eGameType bz_ePlayerStatus bz_eWorldObjectType bz_eAPIColType bz_ePlayerType bz_eRejectCodes bz_ePlayerDeathReason
Plug-ins can register callbacks so they can be notified of various actions and state changes in the current BZFS game. These events tell a plug-in when important things happen, such as when a player has spawned, or is killed. These events are the primary form of communication from the BZFS server into the plug-in.
→ Main article: Event(API)
The BZFS API provides a number of functions to plug-ins for use in querying the current game state. Functions are used both to get information about the game, and to trigger in game actions, such as activating a world weapon.
→ Main article: Functions(API)
The documentation for the API provided on this wiki is mostly concerned with the current development version of the software. There have been changes over time to the API. Any changes to classes and functions will be noted in the new documentation under a History section. In general the initial API that was released with the 2.0.x product line was not consistent, and many of these inconsistencies are being worked out with newer versions of the API (3.0 and later)
All API developers should use the bzfsAPI.h file as well for exact spellings of methods and parameters.