My idea is to add a menu item that allows you to select a version of Minecraft from a list. This could be useful for updates that break mods and for the lazy people who don't want to switch their jar files. What you would do is place your extra jars in a separate folder in the ".minecraft\bin" folder; for example it could be ".minecraft\bin\oldver" (Obviously would differ for Mac and Linux). The minecraft.jar in the "bin" folder but not in the "oldver" folder is the default and fail-safe minecraft.jar (fail-safe for if the one you are using breaks, is corrupted or is deleted). If however the main one breaks, Minecraft will alert you and start with the latest version in the "oldver" folder. Every time Minecraft updates, the one you are currently using is placed in the "oldver" folder, thus no more breaking of your mods when Minecraft updates because you can easily switch to it and back. When an old version is placed in the "oldver" folder it is given a sub-folder based on the version it was. For example; version 1.6.6 would be ".minecraft\bin\oldver\1.6.6\minecraft.jar" and given the name "Minecraft Beta 1.6.6" etc.
My idea is to add a menu item that allows you to select a version of Minecraft from a list. This could be useful for updates that break mods and for the lazy people who don't want to switch their jar files. What you would do is place your extra jars in a separate folder in the ".minecraft\bin" folder; for example it could be ".minecraft\bin\oldver" (Obviously would differ for Mac and Linux). The minecraft.jar in the "bin" folder but not in the "oldver" folder is the default and fail-safe minecraft.jar (fail-safe for if the one you are using breaks, is corrupted or is deleted). If however the main one breaks, Minecraft will alert you and start with the latest version in the "oldver" folder. Every time Minecraft updates, the one you are currently using is placed in the "oldver" folder, thus no more breaking of your mods when Minecraft updates because you can easily switch to it and back. When an old version is placed in the "oldver" folder it is given a sub-folder based on the version it was. For example; version 1.6.6 would be ".minecraft\bin\oldver\1.6.6\minecraft.jar" and given the name "Minecraft Beta 1.6.6" etc.
Did you think of the ammount of minecraft.jars? it needs to reload the game with that minecraft.jar every time. also, theres no need, because youve got everything from other versions in new ones.
Did you think of the ammount of minecraft.jars? it needs to reload the game with that minecraft.jar every time. also, theres no need, because youve got everything from other versions in new ones.
No, its useful because you can have 1.7 and an older version with modifications because modifications break the newer releases, so you can quickly test the new versions and then easily go back to your awesomely modded game. As for the "amount of minecraft.jars", you can clean them out whenever you want (there would be another button in the menu for that purpose). Also, you are right about the restart, but I would assume that it would a. Would be for the release that its added and after (e.g 1.9 and onward) or b. Switching back to a compatible version could be handled by the launcher. But you make good points there.
Screenshots:
whats a verson?
Oh god haha. Darnit. Well I mean't version. Lol. I shall fix that error.
EDIT: Fixed it. :biggrin.gif:
Haha, lol it's cool. Overall= VERY GOOD IDEA! for 1.9 though
1.8 is full of adventure mode and villages and ruins and stuff
Thanks, I guess its also an idea for a modder if someone wants to do that.
But yeah, it would be good for 1.9
No, its useful because you can have 1.7 and an older version with modifications because modifications break the newer releases, so you can quickly test the new versions and then easily go back to your awesomely modded game. As for the "amount of minecraft.jars", you can clean them out whenever you want (there would be another button in the menu for that purpose). Also, you are right about the restart, but I would assume that it would a. Would be for the release that its added and after (e.g 1.9 and onward) or b. Switching back to a compatible version could be handled by the launcher. But you make good points there.