Yeah I pretty much exactly that including the constrain stuff, I have my ball gravity set to -800 and flipper movement to 400, I just don't seem to be able to apply enough force, I need to play around

I do realize that I have to stop the attribute from changing or save the value or something, but I don't know how to do that.

* To keep the flipper in place, make two real self attributes - X and Y, and set them to the starting X and Y position of the flipper. Then constrain the flippers location to these two attributes.

You seem to be wanting 5 white actors. However, you have the white count attribute incrementing by 1 before the actors are spawned. When combined with your < 5 rule, you're never going to get t

Yep, that might be it. Constraining to mouse positions does not work well with collisions.

How do I make it so that my bubble actor collides with the red actor, but does not go under the actor:

Change Attribute game.Fire to 1

For example, "Fire actor " changes image when player touches it in spite of there is attribute "FireGet".

There are Tetris templates available - do a google search and they should show up. Now that we have custom collisions it will be much easier!

Ah I already used a trusty method got my flippers working great. Got my first trial layout. I may publish this game once the collisions are worked out. PUCK IT PINBALL.(Image)

Change Attribute game.startX (real) to self.Position.X

I think it will solve when I make attribute "KeyGet " or "FireGet" and combine rules.

@Rainbros by the time we post the finalists for voting, we expect to have custom collisions working on the Arcade.

(Quote)

So let me get this straight, since custom collisions won't work in the arcade, the community is supposed to vote for a winner without actually playing the working games...?

What do you mean for example with self.AngleToTarget. There's no such attribute that I am aware of. What I discovered is that the expression "vectorToAngle" does exist.

Constrain its"s Y position to where you want it to stay.

Sounds great! Do custom collisions work in Arcade now?

(Quote)

I think @crestwoodgames means that he can't touch and register a touch on his custom collisions. That's something that isn't supported yet and is what my demo was going to do: show a workaround.