Open allejo opened 5 years ago
✅ Documented bugs in this post have been completed
- allejo
From what I could find in BZFS API Events:
Administrative events
bz_eUnmuteEvent correct (still not sure why it uses the same data as bz_eMuteEvent though.)
There is no difference between the data available between a mute and unmute action. If you need to know which action it is, you already have that by listening to either to the mute or unmute event.
Capture The Flag events
bz_eAllowCTFCaptureEvent ('bool killTeam' appears in header, although does not appear in documentation.)
Fixed in 4f9e7f583fcf1c8d672274a1797bddfc7434eda9
Chat events
bz_eFilteredChatMessageEvent (Mentions available, since 2.4.4, while it is available since 2.4.0, but bz_ChatEventData_V2 exists only in 2.4.4 and after, so 'technically' correct.)
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
bz_eRawChatMessageEvent (Mentions available, since 2.4.4, while it is available since 2.4.0, but * bz_ChatEventData_V2 exists only in 2.4.4 and after, so 'technically' correct.)
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
Countdown Timer events
bz_eGameEndEvent (Says 2.4.0, while bz_GameStartEndEventData_V2 exists in 2.4.4 and after.)
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
bz_eGameStartEvent (Says 2.4.0, while bz_GameStartEndEventData_V2 exists in 2.4.4 and after.)
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
Logging events
bz_eNetDataReceiveEvent (In header, there is a 'playerID', but this isn't in the documentation, so not sure if this is intentional.)
Fixed in f1540e15bb67c5e4dfad4eefc1d344f47ca9d325
bz_eNetDataSendEvent (Same as detail mentioned above.)
Fixed in f1540e15bb67c5e4dfad4eefc1d344f47ca9d325
Player
bz_eGetPlayerMotto (Mentions available, since 2.4.4, while it is available since 2.4.0, but bz_GetPlayerMottoData_V2 exists only in 2.4.4 and after, so 'technically' correct.)
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
bz_ePlayerAuthEvent ('bool password' and 'bool globalAuth' appear in header, but not in documentation.)
Fixed in c99bc2e85d3188cd1849dc85a76a7b326779183d
bz_ePlayerDieEvent (Available since 2.4.0, but bz_PlayerDieEventData_V2 exists only in 2.4.10 and after.)
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
Player Spawns events
bz_eAllowSpawn (2.4.6. and after have bz_AllowSpawnData_V2.)
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
Shots events
bz_eShotFiredEvent ('int shotID;' appears in header, but not in documentation.)
Fixed in c99bc2e85d3188cd1849dc85a76a7b326779183d
Slash Commands events
bz_eSlashCommandEvent (exists since 2.4.0, but bz_SlashCommandEventData_V2 not documented, but exists since 2.4.14 and after.
Fixed in bd5f3ea06b75b3cb657d717c16f4ff114c947eb1
Chat Messages
Flag Management
Inter-Plug-in Communications
Map Building
Player Latency
Player Records
Player Score
Player State
Poll Management
Server Management
Shot Management
String Operations
Timed Games
URL Jobs
World Management
Bans
Connection Management
Coordinate System
Filtering
Game Mode Management
Gameplay Recordings
Global Database Management (BZDB)
Help Topics
Inter-Plug-in Communications
Map Building
Map Information
Map Management
Misc
Player Handicaps
Player Information
Player Latency
Plug-in Management
Poll Management
Server Debugging
Server Information
Server Management
Server Side Players
Server Side Shots
Server Time
Slash Commands
String Operations
Timed Games
URL Jobs
Edit: Minor update to "missing descriptions".
@The-Noah, do you have a PR or branch for those functions you've checked off?
Sorry, I have been very busy recently. I am finishing up a few and then will create a PR.
Sorry, I have been very busy recently. I am finishing up a few and then will create a PR.
No worries, thanks for your work! If you could just make sure you split your contributions to reasonably sized PRs, that'd help us review them and manage them quicker.
Okay. Is the list above small enough?
I'd suggest splitting them up at least into two PRs. See how #5 has grown to a point where it's hard to find conversations. But I'm cautious towards suggesting one PR/doc because then we'd be flooded with PRs since we're barely starting off with docs.
Admin Related
API/Server Related
Commit 987414d6841b7a2a89cbf2c21da396e5036bfedc added the entirety of the remaining 2.4.x API to the docs. These files have multiple overloads so verifying that the committed versions are correct would be highly appreciated.