Hey guys, I just need to know how to change whether or not an actor is moveable to false, I just went change attribute self.physics.moveable to false, didn't work, ?? if anybody could tell me that

keep in mind, when you use stuff with a Creative Commons License you will need to attribute the artist in your game (credits scene), and sometimes the license is for non-commercial games only (but not

Attribute

I had this same problem. Found the answer in another thread. Just remove the .png from your rule that changes the image attribute. So instead of saying 0.png it would just be 0.

I have an actor above the scene(my scene is a portrait game). My actor has a timer, every 2 seconds run to completion spawn actor:(actor) in front of actor direction 0, sideways position random (10,63

would i still have to add an accelerate attribute to the actor?

I had a similar issue myself. I ended up making a self attribute that would then trigger the particle animation in another rule.

I am considering when self.touches=2 I will constrain X and Y positions for at least 2 seconds to ensure the particle effect runs its course. Not ideal, but I guess it will have to do. I just havent b

The only different i have in the load attribute one of them are loadis and loadis1..

A tip: if your game starts to become complex, attribute names you've given, like ix and iy, will start to get confusing for you, especially if you name all other attributes in a similar single letter

Yeah the whole distance thing is a magnitude calculation. Also if you need punching and kicking characters you will need to constrain boxes to the hand or foot of the character that is attacking when

I have a mute button on the main menu. Do I have to say when this button is pressed change attribute say..Game.mute=1 and then have every single sound and music in my game under a rule when game.mute

I thought I read some months ago that you should use the change attribute when it comes to the size of an actor if you want the collision area to change to that size, too. Or am I wrong?

you should you constrain for that

I've never thought about this but now I need it for my game. If I constrain an attribute to X then 1 second later change it to Y, will it still be X or change to Y?

alright so I'm using an attribute for keeping the score of the game and when ever the user gets enough points the scene is going to change, so I was wondering if I could re-use that attribute for the

my actor moves fast (y linear velocity = 200), and it has a control camera attirbute, but the camera kinda follows it with jagged movements, not smoothly, is there a way to fix this?

In the interest of processor/resources is it best to create 7 different colored images and have an attribute with a rule that changes the image of the actor? OR, should I create a simple white circle

Create a game attribute equal to 0. So then, if you have a button to activate a box in your scene, create a rule in your button that says when pressed, change attribute = 1. And then, when you code ev

So i have this box in my game. I have this box set to not movable. And then i have this button in my game that when it is pressed, it turns the movable on in the box. I have a game attribute set up an