This is most likely the case. I'm a little uncertain about how "progressing" works in the formula, like how it appears. Since if I constrain rotation to numbers being added, subtract

How is the ship moving (constrain, move, move to, interpolate, change velocity . . . etc) ?

Change Attribute self.A to "(self.B==1) and (true) or (false)"

All behaviours can be set to run at whatever speed you like, you can grow the size of an actor with lots of things, Interpolate, Constrain, Timer+Change attribute - etc.

Or is there an alternative behaviour or attribute that would do the same thing but could be slowed down just a little?

Use a loop to loop through the word. With each cycle, use the substring function to look at each individual letter in the word. Use a rule to evaluate if it's a vowel. If it is, add to an attribute.

Tks but that is not my question. I am asking wether I should use tablecellvalue+change table value or change attribute in order to get everything work faster.

You can have a blank text attribute. Just leave the space after "=" empty, that should work fine. See the attached demo for an example.

Yeah but the attribute should a,b,c...or z.

It depends on what you're doing - You can only use the Change Table Value Behavior if you're changing a table value. A Change Attribute Behavior cannot change a table value. Likewise, a Change Table V

No you can't have a blank attribute.

if attribute =

Change table value or change attribute, what is the best to optimize processing?

Nop, if attribute is a text, and this attribute has nothing attributed=> then...

You are saying if something is true (if the value is empty/blank) then do some action, when GameSalad looks at this attribute to check whether it is blank/empty what would GameSalad be looking for ? W

I usually add a text display...temporarily on my game scene to know wether that Boolean or what ever game level attribute is turning on/off or not.

If attribute 1 is

attribute A = 0

Could you not simply place the rule that checks for parity after the two change attribute behaviours in a timer (after 0 seconds) forcing it onto the next cycle of code ? I think that should work (if

Change attribute 1=> random(-1;1)