search

wispborne / TriOS

Starsector mod manager & toolkit.
https://fractalsoftworks.com/forum/index.php?topic=29674.0
GNU General Public License v3.0
14 stars 1 forks source link

Feature request: Option to avoid renaming any mod folders #97

Closed nissa-seru closed 2 months ago

nissa-seru commented 2 months ago

I do the following to each of my mod folders:

  1. Rename them (so that I can easily reference them without interfacing with the idiosyncrasies of each mods' naming)
  2. Maintain a git repo in them (so that I can easily track+test typo fixes/proofreading locally before PR-ing them.

The implementation in #78 is compatible with (1) as well as its stated aim to avoid disrupting path references to mod folders; it is much less compatible with (2). If it's not too much trouble, I would be grateful for an option for TriOS to simply avoid renaming any folders in the /mods directory at the time that it creates a folder for the new version of a mod. I'm aware that this feature would see very little use (and am more than happy with tweaking some config files or similar if it doesn't make sense to expose via the UI.)

wispborne commented 2 months ago

That seems reasonable. With a warning, maybe an Advanced Settings section.

nissa-seru commented 2 months ago

Perfect, thanks! Thinking out loud - I'm unsure how the Dart implementation of file operations handles name conflicts; perhaps worth including in the warning for documentation iff exposing via the UI.

On Wed, Sep 18, 2024 at 12:08 PM Wisp @.***> wrote:

That seems reasonable. With a warning, maybe an Advanced Settings section.

— Reply to this email directly, view it on GitHub https://github.com/wispborne/TriOS/issues/97#issuecomment-2358877104, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4NBSEUCXF5F7VRQOIHCD5LZXGQQVAVCNFSM6AAAAABONBJWTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJYHA3TOMJQGQ . You are receiving this because you authored the thread.Message ID: @.***>

wispborne commented 2 months ago

Added in 0.2.7