Thanks :-)
As with Construct 2 and 3 - will 3 definitely get a runtime version? Also how much different will it be in terms of interface and stuff like that. Like when I learn C2 now - will I feel at home when C3 "launches"?
That sounds very convenient indeed. What might those limitation be regarding Steam (or maybe PC) support?
The main difference between C2 and C3, at this point, is C3's online functionality. C2 uses a runtime editor, while C3 uses an online editor that allows syncing/editing on multiple devices. In theory, it's supposed to be a strength, but it comes at increased memory costs and more unstable usage, along with a number of troubles when keeping local-only projects. C3 also isn't compatible with previous community plugins as far as I'm aware (they need to be ported individually). Unless you specifically intend to use C3's online capabilities, C2 is a safer bet for now, both for its stability on local use, and its wide number of available plugins.
C3 is supposed to get a runtime editor down the line (supposedly "soon") that should bring it closer to how C2 operates as far as local projects are concerned, but that's mostly theory for now, and the philosophy of C3 as far as its been detailed so far is to move towards an overall online experience.
Construct is an HTML engine, which has its ups and downs. Main ups being it can run fast preview/exports on browsers and its performance is actually somewhat impressive. Main downs is that HTML is a big no-no for consoles - any console export will require workarounds, or switching engines entirely. There are exporters out there, but they're usually developed in house for internal use only. It was designed primarily for rapid PC prototyping, small PC games and mobile games. That doesn't mean it can't do more than that, but those are its core focus.
That leads to it having a reputation of only having "smaller" games, but the gif I've posted above is from a C2 game, as are these:
Klang,
Yonder,
Honey Rose ,
The Next Penelope (actually coming soon on Switch thanks to one of these precious few exporters). C2 may not be an optimal choice for "big" projects, mainly because of its lack of console portability, but performance wise it more than holds its own.
It has no inherent limitation preventing it from working with Steam - in most cases, you'll need to use a Node Webkit export (essentially a browser emulator, as far as I understand), and use a plugin to integrate Steamworks. There are two that I'm aware of:
Greenworks (by Scirra, I believe) and
Steam4C2 (by Mad Spy, the programmer I'm working with on Pachacuti).
Of course, the fastest way to come to terms with it will come through experience - you should try it and see for yourself if it suits your needs :-)
