This wiki is archived and useful information is being migrated to the main bzflag.org website

Search results

Jump to: navigation, search
  • ...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 g The BZFS API is defined entirely in the '''bzfsAPI.h''' header file that is part of the
    7 KB (1,141 words) - 10:19, 22 August 2015
  • ===BZFS API=== ...n refactored but was not very complete, 2.4.0 introduced a new class based API that is forward comparable.
    5 KB (855 words) - 03:16, 5 December 2016
  • ...e class interface, to simplify porting to platforms without the BSD socket API. If the reply was a protocol older than 0048 then bzfs will kick the client connecting to it. In this case we recommend a fallback
    46 KB (7,475 words) - 19:48, 16 July 2016
  • ''This document describes a proof of concept rewrite of BZFS, it does not represent the current state of any release or version of the m Networking is now separate from player data. The base class is Client (Similar to the NetConnectedPeer), with children LocalClient and
    3 KB (434 words) - 14:13, 12 February 2017
  • ...erver side game world. Events are the primary method of communication from BZFS to installed plug-ins. Specific events exist for nearly all logical actions ...]] (2.0.x) or [[bz_Plugin]] (2.4+) and pass a pointer to an object of that class when ever it registers an event callback.
    7 KB (780 words) - 09:18, 27 January 2017
  • ...for passing text back to a plug-in from various events and functions. The class contains a number of utility methods commonly used by plug-ins. ...d never create a bz_ApiString, they are only passed back to the plug-in by BZFS.
    687 bytes (109 words) - 01:57, 8 May 2009
  • The '''bz_eUnknownSlashCommand''' is an API event that is called when the [[BZFS]] server does not have an installed handler for a specific [[Slash_Commands ...nSlashCommand''' returns the '''bz_UnknownSlashCommandEventData_V1''' data class.
    1 KB (185 words) - 07:57, 1 May 2014
  • The '''bz_eTickevent''' is an API event that is called once for each [[BZFS]] main loop. The wait time between tick calls can vary greatly depending on '''bz_eTickEvent''' returns the '''bz_TickEventData_V1''' data class.
    697 bytes (98 words) - 02:52, 6 April 2013
  • The '''bz_eGetWorldEvent''' is an API event that is called before the [[BZFS]] server defines the world. '''bz_eGetWorldEvent''' returns the '''bz_GetWorldEventData_V1''' data class.
    2 KB (371 words) - 01:39, 27 January 2009
  • In order to gain forward compatibility the API had to be changed in a way that broke backwards compatibility. This means t ===API Version Numbers===
    9 KB (1,440 words) - 04:16, 28 September 2011
  • * bzfs should error out if no users or groups have SPAWN * Vector class use instead of float[3]
    7 KB (987 words) - 15:32, 28 April 2013
  • The '''bz_eLoggingEvent''' is an API event called whenever a debug message is outputted. These can normally be s '''bz_eLoggingEvent''' returns the '''bz_LoggingEventData_V1''' data class.
    979 bytes (142 words) - 18:20, 15 October 2011
  • ...me Over), or when /superkill is initiated. This is not to be confused with BZFS being shutdown, /shutdown being initiated, or a game ending due to the '''- ...d '''bz_eGameEndEvent''' return the '''bz_GameStartEndEventData_V2''' data class.
    1 KB (167 words) - 08:29, 22 August 2015
  • * Fix crash on exit with Windows bzfs * Fix crash on exit with Mac OS X bzfs
    6 KB (833 words) - 00:03, 6 July 2016