not sure on this without testing. but try having global integer attributes for

also if you wanted to save on performance you could avoid the constrain and just have the invisible actor move at the same speed as actor 2

oh if actor 2 isnt going to be moving around then you won't have to use constrain

Farther more , display text show you constant change in the attribute , with the debugger behavior we need to use a timer ... are you for real?! and it scrolls down so you dont see the new results com

Farther more , display text show you constant change in the attribute , with the debugger behavior we need to use a timer ... are you for real?! and it scrolls down so you dont see the new results com

Go through your Attributes, let's say, you want to watch the health of the badguy while your goodguy shoots at him, scroll down to 'badguys hps' or whatever you called it and select it. If you go to

It doesn’t show anything even I drag the debugger into the actor & select the attribute. Sorry i’m just too stupid enough to understand..... (Image)

If i remember correctly .. nope. Particles always emit in front. You could always constrain an actor on top of the one emitting the particles with the same image but no rules, that way the original ac

It was a sound bug that is supposedly fixed with this new update. You may just have to re-do the audio parts. The old fix was to add a change attribute behavior that set the music volume to 1 upon ent

I have an actor that changes it's self attributes named X and Y to it's current position each level. If I touch the screen the actor moves to the place I touched (by interpolating it's position to the

1 timer and a few constraints for custom font. But I use a lot of change attribute to random, maybe 250+ times.

Use a game.attribute that's an integer type. Call it whatever, we'll say its game.ActorImage

In the red "player 1 paddle" delete (or turn off) the two rules that are labeled "Move Up Rule" and "Move Down Rule". Then add a new constrain b

You could create a second attribute that keeps track of the number of balls the missile hits except this one should be under the games attributes. When you want the actor to display the text, have it

but in my game this isn't he case. I have a self attribute in the missile actor that keeps track of the score multiplier. It starts at 0, and every time one missile hits a ball, the multiplier goes u

How would I use SystemTime with a Text Display? I tried making an attribute called 'Year', then constraining that attribute to "game.clock.Year", but when I preview it it only displa

put 'debugger' behaviour into an actor (press the 'E' to the right of the debugger behaviour text box and choose the attribute you want it to show, it may have to be inside rules so it is triggered at

is it alright to have the GAME OVER attribute as a boolean?

Do you then use - straight after the spawning (or possibly even after "When BigRockDestroyed is true"), a change attribute BigRockDestroyed back to false?

Hi, sorry to hear you've got probs; Timers can be a bit iffy sometimes but in the main, they're fine. Not sure how you've used the Timers with reference to your attributes; and I've not heard of any p