It's 1:49am here and my 15 week old daughter just woke me up so I'm knackered, but just put a rule saying if actor overlaps or collides AND attribute self.linear velocity.x is greater than 20 (adjust

Create an attribute called Game.Accessory .

Try placing a constrain attribute behavior in the cloud actor:

First create 2 Integer Attributes:

Change attribute, rotation -> 0

Hi,

Make a self.attribute - boolean , call it "trigger rule c"

Obviously click through and select your score attribute instead of typing it.

Create a game integer attribute called 'Text'.

essentially I'm trying to work out if you scale the blocks side actors by a game.scale attribute (lets say value of 2), how far do I need to move their position...and then the same question for the op

after hours of trying to creating a system with so many rules i need your help guys, i have a group of 4 individual actors in my scene, aim doing a baseball game so i have a group say.

btw, all of these Rule behaviors test for a simple boolean true/false attribute.

I'm using a Game Attribute named Extimer that is an integer.

I have created a countdown timer game attribute and it works sometimes.

Enemies on screen (attribute) = 9, since thats what is on the first level.

i think i might end up with more than 200 games attributes. also does it matter if i don't use the right attribute, i still don't understand when or how to use like integer instead of real, so basical

hahaha this made me laugh. Sorry no offense intended. Its just funny how people attribute everything as a bug.

does the platform have physics > movable on ? Should be off so it's not affected by collisions etc

Just did a build with an actor that displays this attribute so I can see whats going on.... It says false and still no movement....

I have the menu interpolate out of the way when you press "start" through an a boolean attribute called "game start". If this attribute is true it will not move ont