Hi, yes, as @simo103 said. A way to do this is to make 2 Text attributes; call the first one QuestCurr and the other AnswerCurr

Is it possible to type a word to change an attribute to true?

Change Attribute GremlinsVsSanta to random(0,1000000)

Anyone have any suggestions as to how you combat this? It may be a setting or attribute I used that may be the cause of this.

One way would be to make an AmountSpawned integer attribute that increases by one every time the spawner spawns an actor, and then in the spawner you can make a rule

I have an attribute called "GremlinsVsSanta" that goes random from 0 to one million (999,999 to be exact)

hi all, so i have a table with 5 columns all tex attributes and say i have the word "house" each letter on a different column

@rhinokey Hmm! Wonder what I'm doing wrong, then. Yeah, I am using Constrain.

are you using constrain attribute to make them move? or change attribute? i use constrain to keep any random weirdness from slowing them down. i also use constrain on y to keep them from movin down wh

So, to clarify...I'm not using Tile in any of the Actor attributes. I'm trying to 'tile' Actors by placing them one after the other. There's no gaps appearing within any Actor, the gaps are between Ac

Yah, that's kind of what I was thinking. So instead of say "when RIGHT is pressed, move right" say, "when RIGHT is pressed, attribute Run Right is true, and when Run Right i

I can turn off the collision on the actor that is being touched. The problem is the items still on the conveyor belt will collide with it because their attribute is not changing. (Note that they are d

on second thought, for the lin x i am not setting it in its motion panel, i am using a constrain atribute maybe the constrain is why i get no gaps

If you use a global boolean all the actors would stop colliding when one is grabbed because they all adhere to the on global attribute, however, if you make the attribute for the actor only, no matter

After posting my questions I can across "Save Attribute" which seems simpler to use instead of tables (?).

@uptimistik sorry man, but your project works perfectly but if I copy EXACTLY the same rules in my project they don't work. I saw that my shake attribute is triggered to "true" and a

gameAttribute: index type … name it X

… where the player is:  gameAttributes: playerX and playerY

of. It is more complicated than it seems as each attribute, actor etc is given identifying numbers by GS and just sticking two scenes into one would likely screw up all those numbers as some may be t

You need a Game attribute to track the maximum number of hearts. Call it maxHearts, for example. Set it to 6. Now, in your behaviours that add a heart for eating a fish, add a Rule at the start saying