Add debug command #35
Description
Would give you a set of debug commands with useful utilities:
modpack-lock debug remove <dir> [pattern]-- allows you to temporarily remove all the files in a specific folder while you test debug an error. Uses an interactive prompt to let the user indicate when they're done, then restores the folder as it was before the debug command. Also allows you to specify a file pattern to match, and will only remove files that match that pattern.modpack-lock debug bisect <dir> [pattern]-- allows you to bisect a folder, removing one half of the files inside at a time, and allowing you to check if the error persists. While it does, continue ot remove half the files until it doesn't. Once it stops the error, use the same method to test the set that was just removed, and repeat until you find the one file that is causing the issue. Uses an interactive prompt to ask the user what the result of the bisect was, and pauses while they test. Once the offending file is identified, it is quarantined and removed files are restored. Also allows you to specify a file pattern to match, and will only remove files that match that pattern.modpack-lock debug isolate <...files>-- allows the user to isolate a single file or set of files, and temporarily remove the rest of the files from the modpack, in order to diagnose problems about something specific and quarantine it from the rest of the modpack. Uses an interactive prompt to let the user indicate when they're done, then restores the folder as it was before the debug command.modpack-lock debug safe-mode-- allows the user to temporarily remove all modpack files and test if errors persist, to check if the issue has to do with the instance itself rather than your modpack content. Uses an interactive prompt to let the user indicate when they're done, then restores the folder as it was before the debug command.