I’ve published a new minor upgrade: 0.6.1.5.
No breaking changes or features, just 10 new fixes. Thanks to Hearn who reported 8 of those, which makes him the bug reporter of the month
As usual, if you want to see all the small changes you can check the recent activity in the bug tracker. The most important changes are:
- Removing markers is now correctly reported in the log window;
- Existence and correctness of pictures in set files are now checked during set import to prevent crashes during games;
- The multiple selection lasso was imprecise on tapped cards. Manipulating cards near their edges may have some unwanted effects;
- Targetting arrows may be incorrectly placed when moving a card across the 2-sided table limit;
- Several crashes in weirds corner cases (e.g. creating a token which isn’t in your database, loading an empty deck, or adding 0 markers, …).
I also did start working on limited play (that is: drafting and such). And I would like to know what you think about print runs:
[1] I am not interested at all in limited play, so don’t even think about print runs!
[2] I don’t care about print runs. Random packs (according to rarities of course) are more than enough!
[3] Print runs would be great. They are more realists and the sequence of cards has been balanced by the game designers. I don’t really think it would be useful, though, because I don’t know of any published print runs for my favorite games.
[4] Print runs are awesome. And for the games I play, they are available here: (provide some links to descriptions of the way print runs work in your game please).
I personnally think print run support would be a nice plus for OCTGN 2, but I don’t really know of any source of print runs [3]. Without data print runs are useless, so I am currently unsure if I will code the feature.



