Sometimes interpolating actors don't detect collisions.

The actor for the laser is big enough so as to not show up even on full screen. When they spawn, they are constrained in relation to a game.attribute on the main actor, they use an interpolate behavio

What you could do is use an interpolate to give a slide effect, BUT, at the part that says "For X seconds", for X put a game.attribute or self.attribute.

@benjaminmage This seems like you have over complicated your code. First, you need to create an attribute called SpawnLocation (You can name it whatever you want) as well as 3 actors.

If the ball collides with the paddle, the it changes the attribute as follows:

I spawn the actor. The first rule of the actor is to assign a random number between 1 and 3 to a self.myType integer attribute.

Change attribute / linear velocity should work fine.

@Socks I am using the change attribute for linear velocity, should I be using Move instead?

Wow, sorry , I set that attribute as boolean (Image)

I have an actor that first changes a self attribute to it's y position. Then, I have an interpolate to that attribute when the actor has moved away. This glitches out the viewer, and it freezes. Am I

Make a 'real' attribute in the actor, let's call it 'OffSet'.

Spawn the actors and assign a "type" to them at random afterwards. That way you're just spawning a simple grid and doing a change attribute in each actor.

for the moving platform I created three attribute on the moving platform. myMin, myMax and mySpeed like i saw in youtube tutorial. Then I created a rule

1)Make an attribute (type = text) called mySpace.

The damage part would be changing the value of an integer actor attribute (set to some value to start, e.g. 10):

constrain attribute->self.color.red -> self.color.red-0.01

Change attribute self.color.blue to 1

Constrain Rotation to vectorToAngle (game.Mouse.Position.X - self.Position.X , game.Mouse.Position.Y - self.Position.Y)

Thanks for trying to help me figure this out. The code is configured in the same context as you've given, the only differences is that I'm not using a 'self' attribute but rather a global one since th

As for detecting platforms, we can't do that. But what I do is put an attribute in you game called game.platform and I run rules that fire platform related behaviours like tweet sheet and more games l