Moerill / fvtt-find-the-culprit

MIT License
8 stars 10 forks source link

Need a recovery method on failure #11

Open justinrpurdy opened 3 years ago

justinrpurdy commented 3 years ago

Often during a Find the Culprit session, Foundry chokes and must be restarted. In this instance (and some others occasionally), this leaves the user in a position to have to try to remember which modules they had active prior to starting, especially if they didn't perform an export beforehand. If Find the Culprit automatically generated and exported a list of active modules when starting its workflow that could be imported by the user to restore the previously active set of modules, that would alleviate a lot of the issue.