Option to keep the highest version of a mod in the same folder (no rename/delete)

wispborne / TriOS

Starsector mod manager & toolkit.

GNU General Public License v3.0

9 stars 1 forks source link

Closed wispborne closed 1 week ago

wispborne commented 3 weeks ago

So, if someone has folder LazyLib with v1.1 and TriOS installs a new version v1.2...

Currently, we'd end up with LazyLib (v1.1) and LazyLib-1.2 (1.2).
With the option ticked, we'd end up with LazyLib-1.1 (v1.1) and LazyLib (v1.2)`.

This means that a dev with their IDE pointing to mods/LazyLib doesn't need to change anything, it'll just update their dependency.

This should pair with #70.

wispborne commented 1 week ago

When a folder is installed through TriOS, and this option is enabled,

check if this new version is higher than other versions installed. If there are other versions but this is older, skip the rest of this flow and give it a versioned folder name.
Otherwise, get the mod folder of the current highest version of the mod. If it exists, generate a versioned folder for it and move its contents there.
Get either the previous highest version folder's name or else the name of the new higher version's folder, and create that folder if it doesn't exist.
Move/extract the new mod's folder contents into that folder.

Result: highest version folder name doesn't change. New mod is installed. All versions lower than the highest have versioned folder names.

wispborne commented 1 week ago

Done in 0.2.0