turt2live
commented
7 years ago Will probably need a custom handler for this, but crafatar provides this as a header:
- X-Storage-Type: Details about how the requested image was stored on the server
- none: No external requests. Player has no skin (cached)
- cached: No external requests. (skin cached)
- checked: Requested skin details, skin cached. (1 external request) This happens either when the user removed their skin or when it didn't change.
- downloaded: Requested skin details, skin downloaded. (2 external requests)
- server error: This can happen, for example, when Mojang's servers are down. If possible, a cached image is served instead.
- user error: You have done something wrong, such as requesting a malformed uuid. Check the response body for details.
So if we check for downloaded then we'll be able to tell if the user's avatar changed.
Some incremental timer is probably needed, here's a rough outline:
- Loop over users to check for update (next 50 every 30 min?)
- Read profile data from store (username and avatar)
- Get profile data from Mojang (for username)
- Read avatar into memory (store header)
- If no previous username, or username has changed, update
- If no previous avatar, or avatar is
downloaded, update - Flag user as updated, if required.
The current system is unreliable and not great. Need to have a better, more robust way, of handling username changes, skin updates, etc.