In the other thread, when I suggested using 'wait 2 seconds', the event said 'on right mouse button clicked'. That triggers once every time you click the right mouse button.

Here you've changed it to 'Sprite is on screen' - that runs 60 times a second so long as the sprite is on screen! So 60 times a second (about 120 times) you say "wait 2 seconds then spawn four balls...".

So even after the sprite is destroyed there are a total of 480 balls queued up to spawn over the next 2 seconds.

However, it did expose a genuine bug! I'll have a look at fixing that soon. In the mean time - either use the old way, or stick to a trigger like the original project.

I'm moving this thread to the 'bugs' forum so I don't forget about the issue :)

Yeah it was originally 'On Right mouse button click' but I created a new system for 0.2 of "Cannonball" and it uses a different "Cooler" system which I find awesome. I guess I could use a value then depletes every 1 sec, and at 0 it does it. like the original, until you fix it. Thank-you guys very much!

Tutorial: wait action

This is not a bug, the wait action is working as intended.

The way C2 reads your code is :

Every rendering frame:

.. Is red ball on screen ?

.... If it is, wait 2 seconds, create 4 balls and destroy the red ball.

And so, for the 2 seconds of "delay" you're expecting, each frame, there will be 4 more balls created, etc...

You made some kind of loop that is memorizing a sequence of actions to do, and will do it once the timer is done.

The fact is that since the wait action is the first, you'll have some kind of infinite loop going on.

I suppose you're trying to have some delay between each ball you create ?

Prefer using variables to make a kind of timer.

You can check this topic and the capx I give as example it might be closer to what you are willing to do.

Also I noticed you asked a few beginner questions/notices/suggestion, did you read the beginner's guide tutorial or Where to start ?

You have the wrong impression, my apologies if It's my fault.. as ashley pointed out: scirra.com/forum/cannonball-fanatastic-physics_topic44933.html

I'm making a timer that only suppose to happen when there's an explosive ball on screen, and it happens after 2 seconds, I used a manual timer that I created but Ashley suggested to me the Wait action so I threw my hand a try at it. And created this problem, I don't want it to wait 2 seconds between each one being created. if I wanted that I wouldn't be dumb enough to right this event (in the image) which is nothing alike that =P Silly :D

I just want this event to happen 2 seconds after an "explosive ball" spawns on screen. And it seems to just spam the event and not destroy the red ball (well I don't know if it destroys it because it crashes)

Hello people! I have the following condition:

<img src="http://screensnapr.com/e/H55eqs.png" border="0" />

It seems that rather than just creating the four balls and then destroying the red ball it spam-created loads of continuous blue balls. it worked fine before I used the 'Wait' action. Is there something I'm misunderstanding here or would this happen to be a bug?

I've wondered similar things, I'm sure the developers are working hard to add a Paralax option. I may suggest this actually in the forums.

Hello, I was wondering if you could set a physic behavior object/sprite to be immovable by events, if not can it be added? Thanks very much for your time!

make a Castle War game. It will be awesome!

Good idea, I hope coding the AI to fire cannonballs is easy (I bet it is, and even if it wasn't I'm sure it will be soon)

Ashley I can't find the 'Wait' Condition, it's not in system?

/Edit: Found it! It's an action.

Wow didn't know that Ashley. Thanks very much for the awesome info! It just keeps getting better. And now with these simple physics I can finally create a game I used to play inwhich was very fun.

Construct 2 is by far the best game-maker I've used.

Wow, just beat the record:

<img src="http://screensnapr.com/e/Io0Z1R.png" border="0" />

Hello, I just created a little project test to really try out physics. Physics is just too superb. in all other game-making software I've used physics is very tough to implement into the game. Where-as this just takes a behaviour. I'm amazed!

To try it out I made a little project where you have to knock out the structure using only your cannonballs. (not limited yet)

It will be improved but for now this is it!

-Controls:

• Left Click - Fire Cannonball
• Right Click - Fire Bomb Cannonball (explodes 4 Cannonball's after 3 seconds)

I am setting a record at the moment which I achieved, I knocked over the structure using only 2 cannonballs! See what you can do and if you can beat it!

<font color="red">Source code (.capx)</font>: Mediafire, <font color="blue">Mirror</font>: Uppit

<font color="red">Export</font>: Mediafire, <font color="blue">Mirror</font>: Uppit