Someitmes you constrain an invisible actor to moving red actor. One that is farther over that could collide with purple wall......

Make an attribute for a switch, an integer will do. For an example, we'll call it game.active.

This happened to me on my Ludum Dare submission, and I got very frustrated. My first level worked perfectly and on the rest of the levels the collisions messed up. However, on the GameSalad preview, e

The constrain rule is just so that it faces the way it goes, I found it in this video: (Image)

@OscarsCoding , what is up with the constrain in the bullet actor?

(Quote)

(Quote)

(Quote)

Constrain the actor's X position to

(Quote)

@socks but will I have to constrain this particles spawning actor to my main actor?

Make a game.attribute, let's call it 'X'.

(Quote)

Do: Change attribute: Self.Motion.Linier Velocity.X(or Y) To: (Self.Motion.Linier Velocity.X-(Self.Motion.Linier Velocity.X*2))

(Quote)

Change Attribute self.AtRowFound = tableSearch(game.T_Enemies,self.CurrentNumber,"col",1,1,tableRowCount(game.T_Enemies),"exact")Rule If self.AtRowFound = 0 then

If bullet overlaps or collides with player Change attribute self.color.alpha = 0 (to hide it straight away) Timer AFTER 0.04 seconds Destroy bullet

I have set up a game where my actor is constantly moving forward using; change attribute, player, motion, liner velocity, x. All of this works great except for when i use my buttons that control the p

You are reseting the attribute somewhere in before you exit the first scene or when you enter the second scene?

//I added the change attribute below and a timer for the countdown