Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modpacks with the "Force Directory Change" option set do not install in the specified location #388

Open
MrLenin opened this issue Dec 10, 2013 · 1 comment

Comments

@MrLenin
Copy link

MrLenin commented Dec 10, 2013

A modpack with the "Force Directory Change" option specified does not install in the specified location.

Steps to reproduce:

  1. Set a modpack to "Force Directory Change" on installation
  2. Install the modpack in the launcher
  3. The launcher will ask for the location for the modpack to be installed to, select one
  4. Press "Play"

Result:

The directory structure for the modpack will be created in the default installation directory and the modpack installed to that location instead of the forced alternate folder as expected.

This was tested on Windows 7, 64-bit using JRE 1.7.0_45.

@artdude543
Copy link

I have this same issue, after installing my pack then changing the directory it works. But after closing the launcher and re-opening it, the launcher is forgetting my directory change. Now I can't re-select the folder because its not empty. This looks like to be a saving issue with the launcher not remembering the custom directory change :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants