If I need to change the name of a layer and I have 40 level layouts, I need to rename 40 layers. That's not ideal.

And it's not as simple as just clicking on the layout in the Project manager, I have to open each layout to do it.

It seems like it would be more consistent to at least also show the correct layers for the layout selected in the project manager, since clicking there already changes what properties you're seeing.

Quickly setting an anchor position to the common positions of center top/bottom, middle left/right, or center middle would be extremely helpful. I've found these settings to be pretty common in other engines, I was kind of surprised they weren't options here.

I just released my first game for sale, a retro inspired 2D platformer built with Construct2.

noblevalerian.com/legacyquest

I've also put together a free demo, with 4 SMB inspired levels. It's short, but gives you a good idea of how the full game plays. The game and demo are available on both itch.io and Game Jolt, and can both be downloaded directly from my website. Thanks for viewing!

My stance on native engines is detailed here: https://www.scirra.com/blog/ashley/28/the-case-against-native-engines

I think "make native engines" is everyone's knee-jerk reaction when something doesn't work. For example, sure, we could make changes to make publishing easier. But that can be done anyway. You don't need native code to solve that. I also have direct experience of working with a native engine for Construct Classic. That had enough problems to make me move away from it. It is certainly not perfect. Do not imagine it will magically fix everything!

That article was a strong influence on deciding on Construct as my preferred tool over other software.

Have you ever tried the Editor? It's far from as easy to use as Construct's in my opinion...

I think there's always a tendency to look for the "perfect engine". It happens on every user forum of all the mentioned software packages that i've ever been to. There are always things that could be better or optimized etc. I think there are a lot of people who never start actually making a game, because they keep looking at different game engines every other week. I know i had that problem for much too long. In the end what counts is, which tool makes you actually realize your project the quickest and most convenient to you, which is very subjective. For me PERSONALLY i really always came back to C2 because i didn't see any other program, where i could get something done so easily and still remain a great deal of flexibility. So i'll stick around for sure and i'm looking forward to see what C3 will offer

I agree. I explored a lot of 2D engines, nearly a dozen, and Construct 2 became my preferred engine. They all had pro's and con's, but Construct 2 was the most appealing to how I think about problems, design, and allowed to me to see all the info I want in a user friendly way, the relationships between conditions and actions, level and asset organization, etc, it was just the best fit for me. I hadn't been terribly concerned with "native code" to begin with, but wherever performance *might* suffer, it seems to also be far more consistent and reliable than other software.

GM:S gave me a game that worked moderately well on PC (minor collision issues not dissimilar to ones I've had in Construct 2), but was completely broken when the same project went to HTML5. I don't even know how to identify the cause or come up with a solution for a problem like that. And at the end of the day, every minute of time spent exploring how to get around those problem in one engine, is the same amount of time I could spend resolving issues in my preferred engine. At some point, you need to move from a Jack of All Engines, pick a lane, and commit to development. It was a hard lesson to learn. And sadly, one I still can't take full advantage of, since I have to teach in one program but prefer to create in another.

Clickteam and YoYo Games are showing images of Fusion 3 and Gamemaker Studio 2

When images of Construct 3?

And they are finally *starting* to look as appealing as Construct 2. Personally, I'm comfortable being patient. Although, I'd be disappointed if Construct 3 wasn't again an "easy" choice to make as my preferred tool, as Construct 2 was over the nearly dozen direct competitors I'm familiar with.

It seems like GameMaker is coming with a node -based system. I personally prefer Constructs eventing system.

I quite like the simplicity and readability of the event sheets. The nodes look cool, and might be fun to drag around, but as a very visual person, what makes me effective is that the information I want to see is easy to find. Along with the relationships between conditions and actions, which I think is very apparent in the event sheets.