This repository has been archived by the owner on Jan 31, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request is intended for a server-side implementation of necessary data for a whois command within the client.
Current draft of endpoint documentation:
Player Verification
This is where the client can retrieve the Discord identity of a player based on their Minecraft Name without initiating an auth code check.
This can be useful for debugging the current state of the user.
GET /player/{Player Name}
Possible Errors:
This endpoint finds the discord identity of a player.
Required Headers:
application/json
<webserver token>
The
Player Name
is the Minecraft player Name stripped of all the dashes. The server will providethe following response if everything went alright, otherwise an error may occur.
Response Body
No Data - Response
The player does not exist
in order to account for a change that is not backwards compatible.
Unlinked Player - Response
Valid Player - Response
The player exists, here is the linked account
Errors
Missing Player Name Attribute