Its correct to constrain the swingbox to the character rather than the animation.

Okay I constrained it to the good guy so where ever he moves it follows. I can't just constrain it to the sword because it's just one animation. So will that work?

I'm thinking have an invisible actor Constrained to each combatant with size equal to the sword swing arc. Then, each time you process an attack, have it check if the actual actor overlaps the sword

@grishlock -- you are correct. Constrains override collisions. In fact constrain overrides just about all physics behaviors in GameSalad. Its pretty much the same with interpolate too.

That was it - can't have any constrain attributes on either actor in a collision.

I've been working on the problem. It looks like the 'collides or overlaps' doesn't like a constrain self.size.width and self.size.height. I'll try to rework that part of the code.

I have one question about Stretch. Is it will do stretch also for attribute that I put as number?

@RThurman‌ the actor attributes? Well I need to select real from the drop down menu then type in offsetX and offsetY.

collision sometimes does not work when using a constrain attribute, so I've rewritten the movement with change attribute: self.position.x = interpolate... The actors move fine, but do not trigger th

My actor is a ball and I determine the speed of the actor by constraining my game.ballSpeed attribute to magnitude(self.linear velocity.x, self.linear velocity.y). Then I check if game.ballSpeed &

I have 2 attributes:

@Alano‌ You dont want it to check for badlives since that attribute is for each individual actor and determines when that individual actor dies. Like you said you want to know when all the bad guys ar

My game is set so that after all the bad guys are dead the locked door to the room destroys. I did this by setting a rule within the locked door actor that when badlives=0, door is destroyed. Of cours

To answer your first question, this is what I would do. In the ball actor, I would create a self Real attribute called what touch am I. (It will be set to zero. Then create a rule that says;

Here is how -- in the blue actor, make two actor attributes (type = real) and call them 'offsetX' and 'offsetY'.

I think it would work if you spawned a new rectangle each time you press the turn key and constrain its position so that it changes its size in 1 direction so that it looks like it is moving. I'm not

I see how you made the Lives attribute locally within the actor. I made the attribute a game attribute.

Create a self attribute (Integer) call it lives. Change this number to the default amount of lives. When actor overlaps or collides with bullet change self.lives to self.lives-1.

Or, would you be looking for an actor that always moves vertically, faces vertically, but can be dragged to different horizontal points? I believe that's a Touch constrained with SelfY to MouseY (no c

@mathewvirgen‌ I ended up trying this out as I was planning on using it for a future game anyway. I ran into one problem in the method i gave you. The initial.x attribute would not reset the more you