If the bullets need to rotate to a specific direction then constrain is a very inefficient (processor heavy) way of doing this, constrain is running 60 calculations a second for every bullet, whereas

I created my own time attribute because I thought game.Time started when the app was opened. To control the spawn time of actors, I need time to start from zero in each level and pause when the game

I appreciated your time and effort. Thank both answer my problem.

There is a game.time attribute that already exists by default and is already counting 1 every second, it's the thing that allows the timer you are using to count seconds !

(Quote)

Neither of these things prevents you from using game attributes from what I can see ?

@Socks @tatiang Thats my problem. I dont think I explained well. I cant use the game attribute because I want to have multiple characters at one time and multiple rocks. And the number of character

(Quote)

I got this working, to the point that I have an actor displaying text telling me when the game attribute controlled by alpha is true or false. This part of it works flawlessly, you can see after any s

(Quote)

(Quote)

4. These are two different attributes; refilling or using stamina will only affect "game.stamina".

You don't have to add a text attribute. Wherever you have your Display Text, just change it from game.number to game.number.."."

so your condition wont trigger , and change attribute stamina to stamina + 1 wont work . You will cause him issues later on this way.

* The "game.#ofStamina" attribute is just a time/number reference for next stamina refill. Initially we set this at 1. And when "game.time" is equal to "ga

stamina (if game.time = game.stamina*300 change attribute stamina to stamina +1) , and he wants to loose few stamina points every few seconds , how do you want him to start with 1 ? Im just asking

it doesn't matter though , thanks its a great video , and about the custom collisions and flip horizontally, is it something possible to have in the future ? or is it not possible with how it works?

I just come up with below idea, I think it should work (It does not need every timer or constrain actor, it should use less resources):

Create a game integer attribute call it stamina set it to the number you want , put a timer every few seconds change attribute game.stamina to game.stamina - 2

Sure, what you'd want to do is create a Boolean Attribute for the monster. Lets call it "Monster". This attribute will start as False (since the monster is not unlocked yet). Once th