Unless you have a reason to use numerical values (e.g. it's somehow a math game), I'd recommend storing text values in a ... text attribute. You can concatenate each letter by doing Change Attribute

original scene to show you have it right. The attribute "game.Word" (what you type in for the answer) is a number 77. You get this by adding every letter you typed (A=1, B=2, etc.).

Of course, the answer is always obvious once it's pointed out to you, and to think of all that time I wasted playing around with Change Attribute behaviours trying to get it to work.

let me know if you figure it out---drag in your constrain attribute to actor

constrain self size height to "touch" ???

@Hackim Okay, so boolean made. Ok so when the column is selected do change attribute tablecellvalue(game.(table name),(row selected),(column where boolean row is)) to true. Then if tablecellvalue(gam

If you make the images all the same size you can simply do a change image you could also include the new constrain conditions. Just wrap it in a rule that triggers each one based on the condition of a

thx a lot i fix it i make "save attribute" in 'replay' and 'home' buttons..

change attribute self.selectedcolumn random(1,2)

you'll need to record the initial touch position of Y (this is your offset number) so make a self attribute called TouchOffsetY and one called positionoffset

I love using the [ "attribute-name"..Attribute ] syntax in my display text expression editor so I can tell what is what when I have multiples on screen at once.

This would be hands-down easier if GS had joints. (which I know they are planning to add, but until then...) You can create a separate actor for each part, (arms/legs/head) and constrain their positio

in itunes connect the ID is money_1000 and on my table the text attribute is money_1000

Are the rules not working? What are you tryin to conver to and from? It might be the attribute "change" which you don't need. That was for demo purposes. You may delete that behavior

Please add custom collisions to the roadmap. I have an idea for a project but it would require this feature in the creator.

so try this make a rule in you ball like this and also make three game level REAL attributes Flipper_X and Flipper_Y and Flipper_Angular_Velocity

--Change Attribute: game.toggle = 1-game.toggle

a Display Text behaviour in each, showing your attributes, and one showing the level time attribute so you can get an idea of when certain attributes are changed/initiated/triggered.

First time using Load/Save Attribute. In GameSalad, when I click on Preview, my game runs and I changed the "High Score". I then press the Reload button just beneath the Preview butt

what i did is this....so each actor has a boolean attribute (isdead1, isdead2, isdead3) that becomes true when it the actor is destroyed