lukebemish
- lukebemish
- JIRAUSER737506
- Europe/Stockholm
- Yes
- No
MCL-23087After installing the launcher on linux from the tarball under "other", I attempted to run it somewhere other than ".minecraft" using "--workDir"; this results in everything I knew to look for being placed in the expected directory, except the launcher log which was placed in ".minecraft"
Steps to Reproduce
1) Download the minecraft launcher as a tarball from the official minecraft website
2) Run the launcher from the terminal, passing it the workDir argument. For instance:
mkdir launchertest ./minecraft-launcher --workDir launchertestObserved Results
The launcher's files are for the most part put into the correct folder which you just created. However, the "launcher_log.txt" file is always places in "~/.minecraft" no matter what you specify
Expected Results
The "launcher_log.txt" file would be placed alongside the other launcher files when using "--workDir".
I've updated the issue including more in-depth steps to reproduce the problem.
I have only observed this issue on Kubuntu (a deb installation) with the tarball containing the launcher. I have not tested it on any other installations. I am trying to use a custom .minecraft directory by setting the --workDir argument, which works, with the single exception of the launcher_log.txt file, which is placed in the "default" .minecraft location (~/.minecraft) no matter what I do. I can reboot the launcher as many times as I like, and it will never place the launcher_log in the proper location.
I just tested this on the latest version, with a fresh install of the launcher; the bootstrap_log and launcher_log are both still created in the .minecraft directory instead of in the workDir directory.