Why would there be a problem with more bricks being destroyed when each brick that gets destroyed adds 1 to the score?

Question one is not clear..

You want the max health to be the maximum width of the healthbar?

question 2 would be creating a healthbar for each enemy, setting an instance variable to the uid of that enemy and having the healthbar only react to the health of the referenced enemy..

You could do it with the timer behaviour:

• move = 1
• trigger once

> start timer "moving" for 1 second

on timer "moving"

add 1 to SecondsMoving

-- move = 1

start timer "moving"for 1 second

on player dead

stop timer

If you used custom movement to recreate your movement you could use push out solid..

- bullet on created - bullet move to bottom = Working thanks!

np

- Bullet on collision with player - Bullet spawn animation bloodspatter = How do I defy as specific animation as all I can see is how to do it using frames?

add frames to create an animation.

Add another animation through the animation dialog.

repeat.

- If you set the bullet angle to 180 it will go left, angle 0 it will go right = Tried this did'nt work it only shoots out at one angle at a time, how would I do it so it shoots from both 0 and 180 degrees at the same time?

one bullet can only go one direction, solution?

Create two bullets, set one to go one direction and the other to go another direction.

• bullet on created - bullet move to bottom

• Bullet on collision with player - Bullet spawn animation bloodspatter

• If you set the bullet angle to 180 it will go left, angle 0 it will go right..

You are not picking an enemy in your event, therefor all enemy instances will respond to the action.

Simple solution would be to add a system for each enemy condition..

Don't think LaTeX is supported. One might be able to write a plugin using MathJax (I don't know) that enables it, but that's probably complicated.

Instead of MathJax using KaTex would probably be easier to create a plugin for:

http://khan.github.io/KaTeX/

The implementation of your thumbsticks leaves a lot to be desired..

I would opt for using TouchID and dropping the drag and drop behaviour..

Here's an example with one thumbstick, but adding a second should be easy..

https://dl.dropboxusercontent.com/u/485 ... ullet.capx

I'm not sure if I understand, but wouldn't this be the solution?

brick on destroyed - system add 1 to score

You could do something like this:

system every random (10,15) seconds - call function "create" with parameters 0 = choose (1,2,3)

on function "create"

-- if parameter = 1

create object 1

-- if param = 2

create object 2

-- if param = 3

create object 3

Does Arrays work in this situation?

What would you want the array to do?

Please explain what is wrong with the solution korbaach gave, so it is more clear to us what you want..

Sharing your capx and/or your events might even make it clearer..