Who else will continue to use Construct 2 after July 2021?

Ayy,

I was curious to see how many others would still continue to use Construct 2 after support is officially ended after July 2021.

Personally, I have about 3 projects that I'm working on-and-off in C3, but I do have 1 large project that is only about 30% completed that is still in C2, and I chose not to move to C3 for this project for a few reasons (too many third-party plugins, the project is a free game that I slowly work on so I'd rather not develop it on a "subscription" software, etc.)

Anyone else still hold their love and passion towards C2?

Anyone still in the middle of a large project, or developing addons still?

Or does anyone see themselves starting new projects in C2 even in a year from now?

Does anyone have fears, or confidence, on how C2 will function in the upcoming years? (e.g. Years ago, we once had that issue where a mandatory update was needed to fix all audio in all HTML5 games. What are the chances of something like this happening again I wonder.)

I feel its a strong bit of software still - I found that it fits my workflow in some places, e.g. I do not use multiple event sheets and only use groups, which works fine in C2, but in C3, the editor can lag terribly when you have 3000+ events, so I need to start adapting to using multiple event sheets (which is probably better practice anyway, but hard to unlearn what I've been doing since using clickteam products 10+ years ago!)

Would be curious to see what others think!

I haven't used C2 in a couple years other than to transfer projects.

I had one decent sized project that used the Spritefont+ plugin and it was a little bit of a pain to get into C3, but I did it.

I honestly hate that C3 is in a browser. I use my browser for everything and I never liked it for gamedev. But I just accept it now. But I do use #includes a bunch so that helps a little for editor performance.

I can't imagine any C2 plug-in being that great that you couldn't find a way to do something similar in C3.

I could never go back to C2 just because of all the updates to C3, you can't go back. To not be able to use Functions the way C3 does alone is a deal-breaker for me.

I will still use C2 for my project and C3 for customers' project if it's a requirement.

I only use official plugins in C2, so at any time if something happen I can still move everything in C3 and be safe.

Eh, I'll probably keep using it until it stops working or Clickteam make their event sheets as smooth as C2's.

I will continue to use it for the foreseeable future until there is something else that can replace it’s enjoyable niche for me. The end of support isn’t a worry for me.

I don’t really have projects so I guess I’m not the typical customer. I just like tinkering with tiny projects here and there.

I'm still using C2 for the forseeable future. I still haven't decided to try out C3 yet as I don't like the pricing model. Although, some of the updates are starting to make the transition seem worth it. I've also started using Unreal engine, so that's another reason I'm unsure whether to care about Construct so much anymore.

I started my current project back when C3 still had some teething issues. Now, several years on, my project is nearly finished and C3 looks quite robust. It's been super tempting to jump ship recently, mostly for the improved runtime, but also for little features and that could have saved me development time. It's like, oh, NOW there's pseudo-3D support, lol.

But ultimately, I think I prefer working with an older engine I'm very familiar with than a newer one I'm not. If I encounter a weird bug in C2, I immediately know what caused it and how to fix it. If I encounter a weird bug in C3, I'll probably have to spend days trying to diagnose it.

Not to get sentimental, but there's also a certain grace to using old, familiar tools. It's like having a favourite pair of socks... you know you should throw them out because they're starting to get full of holes, but you're attached, you're comfortable, and you almost feel empowered by them. I wonder if that's how the Iconoclasts developers felt with using Construct Classic in 2018.

Maybe I'll jump ship next year.

SketchyLogic I never thought to ever come across to read such a poetic post about how nice is to develop with nostalgia on old software.

You made my day, even if I'm just going to sleep now :P

If I encounter a weird bug in C2, I immediately know what caused it and how to fix it. If I encounter a weird bug in C3, I'll probably have to spend days trying to diagnose it.

SketchyLogic

This is doubtful, the engine/editor is identical. I've only had a few browser issues, but none were deal breakers. And honestly I've had C2 crash on me a number of times where I lost work.. whereas if there is any crash issue with C3, it allows me to save it first.

The interface feels a little different, but it really isn't. And honestly when I go back to C2 its not a good experience. The slow mouse-scrolling speed alone is gut-wrenching. Its uglier (subjective I guess) and harder to read.

Also just knowing that they won't be supporting it is scary as hell. Like what if Windows adds something that breaks it? or an exporter breaks? I would not take that chance. It's already scary using 3rd party plugins on a supported engine!

I'll be using C2 to fiddle with multiplayer and families when my C3 subscription expires. My situation is similar to R0J0hound. I don't really have any major projects and I have a sub mostly just to support Scirra. For all the little examples I like to make the free version of C3 is more than enough (minus the previously mentioned availability of multiplayer and families).

This is doubtful, the engine/editor is identical.

Scirra have made the C2-C3 transition very smooth, but every engine has its own unique quirks and surprises. The runtime is different. The texture packing is different. The handling of dynamically created objects is different. I'm not familiar with any of this, so of course I'm going to encounter bugs that will take me a while to solve.

Also just knowing that they won't be supporting it is scary as hell. Like what if Windows adds something that breaks it? or an exporter breaks? I would not take that chance. It's already scary using 3rd party plugins on a supported engine!

That's a valid fear, but realistically Windows is pretty stable. Still, if such a thing does happen... then I'll just port the project to C3. After all, that's still an option after July.

I've actually been a little curious about my forward steps. For instance, I have the personal license for C2; if I were to finish the game I'm currently working on and have been for the last year or so, and want to sell it... don't I need an upgrade to my license?

I don't use any plugins or add-ons or any thing, so if I HAD to port over to C3, is the transition a one-to-one? I'd hardly imagine that's the case, but if it is, that'd be fine I suppose.

What do you guys think would be my best recourse? Thanks!

The C2 business license is only required after you break $5000 in sales, so depending on the success of your game, you might not need it.

But if you do need it... you would be in a difficult position. You could contact one of the Scirra team - maybe they'll let you pay for an appropriate C3 business license as a substitute, or maybe they'll waive the C2 business license just for your case. They'll probably just suggest upgrading, though.

If you have to upgrade, then for an average-sized game without third-party plugins or add-ons, the transition is usually fairly smooth. There are a couple of guides like this one that give indications of things you'll need to watch out for.

PrinceAldenSketchyLogic

I asked Tom a while ago and if you buy once the C3 business license that will cover forever C2 business license, so you'll be fine even subscribing to C3 business once.

Oh that would be fantastic. Thank you guys for the information! I really appreciate it.