While I'm glad you like construct, bashing other programs doesn't really help matters, and can be off-putting for people interested in the program and community. You're certainly entitled to your opinions, but insults aren't really necessary and don't help the tone of the conversation. Protecting your intellectual property doesn't mean all you care about is money, either. Let's please remain respectful of other users, developers and software even if you don't like the other programs! We want this to remain a friendly place!

You can, but it's quite a task. Making an RPG is an utterly ridiculous amount of work. Not impossible at all, but difficult.

I'm making one myself, so my advice is: don't make your complex dream RPG first. Especially if this is your first attempt at one! Make a small, simplified prototype RPG for fun and to learn how to do it right. Otherwise by simply leaping in you'll probably make huge design errors that take longer to work with and would take even longer to fix.

You should definitely learn how to use construct well before trying to make a complex RPG. Especially learn how to properly use families!

PDF manual:

Don't do that! I reflexively almost started to ban you! XD

+ On esc pressed

+ + if variable 'menu' = 0

• - open menu code
• - set variable 'menu' to 1

+ + else

• - close menu code
• - set variable 'menu' to 0

Making an object global means it isn't deleted upon switching layouts at runtime and is listed in every layout's object list at edit time. That's it.

I realize it's frustrating to discover a bug such as the ones in the built in saving system, so let's all take a deep breath and calm down before anyone gets any angrier.

First, construct is in beta, which means all the bugs haven't been ironed out. No feature in the entire program should be considered to be 'advertised' as entirely bug free because of this.

Second, learning how to stay calm when encountering a bug such as this is an important and valuable lesson. Bugs exist even in professional development tools, so learning how to work around them when possible is also an important thing to learn how to do. In this case, using a custom saving system like newt suggested is the solution.

The devs are working to improve construct. However, construct is quite a complex application developed by volunteers in their spare time. Patience.

Irbis, it may be due to the langauage barrier, but comments like this:

seriously instead of that biased Construct trailer, someone should make a list of messed up features in Construct.

...tend to be inflammatory. There isn't anything wrong with or biased about the trailer, it shows what can be done with construct in its current form, bugs and all. That said, a 'beta users guide' might not be a bad idea.

On my machine with my example with 500 sprites, deactivating the colourise shader only gets 1 extra fps per sec at unlimited (69 to 70). Reducing the simulation steps on the physics from 10 to 1 boosts it quite a bit more to about 135.

AFAIK there isn't any other solution to having piled objects like what you're looking for that will be any faster.

I know I mentioned already in chat, but for the sake of the topic making sense: it can already be done using physics and quaziblobs, which if I can remember correctly works something like this:

http://www.amirai.net/forums/liquidexample.zip