You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-1Lines changed: 28 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,31 @@
2
2
3
3
Enable Minecraft whitelist management from an exposed HTTP endpoint
4
4
5
-
_wip_
5
+
---
6
+
7
+
`GET / -> [] of {uuid: "...", name: "..."}` - Returns the `whitelist.json` of the server.
8
+
`POST / ({name: "..."}) -> 201` - Adds a user to the whitelist via username.
9
+
`DELETE / ({name: "..."}) -> 201` - Removes a user from the whitelist via username.
10
+
11
+
---
12
+
13
+
- Interfacing with the whitelist via Bukkit's API doesn't seem to work properly, so this plugin just calls the `whitelist` command directly, as you would via the server console.
14
+
- Even if the server fails to whitelist a player, the response will still be a `201`, so it is assumed you hand the server a valid Minecraft username.
15
+
- Default port is 7500, configurable via `<server dir>/plugins/<plugin dir>/config.yml`.
16
+
- Everything is `application/json`.
17
+
- Authentication is done via Bearer Tokens, any request must contain a valid Bearer Token to be served anything but a 403.
0 commit comments