Change attribute self.Touched to true

Start by adding 4 'real' attributes in the actor: touchStartX, touchStartY, touchEndX & touchEndY.

changed the rotation of one of them to 180°. The collisions seem to be working fine when set up in this manner.

While there isn't a way to change game.Time or scene.Time or self.Time, you can use a speed attribute that you then alter when needed. For example, a Move behavior with the speed set to game.speed.

We create 2x new attributes

The issue you're facing is that GameSalad resets a scene each time you change to it. While game attributes don't reset when that happens, everything else does: actor positions, actor's self attribute

The coins can be collected which destroys them individually and adds to a (game level attribute) game.CoinCount which keeps track of our coin score.

That shouldn't be so hard. You need to start with tutorials that will teach you the basics of how the engine works. There are actors and behaviors and attributes. The behaviors are what tell the actor

Constrain changes the value of an attribute constantly. That's why I suggested only using one constrain behavior at a time per attribute. If you use a Change Attribute, it's going to change the valu

Change attribute self.SpawnSpeed to game.time (some math)

I needed to set the change attribute of the DualObj:

Btw on collisions you can make it custom collisions using something like physics editor. Then collisions aren't constrained to just rectangles. I made a banana collision for a game.

The collisions shouldn’t be very difficult. The only issue I had was getting the player actor to display the death animation as soon as it collided with the scrolling obstacles. I’m sure that was born

Yes thank you thats what i want... (the actor can move both directions). i did try the attribute model but didnt work. But it should. So i wil look back over and try try try. Thank you for the suggest

You're welcome! I'm probably not the best person to ask about collisions as I tend to make apps/games that are heavy on tables, math, etc. and light on physics. But post it and someone will likely h

I will also start setting up the collisions tomorrow. There were a few questions that Inhad pertaining to the character and how it responds with collisions but I will try and sort them out before I as

I believe what's causing it is the multiple Constrain Attribute behaviors you have going at the same time. I didn't catch this until I saw your rules but... what you want to do (if you don't use my s

constrain self.ObjSpeed to 350

Constrain: self.ObjSpeed to 300

@mikejamesfisher Do you always want the flying actor to be moving left? If so you could take out its 'if button pressed move left' and just put in a change attribute behavior 'linear.velocity.x to -1