Releases: iquercorb/OpenModMan
Open Mod Manager 1.3.3
Open Mod Manager 1.3.2
- Fixes issues and inconsistencies related to Library folder and Mod folders changes tracking.
- New flexible dependency resolving mechanism allowing version number wildcard.
New flexible dependency resolving mechanism
Open Mod Manager now have a more flexible dependency resolving mechanism that parses wildcard * in version number of declared dependencies entries. It is now possible to declare dependency in the form : Mod_name_v* or Mod_name_v1.* to allow any version of the declared Mod to be selected as compatible candidate. In case of multiple candidate (If multiples versions of the same Mod are available), the one with the greater version is selected.
Beware, the mechanism only work for version numbers, this mean that if you declare something like Mod_name_* (without the v), the parser will simply ignore the * and consider you declared the dependency for a Mod named Mod_name_* (which is not a valid file name).
Open Mod Manager 1.3.1
- Fixed click on Network Library header triggers resize process
- Fixed (sort of) Mod install may overlaps in case of install in progress
- Fixed backup data deleted even in case of restoration error
- Fixed Mod Presets not properly updated during supersede process
- Fixed Repository Editor doesn't save Repository description
- Changed network library "upgrade" and "downgrade" status icons, removed "new" icon.
- Unify logic for downgrade and upgrade Mod download
Open Mod Manager 1.3
- Added alternative installation process to allow or forbid Mod overlaps at install (with automatic uninstall of conflict Mods)
- Added option to disable confirmation dialog when opening external links from Mod description
- Changed logic for dependent and dependency Mods status indications (blue check now indicate Mod is an install dependency)
- Fixed various glitches related to layout (splitters) changes/resizing
- Fixed Mod-Pack Editor file name preview not correctly set at initial Mod parsing
- Fixed Mod-Pack Editor's save button that still disabled after Mod build from a directory
- Fixed progression dialog text that flicker and disappear while refreshing
- Fixed message dialog detail text that overflows dialog box (making it not easy to read)
Open Mod Manager 1.3 Beta
- Added alternative installation process to allow or forbid Mod overlaps at install (with automatic uninstall of conflict Mods)
- Changed logic for dependent and dependency Mods status indications (blue check now indicate Mod is an install dependency)
- Fixed various glitches related to layout (splitters) changes/resizing
- Fixed Mod-Pack Editor file name preview not correctly set at initial Mod parsing
- Fixed Mod-Pack Editor's save button that still disabled after Mod build from a directory
- Fixed progression dialog text that flicker and disappear while refreshing
- Fixed message dialog detail text that overflows dialog box (making it not easy to read)
Open Mod Manager 1.2.9
- Fixed deleted installed Mod not properly handled
- Fixed Mod Directory (dev mode) description not properly refreshed
- Add Mod Directory (dev mod) overview automatic refresh
- Fixed target directory can be changed while Mod installed (can cause dada corruption)
- Fixed deleting repository do not properly clear related Mods and may crash application
- Add resizable Channels List, Presets List with per-Hub save
- Add resizable Network Library's Repository List with per-Channel save
- Add Hud options to hide Channels and/or Presets Lists
Open Mod Manager 1.2.8
- Fixed Repository Editor always add .omx extension at end of saved file name
- Fixed Mod Upgrade throw error message if old Mod is installed
- Fixed Mod Library sort by status not properly secondary sort by name
- Fixed not working keyboard shortcuts in Mod-Pack Editor and Repository Editor
- Fixed Mod-Pack Editor inconsistently detect unsaved changes in some cases
- Fixed Mod can be packed with dependency reference to itself (and cause infinite loop)
- Added Mod Library new status icons to identify dependency state of installed Mod (see details below)
- Added Mod Library feature and option to perform Complete Uninstall as default action (see details below)
New installed Mod dependency status
The Mod Library list-view now show the installed Mod dependency state in the Status column by a specific check mark color:
- A Blue check mark signals that installed Mod has satisfied dependencies
- An Orange check mark signals that installed Mod has unsatisfied dependencies
New Option to perform Complete Uninstall as default action
The "Complete Uninstall (clean dependencies)" command is the new designation of what was previously named "Clean Uninstall". This command is only allowed for installed Mod that have dependencies and is used to perform an extended and recursive search of Mod dependencies in order to Uninstall the Mod and all its dependencies.
By default, this command is only accessible via the Mod Library's contextual (right-click) menu while a double-click (default action) on an installed Mod perform a classical Uninstall. It is now possible to set the Complete Uninstall as the default action (double-click) when it is possible. The option is located in the Channel properties, "Mod Library" tab and is labelled as "Perform Complete Uninstall as default action".
Open Mod Manager 1.2.7
- Fix downloaded large files not properly recognized as zip file
- Removed deprecated configuration migration routines
Open Mod Manager 1.2.6
- Fixed network repositories package thumbnail does not properly display
- Fixed repository global download path do not properly handle full URL
Open Mod Manager 1.2.5
- Fixed downloaded Mods do not properly upgrade