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
Save screenshots at one location and for the config folder, let's say we have lots of mods, and multiple instances that use slightly different mod packs but the rest of the mods need the same config, so we can symlink the config folder to sync settings between.
Suggestion
Create a button in instance settings named something like "Symlink ..." and we can choose name of folder and where it will point. Or make some sort of a system where the user could create a folder and assign instances to use that.
Benefit
Screenshots in one place, Waypoints and World Map synced, mutual ressource pack folder, synced configuration, ...
This suggestion is unique
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.
No response
The text was updated successfully, but these errors were encountered:
Generally, we do not want to touch symlinks, as the implementation differs on different platforms, plus they make a lot of stuff wonky and need special handling. What could be done, is a shortcut to those folders.
Role
Save screenshots at one location and for the config folder, let's say we have lots of mods, and multiple instances that use slightly different mod packs but the rest of the mods need the same config, so we can symlink the config folder to sync settings between.
Suggestion
Create a button in instance settings named something like "Symlink ..." and we can choose name of folder and where it will point. Or make some sort of a system where the user could create a folder and assign instances to use that.
Benefit
Screenshots in one place, Waypoints and World Map synced, mutual ressource pack folder, synced configuration, ...
This suggestion is unique
You may use the editor below to elaborate further.
No response
The text was updated successfully, but these errors were encountered: