BZFlag-Dev / bzflag.org

The bzflag.org static website
https://www.bzflag.org
MIT License
9 stars 7 forks source link

Corrections needed for API docs #2

Open allejo opened 5 years ago

allejo commented 5 years ago

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.

Zehra commented 5 years ago

✅ Documented bugs in this post have been completed

- allejo


From what I could find in BZFS API Events:

Administrative events

Capture The Flag events

Chat events

Countdown Timer events

Logging events

Player

Player Spawns events

Shots events

Slash Commands events

Zehra commented 5 years ago

Inconsistent information

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

Missing Descriptions

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 commented 5 years ago
allejo commented 5 years ago

@The-Noah, do you have a PR or branch for those functions you've checked off?

The-Noah commented 5 years ago

Sorry, I have been very busy recently. I am finishing up a few and then will create a PR.

allejo commented 5 years ago

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.

The-Noah commented 5 years ago

Okay. Is the list above small enough?

allejo commented 5 years ago

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