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
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
While this may be intended behavior, BCML will clear the contents of any target directory when chosen for an export.
This was learned painfully as BCML wiped out 3 hours of mod merging work when the goal was to have the export come out merely sharing the same root folder.
BCML should offer a warning at least, or toggle for this behavior.
The text was updated successfully, but these errors were encountered:
jedinjapan
changed the title
BCML Explort Folder Wipes Contents
BCML Export Folder Wipes Contents
Dec 11, 2022
Related:
Changing output target does not delete/clear previous symlinks/junctions built by BCML, and will instead enjoin 3+ folders into the output > merge target including all previous locations symlinked.
In my circumstance this began with targeting my User\Downloads directory, and after moving the target learning it will erase the contents of this folder, finding that BCML merges continue to erase the Downloads folder due to pre-existing symlink despite settings change. BCML would benefit from having a check/request to remove junctions/symlinks established previously when moving the merge output target. In this case (on Windows) this required deleting and recreating a user profile folder so it can function correctly.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While this may be intended behavior, BCML will clear the contents of any target directory when chosen for an export.
This was learned painfully as BCML wiped out 3 hours of mod merging work when the goal was to have the export come out merely sharing the same root folder.
BCML should offer a warning at least, or toggle for this behavior.
The text was updated successfully, but these errors were encountered: