What @baronedevelop says will most likely work and might be the easiest method. An alternative though is to constrain the player's X and Y position to two real game attributes, and within the cannon h

Create an invisible actor, a boolean attribute and a rule that says when player touches invisible actor than attribute is true cannon can shoot balls.

Im having trouble using behaviors to edit attribute on the scene. Can you pls help? Im creating a plane game and I want if all the planes are knocked out, the scene is changed to You win. But I have m

,1,5 is purchased >> change attribute Upgrade ? to true , and after 0.03 s save this attribute .

Ok, so you tried the method I posted, you saw the actor rotating, which you concluded was obvious given it effects the rotation attribute, so your question is does my example make the actor rotate (th

@RThurman, I actually used @timolarpe1998's example, although I might eventually take a look at Socks'. @Socks, did your example actually make the actor rotate while moving? I inputted what you put on

When abs(self.Position.X - game.heroX) < 100 Change Attribute: self.Shoot To: trueotherwise Change Attribute: self.Shoot To: false

I think you can create a giant square or circle (that is invisible) around the hero that when collides with the enemy activates an attribute that tells him (the enemy) to shoot. Or two (one left, othe

The parent's name holds the value (just like the idea originally sketched out in this thread) . . . . then in the parent's Spawn behaviour you change the Direction field to self.name . . . then in the

Track the hero's xPosition in a game level attribute: heroX

will include ten blank tables at the top of the Attribute panel (I hate that I can't sort the tables and attributes or images for that matter). UB and other standard game attributes with a lot of bla

@BonepileGames‌ I'm not terribly versed in Windows Creator (hoping to get VMWare running really soon though) and I assumed since this was in the Mac subforum that you were using Mac Creator. One thin

constrain self.motion.linear velocity.X to 3*(game.mouse position.X-self.position.X)

* create an attribute (ex. check = 0 ) and use it with the Rule, like in the image below.

I created a new concept for the reset scene behavior. Most of you probably know how frustrating it can be if you have to reset your scene and it needs to reset attributes as well. Bigger games have to

(Quote)

Constrain self rotation to vectorToAngle (mouse x - self x, mouse y - self y)

Another useful toggle switch is to have an integer attribute (set at its default 0) - let's call it 'switch' - and to use it like this:

On the left side of the rule, instead of selecting attribute, select numeric expression.

You can avoid this by using attributes in your formulas and always use the engine attributes in place of the ones you create wherever possible. For example the centre of your screen should always be g