* if global attribute is 1,

(Quote)

Hello everyone! Is it possible to flip the image of an actor when the actor he is forced to change direction without using the game attributes or collisions? I saw that I can't say "when its

The attribute game.manAng should have a value between 0 and 360 depending on where you place the actor. See the attached demo. You can drag the white rectangle around to change the value of the vector

And then you can have the bullet actor check for collisions with actors of type "killable"

There are two sides of the coin - rules for actor bullet's collision, and rules for actor stealth's collision, (some if not many of the rules are due to no accessing self-attributes like I keep taking

Hi, could you pls help. I constrained game attribute, say "angle1" to an actor's angle (type - angle, via vectorToAngle). Then when I tried using this game attribute, angle1, in calc

Change Attribute self.critical to floor(random(1,100)/85)

track it or we have a device attribute that constrains the counter. The game logic can then update that number or clear it out.

(Quote)

There are other ways but @UltraLionBlu's way is simple and easy. Except you can say game.criticalChance random(1,100) like he says, but only need one condition. <=15 will give you either 1-15 (

change attribute game.criticalChance random (1,100)

I can think of MANY time saving changes. While I really appreciate GS transparency, I have to confess I feel like I'm paying for an unfinished product (well technically I am lol). > @Armelline…

(Quote)

just thinking off the top of my head, maybe use a global real attribute that is preset to 1 and is used on all actors that you need to change (call it motionFactor for this example)

I know all I do is nag you these days but if you could find a little time to make the "Choose" button be highlighted when making attributes, so we can just hit enter to make them, th

attribute redacting issue looks fixed. thanks @adent42

depending on what you’re trying to do, you could just have an actor offscreen that triggers the attribute the play button does without being pressed, and get rid of the play button.

RC has been updated for the instance attribute editor color issue. I just need to figure out what's going on with android app signing and I think we're good to call this a wrap!

If you reference other prototypes, what happens when those prototypes go away? Or the event triggers for an actor that doesn't have that attribute? (BTW the names of user defined attributes are just f