You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.
You may use the editor below to elaborate further.
In https://github.com/MultiMC/Launcher/wiki/Directory-Structure, the information given is very helpful, but it would make sense to mention where the root directory is at the top of the same page. My suggestion is below--apologizes for any errors.
Of course, you would first mention buttons like Folder > View Instance folder.
Then mention the default locations. It's always the same location MultiMC or multimc.exe is installed to.
On windows, wherever you extracted your zip file
On linux and mac, ~/.config/local/multimc
As a final note, on my linux install, I don't actually /have/ a graphical file browser, so all the "open folder" buttons couldn't work even in theory. I would have found documentation extra helpful for this reason.
The text was updated successfully, but these errors were encountered:
Role
I both make and play modpacks
Suggestion
(docs, see below)
Benefit
(docs, see below)
This suggestion is unique
You may use the editor below to elaborate further.
In https://github.com/MultiMC/Launcher/wiki/Directory-Structure, the information given is very helpful, but it would make sense to mention where the root directory is at the top of the same page. My suggestion is below--apologizes for any errors.
Of course, you would first mention buttons like Folder > View Instance folder.
Then mention the default locations. It's always the same location
MultiMC
ormultimc.exe
is installed to.As a final note, on my linux install, I don't actually /have/ a graphical file browser, so all the "open folder" buttons couldn't work even in theory. I would have found documentation extra helpful for this reason.
The text was updated successfully, but these errors were encountered: