(Quote)

Yeah, I have tried a bit of debugging and I can see that attribute reach 0 and then I used the same rule to spawn an actor and that works!

Hard to tell without seeing how you've set things up. The way you've described your rule sounds good, but are you actually certain the game.attribute is actually reaching a value of <=0? Use th

I'm trying to get a Level Complete screen to show when an attribute becomes a certain value.

2. I created an attribute for the button called "On Off State"

* Fixed the issue with center of mass and collisions

I think there was some talk about text input directly to string (attribute) becoming available soon in this thread here . That would certaintly simplify things in GS.

(Quote)

(Quote)

Follow this one and it shows how to keep collisions intact and you can just freeze the Y and put walls in the end for your sliders to collide.

at one time, so tutorials will often say to constrain to the mouse or something. However, because I've got two people doing this at once, I'm afraid that makes it a multi touch situation. I'm not sur

Just a guess, but did you make sure both actors are on scrollable layers? If you try to have collisions between actors on scrollable and non-scrollable layers, you will get both false-positive and fal

I have spawning actor that every 5 seconds will spawn one of four different actors ( A,B,C and D ) ..based on a random spawning attribute ( SA ) this attribute changes every 5 sec with random value (

For the first one I used a constrain attribute with; self.image to game.points%10, and floor(game.points/10)%10.

In the CoinsLogic actor, we use a timer and local game attributes to reevaluate how many seconds have passed since the game was first launched. The AF_SecondsAfterLaunch attribute has filled in the fi

* In order to evaluate them, you need to have some kind of identifier (either a number contained in an attribute or maybe a table)

* In order to evaluate them, you need to have some kind of identifier (either a number contained in an attribute or maybe a table)

But when I tried to use logic as attribute "if x is true then move >>>" If false then move <<.

(Quote)

If you had a game attribute (let's call it 'X') which changed from 0 to 1, depending on which way you were facing, you could - for example - set the direction in a Move behaviour (for the weapon actor