Add fallback UUID URL in case the Mojang UUID API returns 403

[nagornin]

Is your feature request related to a problem? Please describe.

The Mojang API for resolving player UUID is currently broken[1][2][3] and returns 403 on query. This is a well-known issue and the API is sometimes unavailable for days. I suggest adding a fallback UUID URL to CraftAPI (which is used by FastLogin) that will query api.minecraftservices.com if the GET request to the api.mojang.com UUID endpoint returns 403.

The api.minecraftservices.com UUID URL as well as the note about instability of api.mojang.com UUID URL is mentioned in https://minecraft.wiki/w/Mojang_API#Query_player's_UUID.

1. https://bugs.mojang.com/browse/WEB/issues/WEB-7591
2. https://www.reddit.com/r/Minecraft/comments/1l8yx2f/im_trying_to_get_my_uuid_from_apimojangcom_but_im/
3. https://www.reddit.com/r/Minecraft/comments/1l8rsd8/mojang_api_down/

Describe the solution you'd like

Add a fallback UUID URL to MojangResolver that will be used if the primary UUID URL returns 403 on query.

Describe alternatives you've considered

No response

Platform

Spigot

Relevance

• I checked for existing tickets -
  If there are, please vote them with a thumbs reaction and not create new ones

[WuzzyLV]

I was gonna try to implement this but im noticing that the CraftAPI on github is stale for almost a year and the version only goes up to 0.5.
Is the current version no longer public? @TuxCoding

[TuxCoding]

The last tagged version is 0.5, but the main branch is up to date and in use:

https://github.com/TuxCoding/CraftAPI/blob/6f8604536cf9dabc59dd226aeb1be8a73698dbd3/pom.xml#L10

Sent from mobile.

[WuzzyLV]

The last tagged version is 0.5, but the main branch is up to date and in use:

TuxCoding/CraftAPI@6f86045/pom.xml#L10

Sent from mobile.

Are you sure, as for example FastLogin expects getConnection and specific readJson overloads in AbstractResolver.java, while it doesnt really contain any of that on the repo.

Decompilling the 0.8 version shows that AbstractResolver.java has ingeneral a lot more than the repo version does.

[TuxCoding]

You were right. One commit was missing. What got mixed here is that 0.8.1 isn't tagged. FastLogin doesn't use that latest version, because the changes weren't relevant. So it is still on: TuxCoding/CraftAPI@e0bee31

[TuxCoding]

There you got the 0.8 version.

[WuzzyLV]

Yea i see, i decided to just try using the newer version, otherwise its a mega pain to test my implementation.
Which means i have to update the FastLogin implemenation, so my question is, what is the point of https://github.com/TuxCoding/FastLogin/blob/main/core/src/main/java/com/github/games647/fastlogin/core/ProxyAgnosticMojangResolver.java
Cause as far as i can tell the new version of MojangResolver does basically the same thing.

[TuxCoding]

FastLogin/core/src/main/java/com/github/games647/fastlogin/core/ProxyAgnosticMojangResolver.java

Lines 38 to 41 in c28c634

	* An extension to {@link MojangResolver} which allows connection using transparent reverse proxies.
	* The significant difference is that unlike MojangResolver from the CraftAPI implementation, which sends the
	* "ip" parameter when the hostIp parameter is an IPv4 address, but skips it for IPv6, this implementation leaves out
	* the "ip" parameter also for IPv4, effectively enabling transparent proxies to work.

[WuzzyLV]

https://github.com/TuxCoding/CraftAPI/blob/main/src/main/java/com/github/games647/craftapi/resolver/MojangResolver.java#L79

That makes sense, but i see youve already implemented something similiar in CraftAPI, so do i just refactor ProxyAgnosticMojangResolver to just not pass the adress, instead of making the request itself.

[TuxCoding]

Oh wow, I just checked the Mojang API. That service totally went unreliable that even a visit with a browser is declined.