-
Bug
-
Resolution: Awaiting Response
-
None
-
1.5.3
-
None
-
Linux amd64/Oracle JDK 1.7.0_67
-
Unconfirmed
I play using a custom profile that inheritsFrom 1.7.10. I experience skins missing in-game and notice in the log that authlib/realms are on older versions (1.5.13/1.2.6 respectively). Upon inspecting versions/1.7.10/1.7.10.json, the authlib/realms libs listed are the outdated ones. Only upon running an empty vanilla 1.7.10 profile will the authlib/realms libs update to the latest (1.5.16/1.3.5), whereby the custom profile will then use.
What I expected to happen was...:
The parent 1.7.10 profile to automatically update its libraries (specifically authlib/realms) when running a custom/child profile inheriting from 1.7.10.
What actually happened was...:
Parent profile didn't update.
Steps to Reproduce:
You first need a child profile that inheritsFrom 1.7.10.
- Make sure that versions/1.7.10/1.7.10.json has outdated authlib/realms library entries. If they are updated (1.5.16/1.3.5), simply manually edit the JSON to make them outdated (1.5.13/1.2.6).
- Run the child profile from the launcher.
- Check the logs/classpath and notice that the authlib/realms used are the outdated versions (1.5.13/1.2.6) instead of the updated ones (1.5.16/1.3.5).
As mentioned earlier, running a vanilla 1.7.10 profile will force an update, but it'd be nice for it to auto-update. I can provide more details on request.