Valid paths given via CLI do not need to be interactively queried.

• user-defined version name
• version notes

Also

• Validate that selected version still exists if not "latest" else set to latest
• consider --preserve-config option to not delete the mod config file

I just need to convince myself to stop being lazy 😉

The current newest tagged version is incredibly out-of-date (0.1.0).

The Changelog needs to be expanded to include all of the changes since then, and a new release should be tagged, so people don't try to use the ancient version.

In the meantime, I recommend that everyone interested in trying out modfs use the newest commit on the master-branch.

Change the code so subversions begin at 00 instead of 01.

No need to waste a perfectly good slot, after all.

subversions should cap out at 99 and additional attempts to create versions fail.

there should be a way to signal that an instance was created / managed with another version of this software that may not be compatible.

See details on compatibilityversion.txt in docs/ directory

This configuration should allow the user to

• disable a mod
• select a non-latest version to deploy
• Assign the following metadata:
  • pretty name
  • author name
  • custom notes

This information will be stored in a .json file on the same level as the mod directories and share the name of it's mod.

mods/ussep/ -> mods/ussep.json

already in progress