Well yes and no. You can interpolate the self.color.alpha attribute to 0 if you want to fade out, and while the image alpha was at 0, your could fire a change image actor and then interpolate self.col

Polygon Collisions Are on the long term roadmap. Just not sure when they will be here the old full road map is not visible anymore. Just the sept. and October one. hopefully by the end of the year tho

There are two device attributes: Audio.Sound.Volume and Audio.Mute.Volume

errrrrrrrrrrrrrrrrr........... not easy. you would have to fill attributes with the x and y s of all the points you wanted saved from spawned actors that would have to have complex rules to recognise

[FYI....For anyone else trying this, make sure the actor that controls the camera is not the same actor that triggers the game.setback=true attribute. Otherwise the camera then moves first and you ge

The other would also be a text attribute. One of them would be the temporary name. The other would be for storage. You would simply add the temporary text to the storage text attribute. Then reset the

UPDATE: So what I did to get it to work is go back and copy an existing visible element and just drop it in as is, no modifications, and then see it display. Then I changed each item, one-by-one, pr

That isn't my problem. It is not an issue with collisions, read the post again. Sorry that it is a little confusing, but this problem is fairly complicated.

There is a bug In GameSalad where Collisions are not detected properly while sizes are changing. So that is why it acts funny on you. Unfortunately you'll have to think up a different solution to the

is dragged into the box (collectBox), an attribute (numberCount) is incremented. When a numberBlock is dragged out of collectBox, numberCount is decremented, so that numberCount will always show the

Although, CodeMosters, you said you had to put in 2 attributes, I am guessing 1 of them would be a text attribute, what would the other be?

1) Create an attribute that will store your name input. well call this name. Then create another attribute to store all names. well call this storage.

I believe you need to constrain it to the X and Y location of where you want your paddle to be.

For example, I create a rule to update the Game Attribute game.score to game.score+ some value when an actor is touched. For the life of me I can't get the changes to stick.

So here's the logic: [BARRIER]: when collide with {Block A}, and Attribute: 'game.BlockVelocity'=0, then: "Change Attribute: game.Win to True".

I have an attribute with and interval called Gameplay Start and its set to 0. then i have two different rules on my character actor. 1 for the animation with a rule that if game.gameplay.start = 0 th

Nope. I also have a command that makes your power go up ever 2 seconds and there are things you collect while flying that also give you power. But when you run out you hit the ground and you are game

For hit points make a self.integer call it hitPoints and set it to say 5 and do a rule if it overlaps or collides with cannon change attribute self.hitPoints to self.hitPoints -1.

So it checks whatever game attribute you're using to for the power level and if its zero it will break the rule. I assume you wait a few seconds and power climbs back up? At which point he can fly aga

In the resume button i have made a rule when touched change attribute to false