The new launcher features a (Default) profile which is set to use the latest version. However, when I install another profile by adding a new folder to the "versions" directory, that jar file comes up as most recent.
It's simple to work around this just be creating a new profile for the current version, but the fact that this problem is there troubles me. Is there a way to make it so that "latest version" will always be the latest Mojang release?
Also, I noticed the Forge profile doesn't have this problem. It comes up at the bottom of the list, and "latest version" doesn't consider it. So I know there must be a way...
Thanks!
Rollback Post to RevisionRollBack
WIP 128x 64x, SEUS support, Mod support in the pipeline TEKKIT, FTB, the more support the more mods!
Probably, because of the new update it thinks that the earlier version is the latest version? It might be a bug. The simplest way to fix this is to just make new profile. Shouldn't be to bothersome.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
It's simple to work around this just be creating a new profile for the current version, but the fact that this problem is there troubles me. Is there a way to make it so that "latest version" will always be the latest Mojang release?
Also, I noticed the Forge profile doesn't have this problem. It comes up at the bottom of the list, and "latest version" doesn't consider it. So I know there must be a way...
Thanks!
WIP 128x 64x, SEUS support, Mod support in the pipeline TEKKIT, FTB, the more support the more mods!