MCL-416minecraft launcher uses old directory even when a new one has been given
I created a new player profile and changed the minecraft directory to a dropbox folder. The game loads/plays just fine, It just saves everything in the old directory. so basically: the directory feature doesn't work for me
Environment
windows 7
Linked Issues
is duplicated by3
Created Issue:
minecraft launcher uses old directory even when a new one has been given
I created a new player profile and changed the minecraft directory to a dropbox folder. The game loads/plays just fine, It just saves everything in the old directory. so basically: the directory feature doesn't work for me
Environment
windows 7
Added Linked Issues:
relates to
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
Added Assignee: ![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png)
[Mojang] Nathan Adams
[Mojang] Nathan AdamsAdded Linked Issues:
is duplicated by
Added Linked Issues:
is duplicated by
Added Linked Issues:
is duplicated by
Added Fixed Versions: 1.1.1
Added Attachments:
Added Attachments:
Added Linked Issues:
relates to
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Changed my directory to a normal folder, like C:/Minecraft/.minecraft, doesn't work too. Bug? Or is this feature not ready yet?
Folders have to exist, before you can start playing from there.
I know, this is my directory "C:\Users\Maarten\Dropbox\Minecraft"
I allready added a folder called minecraft to my dropbox
@Maarten:
The new launcher does not download any files to the new directory, you have to move them manually from the old to the new one. Then it should work. Unfortunately, there seem to be other problems too:
MCL-446. Does this happen to anyone else?Following launcher versions aswell:
+ 0.9.1
+ 0.9.2
... Why reopened?
I created a new 1.5.2 Version with Forge in it, and then created a new profile to use this version an the folder of a working FTB pack.
The game started correctly but there were no mods and the texturepack and saves folder were obviously in the old MC directory, so from my point of view, this post has to be open.
Daniel, pre1.6 doesn't observe directory settings.Oops I was wrong
Ezekiel, it does. I've tried it with 1.5.2 and 1.5.1. It will download and install to a new directory if it's a new version, but if you try to change the directory again it doesn't acknowledge said change. This becomes a problem with local only versions because they're never installed to begin with.
Edit: Nevermind. It works for any version that exists on the new launcher. Local or kept up to date on remote. So any 1.6, 1.5, or snapshot shown on the launcher will be able to change their game directory where they see fit. The version I need working is 1.4.5 which isn't listed.
Tl;dr: The problem isn't with pre-1.6 jars. It's with jars not on hosted on the dev launcher. (1.4 and under)
Blaze, I later noticed this. Any versions not up to date with remote don't seem to be able to switch folders.
Ezekiel, that's not entirely true either. =P As long as there is a version on the launcher it'll work regardless of being local or being kept up to date with remote.
For instance. If I make a copy of 1.5.1 and rename it to something else, it's no longer "up to date with remote" but rather it's only "local". However. Because the launcher has a 1.5.1.jar on it it'll work. A 1.4.5.jar or lower won't work though.
Is this still a concern in the current Minecraft / Launcher version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I think it's fixed
Thanks.
It's not fixed. In the image I just attached you can see I'm running my .jar with the custom directory but nothing is in there but the server.log file. I'm on launcher 1.1.1.
@BlazeFaia:
Minecraft 1.4.7 ? Forge ? Optifine ? MCP ?
Recreate with vanilla 1.6.2.
But the title of this bug report doesn't specifically state 1.6.2. Just that new directories don't work. So even though it works for 1.6.2-1.5.1 anything lower doesn't work. That's still a bug that needs to be fixed.
Also whoops, meant to say 1.4.7. Not 1.4.5.
Works with vanilla 1.5.2
I said it worked with 1.6.2-1.5.1 XP What it wasn't working with was 1.4.7. Well. It WASN'T working. I tried a fresh vanilla 1.4.7 and it worked. Tried to install Forge and I got the same problem. So Forge is the problem here. Looks like this problem is indeed fixed.
@BlazeFaia:
If one of the two things is missing, it won't work.
I don't see Client> Setting gameDir to:<path>
I'm assuming that has something to do with Forge. But I need Forge. Any tips. =x
This is an issue for me with v1.2.2 of the launcher.
I'm using "release 1.3.2" for the game version, and trying to change the game directory to "F:\Downloads\Vanilla\v1.3.2". The game runs, but it uses the default game directory.
@Sean Anderson : That issue is
MCL-1394I fail to see how this and
MCL-1394are different.That issues are clearly related, but this issue is "doesn't work at all" ,
MCL-1394is "doesn't work always"