IMO if you are focused on HTML5 games and you are already familiar with Construct 2 then you may stick to C2. C2 has very nice performance for HTML5 games, it's very user friendly and you can do whatever you want in a fast and simple way.

However if you are focused on Android games, then for now C2 is not that good as Game Maker especially regarding performance. C2 is meant to be used with Intel XDK with Crosswalk. Crosswalk works great with devices like SGS6 (devices which are at the moment the strongest ones available), but older devices have problems running dynamic Crosswalk apps smoothly.

Another thing worth to mention is that while in C2 you do not really need (or even can in comfortable way) to code anything, Game Maker is close with coding. You can code your actions inside the studio. If you are a programmer and you are familiar with some common programming/scripting language like PHP, JavaScript, C etc. then you will find it extremely useful - if not you will have to learn it anyway to be a happy GM user.

So to wrap up IMO:

Construct 2 - a must have for making HTML5 games and very simple mobile games (I believe this limitation should be gone within not more than a year)

GameMaker - a must have if you are focused on mobile games and/or if you are a programmer. But to be honest, it's a sin to not buy it while you have a chance to order it for $12 instead of $450 anyway.

Move some sound effect file from Sound directory to Music directory, and music file from Music to Sound directory. This should tell you if it's a problem with the music file or way engine treats it on your mobile.

The bigger the better I guess. You can always resize the asset to make it smaller without quality loss, but not otherwise.

(sorry could not resist! ;P)

Boolean is not an action so it can't actually "work", it's a type of variable. There are various types of variables (of data types) where the most common are - let's say - string, integer and boolean. Let me explain you all of them, that should make you understang boolean better.

String is a text type variable so you can store some text f.ex:

• "Elvis is the only one real super hyper mega king of whole music history!" - this is some long text
• "a" - this is a single character, but still a string, still a text
• "1" - this is still a text, you see a digit but within the quotes it is treated as a string/text
• "" - this is an empty string, like a text without a text but still engine treats it like a text if this is a string variable

Integers are simply a digits like 0,1,2,3,4...

Now as you can see strings and integers can have many different values. Boolean is a type of variable which can have only two different values: true or false. It is not a text "true" or "false", true or false it's just a logic assumption for the condition result. You can also think of it like the boolean may have only a value of 1 or 0. Switch is on or off.

Now you probably wondering: "Why do we need a boolean if we can use Integer and just set it to 1 or 0, or even empty or not empty string?". Well that is a good question, and yes you can do it with integers and strings as well, but here are the reasons why you should use boolean if possible:

Reason 1. To save some memory and what goes after increase performance. Depends on the programming languages, booleans may be a really tiny variables, but in other langs they are treated exactly the same like integers but just "wrapped" with the boolean functionality (something like "enum" in SQL).

Reason 2. Safety. If you have a variable which should always be a digit, then you use integer, if a text then string if it's a switch/flag then boolean. If you use the proper variable type then you protect yourself from unwanted code results (calculation etc.).

Reason 3. Because semantic code is the good code. This means that every functionality you build should be built using tools/elements which are dedicated for the particular functionality.

If you are not an experienced develper then I understan those informations might be confusing or even sensless. Well but doing so is simply a good practice so I encourage you to stick to those rules, you will understand all the good things it brings once you'll get more and more andvanced developer. Especially once you start working in a team.

I hope you get the meaning of boolean now, and as you see it doesn't "work", boolean is simply a flag which can hold one o two possible values officially accepted as true or false.

If you write a game where you can turn on or off the lamp in the dark room, then you can use boolean to remember lamp's current state - isTheLampOn (true or false) etc.

It is also worth to mention that if you think of it more closely then boolean is usually the answer for some question (is the lamp on? yes/no). Therefore a good practice is also naming boolean variables starting with "is", so the variable name itself tells you what question it's value answers to... like: isTheLampOn, isOnAir, isShooting, isMoving, isVisible etc.

ALRIGHT! I was just about to write a short explanation and here's the "short" one haha.... but that is beautiful in development that even such a small thing as boolean is worth a discussion cause of its usability! .

Why not me?

It might look like I have no other life than to serve you, but actually I do..

I might have been a bit more eager to help you if you said "thank you" once in a while and asked "could you please" instead of demanding someone to do things for you..

I feel my free time is better spend doing things for me or helping people who actually show appreciation..

Good luck on your project!

+1

Calfuso as I see you have a serious problem with the very basic thing. Even if we manage to understand what exactly do you need and give you the exact solution, it won't be a real help in your case.

You need to go several steps back. Try to read/learn about what variables, strings, integers, comparisons are. Not only from Scirra forum but in general. Maybe try to read some tutorial of basics of programming. Pick any common language like PHP or C. Just to understand the basics. It would make many things clear for you.

This topic has already beed discussed several times and as far as I know nothing has changed yet. You will find some workaround here https://www.scirra.com/forum/viewtopic.php?f=147&t=153661

Have you tried using the Cocoon.IO? Canvas+ performance is quite something.

Do you have any Android mobile app on Google Play made with C2 and wrapped with Cocoon.IO?

Your most important layer of database protection is not C2 but PHP. I'm not really sure what DUTOIT meant by "Don't pass login details via post. ", the big majority of websites authenticate using POST. It is obvious that plain POST data with no protection is dangerous for your server, but that's why there are number of ways to protect yourself. You can encode data, params, actions etc. You can add the hashKey/ApiKey/token (whatever you call it), You can (and should) use database library whith SQL Injection protection built in... etc.

There are really uncountable ways you can protect yourself from attacks, I suggest to google something regarding SQL Injection and XSS. This will help you understand how attacks work and you will surely find number of common ways to protect yourself.

First of all you don't need parenthesis. You use them to group calculations like in math.

Second thing. Every event is being checked every frame (so approx. 60 times a second). So if you want to trigger this random calculation only once then you have to add an extra check which will determine if this should be ran or not (suggesting a boolean-like variable or a trigger action like "On tap..."). But I have a feeling that the first thing you should read is How Events Work. Then you may want to read about the "hidden" useful functions called System expressions. This should make many things clear for you.