I have a scene, it has 5 buttons- when I press one an attribute called ButtonChoice is changed from 0 to either 1, 2, 3, 4 or 5.

Actually, making a new condition makes the right side show up. You can then delete the new condition and not have to reselect the attribute.

I don't really need to know the names of scenes and when text will and will not be displayed or about the 'fill' actor or how the buttons work or the names of your Save Attribute keys (and so on !) I

Change attribute: game.character select To: 1

-Change it back to "attribute"

Notice i select attribute condition but the rest is blanked out so can't finish it, only way to fix it is to delete the condition and redo it.

When [numeric expression] mod(attribute,5) = 0

@Socks you have given me something to adjust. I did not have a code to adjust the global CurrentPlayer attribute. I will add this a see If I get a better result.

Change attribute: game.character select To: 1

(Quote)

Atribute - CurrentPlayer(the global selected character saved attribute name) = 1

I see, I was confusing constraint with constrain. Yes, the 'When X < 10' would be one of the rule's conditions/constraints.

re: constraints. I'm using it in the more common usage sense than the Behaviour sense. The "When X is < 10" part of your suggestion looked like a constraint to me; one of the

I've not suggested using a Constrain behaviour (if that's what you mean) ?

Attribute game.CurrentPlayer (this the save attribute with the selected character number) greater or equal to 1

I forgot to say that I created a global integer entitled CurrentPlayer. CurrentPlayer is the save attribute for the number of the character selected for game play. I am trying to call this "C

the need to store extra info. I added a save attribute to the character select screen (specifically the next button -- which already has the conditions required before the game player can go to the

I mis-expected what the "max" function would do, and when looking for alternatives the ceil seems to be about rounding and Constrain seems to be more of a post-process than the pre-

I am trying to figure out how to interpolate camera to zoom out and at the same time keep it centred. I am fairly sure that I need to Interpolate or Constrain Camera Origin as I interpolate Camera Si

When attribute is >1 and <7