onetwo three

Has been more than 2 months and no update. Is there any confirmation that this is even on the roadmap for the future, or if you do not plan to fix this, just close the issue -  no point keeping this issue open if there are no plans to fix it.

Dinnerbone himself has discussed this endpoint on Twitter in the past (see https://twitter.com/dinnerbone/status/554739042529849345).  I see no reason for it to be removed. No update in almost a month from Mojang staff.

While I'm at it, the fact that there is no notice whenever an API update occurs is a pet peeve of mine. If Mojang deprecates something it's up to the user to figure it out. We're not given any notice of that. It would be nice for API changelogs to be released whenever there's a new version or update. Especially considering that the entire API changed recently due to the MSA migration, and lots of old tools and programs will most likely stop working. How are we supposed to find the equivalent endpoints on the new API?

Jake (or should I say Legendarisk? That's what popped up in my email notification...), I didn't say that the creation date was the only thing this endpoint was good for. My mention of Jomo's program was simply because I know that program is incredibly useful for servers in order to find cheaters on new alternate accounts. This program has existed for years without any issues and this API change essentially kills it, which I don't think is intentional (as Mojang could've killed this program many years ago if they so chose).

Adam, I fully agree with you. This is a very smart way of going about the issue you've been given, and I'm also collecting data on numerous Minecraft accounts (currently have about 12 million UUIDs saved) - this method would be great to get more UUIDs and collect more data... shame that this has been removed now.

I hope Mojang can understand the many use cases of this endpoint and will add it back.

Hi Mr. Horndahl,

I've just checked the API and noticed a new version was pushed, which I assume was this fix.

Thanks for the quick patch, this issue can be closed now 🙂

Hi Mr. Sjödahl,

The impact is that users cannot fetch the current username of a user that has changed their name. For example, let's say we had a user with the name "test_account" - they had the name "simonatator11" which was their name at 1423422139. However, they have since changed their name and we don't know their current name. We would use the endpoint https://api.mojang.com/users/profiles/minecraft/simonatator11?at=1423422140 (one second after they changed their name to simonatator11) to find their current username and UUID. This endpoint is currently broken, since if we pass in this time, when they did, in fact, have this username, it still shows up as 204 No Content when it should return 200 with the user's current name (test_account) and their UUID (3d28908693324417bb78f90c3cc5e0b7). Alternatively, requesting the name "Test_Account" and passing any Unix time in the ?at= parameter returns 200 when it should return 204 for any time before 1426100819. A further explanation of this is located here: https://wiki.vg/Mojang_API#Username_-.3E_UUID_at_time

We also can see that this program (finding a Minecraft account's date of creation) is impacted by this issue as well, and no longer functions correctly - https://gist.github.com/jomo/be7dbb5228187edbb993 This program has worked for years and today it has stopped working as well.

Maybe someone has the name Trapezoid on other gaming services and would like to match instead of having to use Tr4pezoid or something similar. Perhaps the filter could be checked against a wordlist so that names like Trapezoid or Grasshopper, being English words with no bad meaning, could be unfiltered and put on a whitelist, while leaving the other vulgar names/phrases blocked. Also, is that you, Wreeper?