Should I focus on learning C2 or C3?

I wanted to start learning Construct but i'm debating if I should start learning the established version or the upcoming one?

It's pretty much the same thing only that C3 is a much nicer looking experience +- some awesome UI stuff.

If you intend to finish a major project that relies on stability focus on C2, if you want to have a nice time while learning and experimenting for a few months until they fix stability then do C3.

Either way you learn the programming aspect.

It's pretty much the same thing only that C3 is a much nicer looking experience +- some awesome UI stuff.

If you intend to finish a major project that relies on stability focus on C2, if you want to have a nice time while learning and experimenting for a few months until they fix stability then do C3.

Either way you learn the programming aspect.

Thanks for the response, I already got C2 with a template to start with; I was concern with the upcoming upgrade and how that would effect the game, I plan on making a series out of it.

If you haven't already invested project assets into a large project, there's little reason to go with C2.

The only reason you'd go with C2 is because it uses a critical plugin that hasn't been ported to C3 yet, and because changing versions/software in the middle of a project is foolish and incredibly risky.

As already said, they're pretty similar - so much so that the majority of learning material for C2 (of which there is a lot!) applies equally to C3.

In fact, C3 has some nice new features which streamline workflow, and because it's browser based you have ultimate portability and the ability to work anywhere with it - you just log in - this is something that I really like, personally.

There are a few things I wish were in C3 already (saving a project in a file structure for instance), but they will get there eventually and they're not a deal breaker for me. I don't think they are for most people, if they're really honest.

The majority of people who complain about C3 vs. C2 are really just trying to avoid admitting that they don't want to pay a subscription rather than a one-time fee. Which is a shame for them, because that's the way the whole software world is going. But people are entitled to their opinion, regardless of what I think of it.

Thanks for the response. In that case I will stick with C2 and start the project, due to C3 being unstable at the moment; hopefully I don't run into major problems later on when I upgrade. I agree with the yearly subscription it helps the developers and exhilarate their potential on putting out better upgrades, the old model does not work in their favor. I love the software and hopefully it will pay for itself soon after I release my games.

Hi aMortalArtist,

Firstly, welcome to the Construct community. It's a wonderful tool and to be honest 95% of the knowledge you will learn on older tutorials for C2 has crossover for C3 as well. So don't be too worried. Read and watch as many videos and tutorials as you can. Construct has an amazing workflow and the coding is very intuitive.

I was in a similar situation to you not so long ago. I bought Construct 2, than within a few months later Construct 3 came out and I jumped on it within the first week of it being released. I did this mostly because I enjoy the whole visual scripting and want construct and Scirra to succeed and am happy to financially support Construct 3 even though currently I am using construct 2 more often.

For me, I use both C2, and C3 that is because I was targeting an older version of Android. If you want to release your game for older versions such at 4.0, and 4.2 etc then I found construct 2’s export easier for me. However, these versions of Android make up a tiny fraction of the market. So it was a more specific need of mine. Due to my only Android phone being ancient and running on 4.2. Construct 3 exports to Android 5.0 and above.

If you already know you will export to 5.0+ this won't be an issue at all for you, as older versions add a lot of overhead, memory footprint and download size.

Another advantage of C3 is the build system. This is coming along nicely. I hope eventually it will even have key signing your apks and will cut my entire need for Adobe’s Phonegap build service.

Also if you have already started your project in C2, it is fairly easy to bring it into C3 later if you find a specific reason or need one of the new behaviours such as the Set color. Assuming any 3rd party plugins you used in your C2 project, also work in C3.

It is much much harder to do it the other way around. I recreated my entire game from C3, down into C2 basically having both projects open. Creating the same sprites, names and layers, and it allowed some copy/pasting of the event sheet over, but it was a slow process and I had to manually check I made no mistakes.

Anyway, good luck with your journey into Construct. There is a lot of amazing tutorials on here, Youtube etc. One of the best parts of Construct is its community. I have been lurking for 100s of days reading as many of them as I could.