Future Enhancements

Here’s an update of the list of work planned for future development:

Github/Patreon – More updates to the Github and Patreon pages to add functionality.

Optimization/Performance – More changes of this nature are in the pipeline.

Code Signing – I’d like to purchase a Code Signing Certificate and start signing the application’s executables with it so that Windows Defender/SmartScreen trust will start building up and we can get rid of the nag screens. Unfortunately the cheapest route to doing this costs around $100 a year, so that’s where I hope Patreon might help.

Improved Replacement Suggestions – Currently the replacement suggestion algorithm is quite basic and just uses a fixed “score” on each card when making the suggestions, and especially when it comes to lands, it can leave something to be desired. For example, sometimes it will suggest Stone Quarry when Wind-Scarred Crag would be a better replacement, and it can over-suggest dual lands that always enter tapped when playing more basics would probably be better.

Settings/Options – Add a settings/options area or screen where different sorting options/criteria, font size, log file location (if non-standard), etc., can be selected.

Filters – Add filters to allow showing/hiding based on criteria like rarity count, resilience to rotation, only decks you have cards for, only decks you can complete with wildcards, etc.

Formats – We’ll need to add support for Historic after rotation, and it would be nice to get special event formats, as well.

Data Sources – The deck data has improved a lot over the past week, but I still want to look more into alternate/additional data sources for deck information.

Mac/Linux Support – I’d like to look into better support for using this application on a Mac or Linux machine, either through more guidance on running it via Wine, or perhaps creating a non-GUI version of it that can run natively on Mac/Linux that just dumps out reports.

User Documentation/Release Notes – No tool like this can really shine without having a set of documents that users can go to to get help using it, and to see what changes come with new releases. So far I’ve just done these weekly blog posts, but want to get something better put together (this will likely end up being part of the GitHub effort).