How much events do you have?

How much events do you have on average per game? Is there a maximum amount of events I should have if I want my Android games to work fast?

Well I've got about 2500+ events so far. I'm testing my game with the Cocoon.IO frequently with my HTC One M7. Performance is good, but I'm making quite heavy optimizations with my images by making sure that they are as small as I can make them, without really making a visible difference and by making sure that there are not many objects on the screen.

Just keep developing your game, test it, and keep developing!

We got 9700 events, using plenty of functions and families.

I'm sitting at about 4500 events so far, but I'm not targeting mobile at all. Some of them get a little heavy, of course, but good optimization can help with that.

You can make a simple game with 100 events, but you can make a complex game with tens of thousands of events. It depends on the project.

it all depends.

if your game is organized nicely you can reduce number of events for your whole game.

for example - if you create a family that has 10 enemies - you need only one trigger where you say - if myfamily.health <0 do ... something (explode, count score etc..)

other way could be : if enemy1.health <0 do... something ( explode, count etc..)

if enemy2.health <0 do... something (explode, count etc...)

.... and so on for each enemy. this means - > 10 events for each enemy instead of 1 where you just drop your sprites to family.

and such "optimizations" could be done to reduce number of events. you can achieve that wih families and functions easily. and creating new levels, spawning and all other things are suddenly super easy

I never go above 500. But I make optimizations where I can and very stupid prototypes which dont encompass things like :

UI

Saving and Loading manager

Local storage management (not doing alot of this yet)

Its not really about how many events you have, it's how many events are actively doing something that will slow you down (the more work they do the bigger the impact). Just make sure that you* aren't running events when you don't need to.

You can do this by enabling/disabling groups or using sub-events from a condition (when variable is set to 1 activate this logic etc).

agreed partially. it's actually how much javascript can your CPU run in one second. if you check c2runtime (nonminimized) and data.js, you can notice how things work. if you have seen there how it works, then you can actually predict how much code can you approximatelly run in a second. sadly there is no measures how much linear code can be done in 1 second, but it also depends on the structures used.

anyway if you disable /enable events things should go faster, and using triggers / functions / families = gg