any problem, i'll check again if there's any constrain rules that's causing that, or if anyone else can confirm that their integer type attribute doesn't have any issues.

Set the prototype up with a rule that says when Self touched state is true put coordinates into game attributes, lock the pop menu to those, then when the speed choice is made and put into a game numb

Use a timer. When the actor collides with the power up, for 10 seconds change attribute.slowmotion to false. And use an otherwise...change attribute.slowmotion true.

In your button add a change attribute behavior and set it back to what ever you want.

Which Behavior do I use to have npc1 shoot a bullet at player1. I've got a constrain for player1 x and y, but no matter which behavior i use the bullet seems to either freeze the screen to fire upwar

Create a self.boolean attribute called GameOver. Make sure its unchecked. Create a rule that when the actor collides with a wall, change attribute self.GameOver to true. Then, put ALL of your moving r

location AT the time of the shooting. If I constrain it to his location, it just tries to follow him instead of moving straight off the screen.

You have to reset the value for the Attribute in your buttons to return to the menu.

If you have any change attributes free inside any actors in the scene those behaviors will also run after you reset the scene. Reset scene changes all actor positions back to the original spot and res

the scene, it now resets at least 2 of my attributes, where as before I had to reset those with change attribute. I still have to reset them, but it also resets attributes not on that scene, like gam

As you can see I'm having a lot of trouble with the joystick because this is my second post about it hahaha. I took all the code off of the Official Cross-platform Controller Template and I put the ba

I'm planning a couple of games where probabilities might come into play. Say you're making Oregon Trail, and you want at any given time for there to be a 5% chance for game.attribute "dysent

It's quite easy to do. Simply use a constrain behavior, constraining the camera rotation to 0. Then the cam won't interpolate its rotation, it will simply flip.

It's quite easy to do. Simply use a constrain behavior, constraining the camera rotation to 0. Then the cam won't interpolate its rotation, it will simply flip.

In my case I use an actor as the spawn generator to produce different actors in a time and attribute enviroment. The timer does not work correctly and most of the Actors spawn randomly on places there

do it using attributes like change attribute or constrain but I don't understand how to use min, max, or how to put greater than and less than signs in change attribute equation editor either. any id

Attribute%2 = 0

Change an attribute value equal to the attribute you are checking value % 2

with each update the creator gets better and faster, so things will fire differently then before. For example it seems yo ur case is the spawn is happening as soon as the attribute is turning to 0, so

when actor is spawned at the start of game it turns attribute actoronscreen to 1, when he dies it turns actoronscreen to 0.