Evo's problem was that the lobby system in spring (all lobbies) is woefully inadequate. However, my pain has been everyone's gain because it highlighted some of the sharpest issues.
If you look at the reviews of evo on steam, you will see that the vast majority of them have to do with the lobby, a lesser percentage complaints about no proper tutorials (even though they exist, but are not ingame, which is a foul ball), and you can probably count on one hand issues with the game itself, and 3/4ths of those are issues with ATI cards and spring.
This is why I get all up in arms when people say stuff like "evo is buggy", oh no the hell it isn't. There is one very rare issue that happens thanks to oddness in zk chili, which I have bandaged to prevent luaui from crashing altogether. Ideally at some point I can replace all the zk chili crap that I use anyway with something better, but for the most part, issues with the game itself are exceedingly rare.
Therefore, the bottleneck is the lobby system. Get the lobby system off the ground, and all of a sudden, issues start resolving themselves. Unfortunately for zk, licho thought it would be a good idea to split to a different server (a move which I consider to be a net negative for zk and a net positive for everything else spring related) which has massively increased the workload needed and split the potential for devs helping in half...
That said, I knew good and damn well that these issues would exist whether I waited or launched. Unfortunately I set my launch date too early on accident and screwed the pooch on that one, but the end result would have been the same regardless.
tl;dr: at this point you might as well package it up and release it, cause otherwise it will never get done at all. What are you going to do if steam decides to revoke your greenlight because you haven't used it? That would be a damn shame. Fact of the matter is, zk probably has a large enough community to overcome the issues that evo ran into and come out the other side looking pretty grand.
