No don't constrain the main actor to the invisible actors. The invisible actors only serve the purpose of telling the main actor which touch is being used to control it. So if it overlaps with actor1

Hi guys

area. You need to have the button change an attribute that triggers invisable actors in your scrolling layer for your visable actors to spawn on. Tshirt had it right you need to listen and think.

add attribute … real type … name: origY

If you study the official GS control template found in the creator's start screen you will see how they handle multi-touch issues like the one you describe. The idea is to create a small invisible act

I all. My problem is i'm using diferent coins foreach scene in my game, but allways the same scene. My rule for the coins is when they collide with my actor or they aren't in their scene, they goes to

Game attribute - integer - "Counter"

-constrain att

-constrain att

Make a game attribute - index- call it "hero speed" - set it to 100 (for example)

ive tried interpolate, but then the actor goes completely straight through teh collisions it's supposed to have...

Thats because they split the "ground" from a "ceiling" .. notice that in the hero actor there is an attribute "grounded" meaning when the hero is

The collisions send the actor in different directions but the actor always stops moving.

Alrighty, thanks. I kinda figured that I would have to go through and make an attribute for each, but just wanted to make sure lol

You'll either need to do a separate attribute for each..

I use an attribute with the random expression to generate a random number and, based on that number, an actor will be spawned. I have almost 100 actors yet Im surprised to see that there's an overwhel

my jump attribute is integer type

In your actors make a self attribute - boolean - call it "I've been touched"

Make a game attribute - boolean - call it "climb"

(you could instead do a changeAttribute: self.Name or even add a new attribute