ZK has been Greenlit!

Few weeks later? In a rush are we, eh?

:P meh atm is the worst time to release, most people have or have just finished exams, this is the time for casual games of relaxing

Well if you would have said few months later. I still would think its quite a rush, unless you are planing to stick with old engine. Think like debian release when its ready, dont follow some stupid deadlines.

so will curent players have to change acounts or anthing??

It is real when everyone except devs are speeding around earth at 299 000 km/s

Wow, I'm not the least bit surprised it was greenlit but that was pretty fast.

Perhaps a link and concise instructions with a bold "There be dragons ahead" warning in the description could still bring enough brave newbie souls to find the weak spots to fix before official release?

Just winning each award N times (1, 10, 100), first-time building certain units, and hitting certain ELO values would make good achievements.

quote: I hope game will switch and test a to perfect a new engine so we have perfect Linux compatibility

this. It looks like from people's reactions that .91 and .96 engines put us in this terrible Catch-22 of ".91 is the worst engine except for all the others that have been tried". Would dedicated ZK fork of Spring (probably forking .91) help?

What exactly is wrong with 91?
Im not defending keeping it instead of moving on, but curious to what isn't working as intended.

quote: What exactly is wrong with 91?

Newer engine versions generally have "more stuff and fixes." But it is imo only partly about if game needs this stuff.
It is also about spring as organism in general.

Example quote from from http://springrts.com/mantis/view.php?id=4384

quote: sorry, i refuse to investigate crashes in such an old engine version as its very likely fixed in the current version. [...] also the current stacktrace translate doesn't work for this old version, so it would require doing this manual -> a lot of work.

So it seems engine devs are unable/unwilling to investigate crashes in old engine versions.

Everything in spring organism is kind of connected with each other: Games copy stuff from each other, players provide bugreports on game or engine etc. So it goes and grows.
If a gameproject removes itself from this feedback looping then it weakens whole organism. And thus, after some time, also the gameproject itself.

quote: Perhaps a link and concise instructions with a bold "There be dragons ahead" warning in the description could still bring enough brave newbie souls to find the weak spots to fix before official release?

Better yet, put this on download page:

(make better grahic, maybe)
Think such videos would provide really good ideas about what needs to improve, where players struggle, what they try to do first and so on.
Is done in any software/product testing.
Nowadays recording video is common. Many players stream to twitch.tv when playing games etc, so it at least has a chance for sucess?