This is one reason why you should ALWAYS run each version in its own game directory - otherwise, they try to read data files created by newer versions and crash:
Downgrading is not, was never, and will never be officially supported. You are advised to run older versions in separate directories. Otherwise, issues like this will occur.
In some cases you can even get errors that seem to indicate a completely different issue, such as a bad graphics driver; this includes versions newer than 1.5.2 (most such reports seem to be for 1.8.x; 1.7.x has its own issues as well, and other versions may have issues; at the very least, you may lose settings when you switch versions.
Most importantly, even if there seem to be no issues loading a world in the wrong version will either ruin it or prevent you from ever running it in an older version (which may as well be the same as being ruined if you only intended to play it in the older version), which I've seen happen countless times with no backups, which most people never make until it is too late (you should be making regular backups of any important data, including to a separate device/location).
The Meaning of Life, the Universe, and Everything.
Join Date:
6/11/2016
Posts:
63
Member Details
MaxPlayzzzMC, I also had the problem of old versions crashing.
No matter the reason of the problem was, the best way to avoid such problems is to run old versions in a separate working directory, ie. specified by --workDir parameter of the native launcher.
The suggestion of using separate game directory (aka Profile) may be not enough in some cases.
This is because the "game directory" still uses the same "working dir" (default = %APPDATA%\.minecraft),
which may cause problems with versions older than 1.6 .
On the other hand, as I suggested, by using a separate "working directory" (--workDir param) you can create completely separate Minecraft installation, which will not interfere in any way with versions you use in the default "working dir" (%APPDATA%\.minecraft).
Hey
So im probaly not the only person who noticed that all versions from 1.0 to 1.5 arent working and crashing.
Why is that?
This is one reason why you should ALWAYS run each version in its own game directory - otherwise, they try to read data files created by newer versions and crash:
In some cases you can even get errors that seem to indicate a completely different issue, such as a bad graphics driver; this includes versions newer than 1.5.2 (most such reports seem to be for 1.8.x; 1.7.x has its own issues as well, and other versions may have issues; at the very least, you may lose settings when you switch versions.
Most importantly, even if there seem to be no issues loading a world in the wrong version will either ruin it or prevent you from ever running it in an older version (which may as well be the same as being ruined if you only intended to play it in the older version), which I've seen happen countless times with no backups, which most people never make until it is too late (you should be making regular backups of any important data, including to a separate device/location).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
k thanks
-
View User Profile
-
View Posts
-
Send Message
ModeratorUse a different launcher like MultiMC if you want to use older versions of Minecraft.
Some older versions may need a fix if you're using Java 8.
MaxPlayzzzMC, I also had the problem of old versions crashing.
No matter the reason of the problem was, the best way to avoid such problems is to run old versions in a separate working directory, ie. specified by --workDir parameter of the native launcher.
The suggestion of using separate game directory (aka Profile) may be not enough in some cases.
This is because the "game directory" still uses the same "working dir" (default = %APPDATA%\.minecraft),
which may cause problems with versions older than 1.6 .
On the other hand, as I suggested, by using a separate "working directory" (--workDir param) you can create completely separate Minecraft installation, which will not interfere in any way with versions you use in the default "working dir" (%APPDATA%\.minecraft).