It is much better now, onur but I've got an idea I think you can improve your game (altough it would affect the gameplay):

I assume the numbers are random, right?

In fact there is a possibility (a nearly impossible one) that for the next 10 minutes it won't score a 7 (the number I need) and it is a little bit frustrating to wait until there and then, 10 more minutes so I can hit it again.

Instead, why dont you make a global variable "speed" and start counting, (initial random number) let's say 7, then 6, 5, 4, 3, 2, 1 real fast, then Every loop you start slowing down until it is very easy to score.

The faster you can hit the number, the more points you score.

OR, with a plot twist you can make finjutsu 2 and instead of points, it will consume the enemy's health bar. Something like that.

Keep going, bro.

Epilepsy Alert.

If they are pixel art, just use "nearest neighbor"when resizing to keep them crispy pixels.

As thenormalgeek said: "Solid" behaviour. Right click > behaviours > solid

every 1 second - global gravity = gravity -3 (300 minimum)

if ppl tap slow (3 times), it will remain zero

If ppl tap fast, lets say 10 times, 10-3 = 7 (increase of speed).

Ppl stop tapping, -3, -3, -3, until 300 minimum

(just an idea)

What about setting a global variable gravity and increase it (you name it how much) everytime anytouch is triggered? (using physics) then set world gravity to global gravity.

I´ve tested the video object on browser and it runs ok. When I exported to CocoonJS, on the ipad (using the app) I got a blank screen and an error message: Not implemented createElement: video.

So, am I doing something wrong or the video object cannot be used on mobile devices yet?

Thanks in advance

Great games, — I like your pixelart style a lot.

Includes are good to keep things organised by catégories (ennemi AIs in one event sheet, decorative elements in another, inputs in another one, etc..)

Groups can really help subdivising things (for exemple: one group per ennemi AI), and that can be deactivated in some cases to reduce the impact on the CPU

functions are a pretty neat thing, it help not having to repeat constantly the same things over and over, or subdivising complex math calculations, which also helps if you need to modify something (having to modify it only once rather than a lot of times). local variables and constants are also pretty good to have this "change once apply everywhere in the code" effect.

My primary objective is to try to always code in a similar way, so if there is a problem, I have an idea of where the problem can be located.

The debbuger is a good tool to have an idea of what is happening, also, sometimes I read the entire event sheet, from top to bottom, to see if there is something that doesn't feels right.

Hey, thanks for the tips, bro.

In fact, as a noob, I still don´t use functions but I´ll take a look at c2´s manual and tutorials right away. Maybe I can have a cleaner code using them.

Also remember that sometimes, optimising something is not necessary, you have to see what is really taking down your game so you can optimise that in particular, this is why you should care more about organisation at first rather than optimisation, a disorganised code is too hard to optimise correctly, and also too hard to expand it, keep things organised, and everything will be easier, not only to optimise, but also to go further into developing your game.

I´ve been trying to separate in groups, so when something is not active, I disable the group and save processing.

Do you know any "rules", or tips, hints to better organize the code?

Scofano

What resolution and fullscreen option did you use in your mobile game?

I´ve only tested on my ipad, trough cocoonJS. 1024x768px

[quote:15dwjiku]

All of the event sheet (except triggers) conditions are checked every tick, you should not worry about every tick, just make sure you don't do useless actions or conditions (if you want something to happen, does it have to happen every tick, or only on particular cases? When you are checking for a condition, is it really nessecary, or can you filter down even more if that is intensive), there is no magic, no wizardry, just see what you event sheet does, and when it does it, if there are redundancy or things that should not be done in some particular cases, because it serves no purpose to do it, then don t let the system do it.

Thanks, I´ll try to lower to zero unnecessary calls.