It's actually the other way round: Diego is working on C3 with me, but I still do maintenance on C2 so it's not left behind.

Thanks for clearing that up. Seems like I was misinformed.

"C3 is not going to allow non coders to "make plugins".. that's the whole point of a plugin is to connect C2 (non coding) users to bodies of javascript that call on larger solutions like revenue generation that don't care if you're using C2 or Unity or Unreal.. they are just a service."

There's no reason for them not to make it so the users can create their own plugs using the sdk via eventing, other than the extra work involved.

It would be a huge selling point.

This is one of the main things I'm hoping C3 will achieve.

If someone was that interested in coding wouldn't they just move on to another engine?

Its really hard to tell that to a customer that just paid for a license, because a selling point was "no code".

There are developers who can and want to code, but they still stay with C2 because the engine fits their needs and the event system provides rapid development.

— True.

Thank you for the information. We're looking forward to the updates

I kinda sigh a little each time we get C2 updates lol.. thinking.. that was time he could have spent working on C3.. but i know others are helped by these updates so of course I know it's not really wasted effort!

If you are referring to Ashley, as far as I know he only works on C3 at the moment. Scirra hired a new member to do the updates for C2.

Can you please describe your idea a bit more? Based on the "2 players in a very simple mobile game" description: Yes, Construct 2 can do that and a lot more.

This should be in every single school. Imagine what the next generation of creative minds could come up with using it.

Working on it

At it's core, programming relates to logic. You tell the computer to do something based on conditions, if, else, loops, triggers etc.

Traditional programming involves typing out instructions manually in that specific language's syntax.

C2 bypasses this and replaces the manual typing of text with its event system. But it is still logic. It still requires you to think like a programmer. The difference is instead of learning C# or C+, you are learning "C2's event language", which is a lot easier to learn for most people (myself included, who have learnt Java before moving to C2).

If you want to make a complex game, you have to understand C2's language very well. Like anything in life, to understand it well, one must learn.

Well said.

I'm not sure it's work that way, but I use the "Else" event after a loop for doing actions that requires the loop to finish first.

However you make money with your apps, be it AdMob, Steam, Google Play, there are always records of the sales. So you can check how much money you made and act accordingly.

Welcome back.

The best thing that can happen for C3, is a native export option.

Oh, not again Please don't bring that up again. Don't turn this topic into a native exporter requesting one.

Maybe it has already been discuted, but does anyone know if Construct 3 will have a "children family" feature for the families ? C2 is greatly lacking this.

Like a family "enemy" and a subfamily "shooter" which herits all the properties from enemy but have their own properties.

Then you could do "if shooter collision with player -> shooter decreases HP" where HP is an "enemy" property which from "shooter" inherits.

I'd love to see such thing implemented.

C2/C3 needs to be the BEST 2D game engine, period.

+1

I understand what you mean. And the collision example is a good one to demonstrate it.

When a collision occurs, there are 2 objects involved in that situation. For ex. a player and an enemy. If we focus our events on the player and create the "Player on collision with enemy" then we could reference the other object with this expression (in this example, the enemy). Yes, it can be done with families, but not in the free edition. Also, you don't have to create families for different groups of objects if you can use the "other" expression. It may help developers who think differently to those who use families efficiently. Also, the collision is just one example, I'm sure it would be useful in differens situations as well.

What if there are 5 other conditions in the event which all refer to different object types? What if there are hundreds of "other" instances to choose from? How do you know which will be referred to by "other"? This seems far too ambiguous to be useful at all.

These are indeed problems with this idea. Maybe it should be a Sprite only expression. I don't think it would be a problem if there are hundreds of instances. Staying with the example: the collision event would run for every collision, so picking the other instance there can work.