And if I change an image using the "Change Attribute" behaviour, is that different? Does that not experience the same issue?

The only major difference is that GS Windows doesnt have an 'index' attribute so you a real one I think.

(Quote)

So let's say you have an attribute that you're incrementing from 1 to 100, and you're using Display Text to show the attribute value. As the game runs, the engine will generate 100 textures, one for e

where the text changes, to say, another attribute value such as a score or timer value, or a table cell value, or...?

(Quote)

* In a Loop over Table behavior, the index attribute is incremented automatically. No need to change game.loopindex to game.loopindex+1. If you add a Log Debugging Statement to that loop and open th

Set your collide attributes for your actors then create a Boolean attribute and name it something like "interactions". Then you could set a collision rule like when actor1 collides w

me double jump but when I changed it Rule Check Attribute (according to the touch pad I assigned), it does not tally and give me 3 jump instead.

I made a game.closesttohero attribute. Then I tried making a loop in the missile and I'm just lost in there. Basically not sure how to make it say to check the cell value of any cell in column 3. Is i

Additionally, the simple bit of gamesalad knowledge I was missing is that one can simply edit a text attribute by clicking the empty space between the attribute and the word "text."

I don't know how your game is supposed to work but you also might consider not spawning actors but just changing their alpha value to make them appear/disappear and then constraining certain attribute

One thing to keep in mind is how GameSalad rules work. Rules only "fire" when their condition changes from false to true. So if you have a rule that says when attribute = 3 and you

Attribute>> game.player 1 keymap. Dpad Up>> contains >> blank

set attribute flag_load_notes = true

You could also loop the table and grab each value and compare it with the lowest value before it. So you'd create a game attribute and set it to the lowest value it finds first (which would be the fir

Sorting is handy but if you only need the single lowest value, it's easier to Loop over Table with a rule that checks to see if the current tableCellValue is less than game.lowest (set to some high nu

That's unfortunate. I'm not sure why you had performance issues with table vs. attributes but I would definitely use tables for something like this. And yes, you would increase a counter attribute a

I have 5 scene attributes named like so:

I've hooked up a PS3 controller to my Mac, and I've found the various Keymap Attributes under [Game Attributes] but they don't seem to be corresponding to anything. When I create a new rule, can make