C2, hands down. I put years of work into loot pursuit in CC and still restarted in C2, and it wasn't just to be able to deploy to more platforms. CC is basically a minefield - some people seem to have no problems, and others encounter tons of them. With loot pursuit, on one event sheet CC would freeze for 7 seconds every time I edited something. If I pressed undo It would lock up for 30 minutes. Copy often didn't work. Placing events was inaccurate (misplaced that event? Wait another 7 seconds to try again). There's still a memory leak hiding somewhere. I still got crashes at runtime. It's just plain not worth the risk.

C2 has a much better workflow, is getting updated frequently, is far more stable, exports to more platforms, etc etc... There's pretty much no reason to use CC anymore with C2 around.

And don't worry about being forced to make 'web mini games' because you're not. With node webkit the output is visually identical to a native exe. The only difference is what's running under the hood which makes no difference for most people anyways.

A game by Alspal was released recently using node webkit: http://www.scirra.com/forum/angvik_topic69145.html

@tokinsom - you actually can preview as exe, though it takes a little setup. All you need to do is make a node webkit application that goes to the preview URL via the browser object at the start of the layout, then when you're working on the game you want to preview as exe, press preview, close the browser it brings up, then open the node webkit exe. Now when you hit preview it will update the node webkit window with one click instead of another browser.

[QUOTE=Arima]you actually can preview as exe, though it takes a little setup. All you need to do is make a node webkit application that goes to the preview URL via the browser object at the start of the layout, then when you're working on the game you want to preview as exe, press preview, close the browser it brings up, then open the node webkit exe. Now when you hit preview it will update the node webkit window with one click instead of another browser.[/QUOTE] ...Wow

@Arima owo interesting. Thanks for the tip!@Janroth I just meant you'll still be developing desktop games the same way you would browser games (like using webstorage/AJAX/project files instead of the usual external files..but with Arima's .exe preview idea that might not be the case) - you definitely aren't limited to crappy little minigames! I've never run into any performance issues or anything with C2 out of the 8 projects I've worked on with it!

Argh - I spoke too soon guys. Sorry, but what I suggested doesn't work, because at a glance of the preview source, the node webkit plugin seems to be disabled at preview (the var isNodeWebkit is set to false and such) - so while you can preview in node webkit, you can't use any of its specific features. Gonna ask Ashley if this can be fixed.

Sorry, I should have tested it more thoroughly.Arima2013-07-03 04:08:21

Thank you so much guys! You really encouraged me to finally start creating the project with C2. The Guild Wars game and especially Angvik look like great games and seem to go the same direction as I want to go with mine. Would be awesome if previewing with the node webkit would work in the future!

I'm concerned about the "mini web games" stereotype. In several ways, C2 is actually faster, more efficient, and more stable with large projects than our old native engine. I'd actually say it's more suitable for large projects.

I'll look in to fixing the node-webkit preview issue...Ashley2013-07-03 13:03:47

A button to preview directly in node-webkit is really missed. Not a hard addition and great feature.

About the stereotypes...

The stereotypes will go away as soon as more and more 'desktop level games' made in C2 start to appear. I don't even mention mobile games. C2 needs more games like Iconoclasts which is brilliant and would never work in a touch screen (But in a console would). Mobile is not everything. Now that C2 has Desktop support there's no limit to the possibilities.

But there's complicating factors involved like the stereotype that web games are all simple mini games (Shame on me, my only game on Arcade is a mini dumb game :D). Until recently HTML5 platform was too immature to make big complex games but now it's finally ready. Or almost.

Another factor is that making games in pure JS is a terrible experience (Not everyone knows of C2 :D). C2 is here to save us all of that of course.

And another is that C2 is treated by many as a game maker for non programmers or entry level programmers (It's announced as such in fact, a mistake imo). The problem is that it attracts many people that are just starting , not exactly a bad thing, since there's many very talented amongst them, but scares away many experienced developers who are making those awesome 'desktop level' games in other engines.

Of course there's lot of pre-conceptions involved with web games etc. Those are still very hard to break. Flash is the culprit ! :DKiyoshi2013-07-04 02:03:43