https://www.scirra.com/manual/48/image- ... ons-editor

Styling Button objects

Button controls can be customised in a huge number of ways via CSS (Cascading Style Sheets). Rather than adding actions to set all of the possible properties, the Button object exposes a Set CSS style action. Knowing CSS will of course be an advantage here, but it is simple to use for simple properties. A few examples are listed below.

Make the text red: Set "color" to "red"

Make the background yellow: Set "background-color" to "yellow"

Make the border a thick light grey: Set "border" to "3px solid #AAAAAA"

Make the font bigger: Set "font-size" to "2em"

Make a dashed red border: Set "border" to "2px dashed red"

Do yourself a favor and read the manual , do some tutorials ,search the forums and then experiment as much as you can , the more you teach yourself the more you retain . Asking for help should be a last resort and a hard habit to break as it makes you dependent instead of self reliant .

Try this out :

In event 97 change the condition from car>health to system>health . In your game you are subtracting from your global variable health so your car variable health is never changing. It is not necessary to have both .

The reason the score and health do not change is because of the order your events are setup . You destroy the balloons in early events and then much later check for another collision event to change your variables , well these events never trigger because of the earlier events that destroy the balloons. Put your actions that change the health and score variables in the earlier events that check for collision and all will work fine . You should also use families instead of all the repetition your doing with collision checking . You have over 100 events that could easily be managed with 20 and serve the same purpose . Perhaps reading the manual and doing some tutorials might provide some insight .

Lets say you are controlling the paddle with the mouse and the furthest the paddle can go to the left without hitting the wall is 40 and the furthest right is 500,,,,,,,,

make a condition and action as follows :

System>everytick..........Paddle >set x to clamp(mousex,40,500)

Just use clamp()

clamp(x, lower, upper)

Return lower if x is less than lower, upper if x is greater than upper, else return x.

It looks like your off to a good start and welcome to the forum

Underwater assets would also be nice

Try comparing their y positions

Might want to try one of the other physics engines and check performance.

No worries