The first is remove the self.bla=0 attribute from the first rule and test

you will need a separate Change Table Value attribute for each value change. Depending on how many changes you need to make at one time it can get a little clunky to work with but it makes no differe

So why is this firing more then once. It fires everytime position moves above and below 300. I change the attribute self.bla no where else in this simple project. Is this a bug in GameSalad. I'd like

Make a new integer attribute called "self.TempNum"

Make two text attributes, let's call them firstHt and secHt

I always make a mask smaller than the main hero actor and have the collision shape a circle and have all collisions in the mask while constraining the actor with the animation in to the mask actor.

Hey everyone, I have been making some good progress on a platformer that I am working on. I have run into a problem that hopefully I can get some help on. The game is fast paced, and built around the

first actor's velocity by storing it in a game attribute and then just have the other actor change it's own velocity to the game attribute when it spawns.

to the Animate behavior or Change Image/Change Attribute self.Image behaviors, which means that you would need to export video frame-by-frame and then import those frames and well, the current implem

In case the missions are always in the same order this shouldn't be to hard to do. Say for example the player accomplished missions up to mission 5 then there should be a game attribute (integer) name

As you see, changing "moveable" does more than simply constrain an actor to a certain x,y position. (Or is it less?) It essentially makes many of the physics interactions from Box2

not have any collision shape then you could constrain one of the two other actors to its position. Each of the other two actors would have either a circular or rectangular collision box but the main

At least i couldn't get it to work properly because i'm now spawning another actor with a different collision shape that replaces the other actor. But if you do that it doesn't constrain the velocity

I hope those are some good bug fixes, I can't even work in 10.4 or nightly because of actor attribute bugs.

there are many ways you can make checkpoints. I believe you can have a character spawner and an attribute called "checkpoint number", then you can have an invisible actor at your che

actor, it will change an attribute (game.Checkpoint = 1) so we know that the player have reached "checkpoint1", and when the player enters the "gameplay scene", th

(Quote)

Here is where my Noob-i-ness comes in. The answer is that rather than un-checking the "Moveable" attribute of the Target, I instead added rules to constrain it's X and Y position.

I want to try to save all my attributes in a table how I do it?

Let's say your actor is blue and then is clicked/tapped and changes to red. You'd use the following rules to automatically change it back after 10 seconds (self.clickTime is a real attribute):