It's time for a post mortem on how we did on the top issues for this forum:
Thank you all for the posts!!! I counted over 50 distinct ideas and I've recorded every one. Even though they may be known, the prioritization is useful. I've organized them by the number of distinct posters who supported them (unscientific I know but better than nothing.) Based on that, here are the top 10 (or so):
1. Always-visible game logs (on non-mobile)
YES, this was put into 2.0 for non-mobile. (#8 on the new features list)
https://forum.makingfun.com/showthread.php?7889-Exiting-Open-Beta-Sunset-of-Goko-Site2. Automatch
YES, the seeking feature in 2.0. (#6 on the new features list)
3. Kingdom cards on 1st page (esp. if ruins, bane)
YES, in 2.0 the number of displayed piles was upped to 12 for a wide screen resolution from Goko's 10. (#7 on the new features list)
In 2.1 it was further increased to 14 piles. The Ruins pile was relocated by the Curses so it didn't take up a kingdom slot. Some piles such as prizes were consolidated into a single pile
https://forum.makingfun.com/showthread.php?10154-Release-Notes-v-2-1-with-Adventures4. Real kingdom generation
YES, in 2.0.41.
https://forum.makingfun.com/showthread.php?7785-Release-Notes-v-2-0-415. Better reconnect
YES. This was improved over multiple releases of the 2.0 beta and overhauled in 2.0.47.
6. Button options instead having to drag
PARTIALLY, for example using the trigger resolution dialog added in 2.1. This was a work in progress.
7. Support Adventures set
YES, in 2.1.
8. VP Counter
YES in 2.0, with updated seeking options in 2.0.46.
9. Blacklist
NO. This (and other social features) would have been released in late Spring 2016, but we heard the license news and had to shut down development.
10. Prevent misclicks
YES in 2.1, when key buttons were relocated to address this.
11. API
NO, because we deemed this less important after a mod was released. It seemed sufficient in the short run to just make sure no code was obfuscated.
12. Who-goes-first adjustments
NO. Again, it certainly would have been implemented in 2016.
13. Rematch
YES in 2.0. (#9 on the new features list)
So we'd managed to get as far as 9.5/13 of these particular requests. Thanks again for all your input.