Basically you create an actor with a spawn attribute to spawn a chosen actor into your scene. It works perfectly in Gamesalad.

(Quote)

Use an integer game attribute called game.weapon to designate the weapon number that is equipped. To find the attack value for that weapon, use tableCellValue(tableName,game.weapon,1).

I have a question, I have a game attribute called game.attk. I have an inventory that allows you to change which weapon(s) are equipped.

Create an attribute called game.ZERO and give it the value zero.

(Quote)

Then, when trying to adjust the individual attributes of the actors, it behaves as though they have not been unlocked - as if you're editing the prototype itself. The unlocked instances don't act as

At first I noticed some funkiness since my countdownTime was set to 99 and that %60 was, I'm assuming, putting it on a 60sec scale. I lowered that attribute and saw things were functioning just fine

Use Constrain and set self.Position.X to max(min(self.Position.X,320),0)

The angle is actually going to be randomly generated but you have given me my solution. I just need to make an attribute for the randomly generated angle and use a rule to trigger text when this angle

I have an equip button that basically says that whenever an item is selected and equip is pressed , equip that item and change attribute attack to attack + 5. But when I equip another item lets say it

2 check 'speed' attribute and 'position within' attribute (x: -100 to x:+100 relative to actor or scene)

(the first change attribute is to self.Motion.linear Velocity.X)

Without more info, I'd recommend - each time you want to move to a new position - using the scene.Camera.Origin.X & Y attributes, either in a couple of Change Attribute behaviours, or if you

these elements are built with behaviours, rules, attributes, animations, actions and so on, these behaviours, rules, attributes and actions have within them various values, mathematical operators (+

So based on what you said, I feel things should have worked. Divisor is an attribute with a value of 10 so your assumption with the numbers were right. I plugged in your formula and still nada.

I overlooked the problem I was having. Make sure that you edit the scene-orientation attribute in every scene, not just one.

hi

I also found a different approach, which is to constrain the x position of my actor and divide it by the width of the scene. This works for me because the start position for the actor is always at the

From this example I used the huge timer example at the bottom 00:00:00:00 (hours:minutes:seconds:milliseconds) only to use the seconds with a "countdown" attribute set to 99.