Bugfix: Ensures all MD5 folders for My3DPrinter and MyAIMotions mods are deployed on launch.
Bugfix: Ensures all MD5 folders for My3DPrinter and MyAIMotions mods are deployed when enabled/disabled if using symlink deployment on mod enable..
Version 2.8
Further logic handling for MyAIMotion mods
Renamed "Deploy 3DPrinter mods on launch" to "Deploy Symlinks on Launch". Deploy Symlinks on Launch now handles deployment for both My3DPrinter and MyAIMotion mods
Changed "Deploy Symlinks on Launch" default value to true. (Ensures for better symlink handling and cleanup of residual symlinks that may not be removed if mods are not disabled)
Added setting for LogLevel so the value can be changed. (This is really just for my purposes and to cleanup the log output)
Bug Fix: My3DPrinter and MyAIMotion mods that have multiple MD5 folders within them were not all being handled
Version 2.7
Added initial handling for MyAIMotions mods. (Never uploaded to Nexus version skipped)
Version 2.6
Enhanced handling of incorrectly packaged 3D printer mods: MO2 now repackages root-level 3D printer mods and renames folders to match the .GLB's MD5 if mismatched.
Version 2.5
Added additional checks for incorrectly packaged sub directory mods.
Added checks for root packaged 3DPrinter mods
Version 2.4
Added Deploy 3DPrinter mods on launch setting. You can enable this in MO2 > Plugin Settings > inZOI Support Plugin > set Deploy 3DPrinter mods on launch to true. (This will instead deploy 3DPrinter mods on launch, rather than when they're enabled)
Version 2.3
Bugfix: corrected invalid removal of directory when disabling 3D printer mods.
Version 2.2
Added symlinking for inZOI Mod Enabler's bitfix folder and dsound.dll > Unfortunately, normal DLL injection did not suffice.
Version 2.1
Updated for better sub-directory handling.
Version 2.0
Initial plugin creation allowing for handling of most BlueClient and My3DPrinter mods.
