When this tool will be stable enough, I want to add it to the standard patch structure, are you OK with this ?
Sure, I was hoping it would prove useful. I've added a commandline routine that skips the GUI and acts as you describe (currently, the only commands are \? and \c). If you don't provide a path, it will look for the file in the current folder. Either way, it produces the .dck in the same folder as the .txt file. It will load the settings from the .ini file and use whatever settings you had the last time the GUI was used, and it still produces a NameOfDeck.log so you can see what it did.
The "compiled" version is much quicker without the GUI, but it still takes a couple of seconds to load the Cards.dat before processing the PlayDeck, so I might have it produce it's own .vod file to speed-up loading (it would check to see if the Cards.dat has changed, and produce a new .vod file if it has).
Should I keep the folder name as "PlayDeckAnalyser"? It's not too long and places the folder just below the "PlayDeck" folder in the directory listing (which is nice). It also only does 1 .dck file at a time in CommandLine mode... I'm assuming this is the desired behavior. Are there any other commands/switches you think may be useful?
Also, is there any way to determine if a Challenge Card is still locked? If not, can the list of Challenge Cards be found in a DAT\CSV somewhere? With the latest Manalink Update I get tons of PlayDecks with no NonCoded cards (over 2500), but many contain locked challenge cards and I'd like to be able to filter those as well.
Work has been kicking my butt this week so I haven't had any time to play with this, but I hope to finish a few things on it this weekend and start getting it ready for a v0.3 release before I try to tackle a few big issues with the app... like completely re-writing the ignorant way I've implimented the Banned\Restricted\Substitute lists. It'll be quicker, easier, more versatile and make more sense, but it'll take some time.