You only need to include one poorly thought through constrain behaviour in each character to reduce the number you can have on screen, moving smoothly, from 50 to 10 . . . and by the same rule a simpl

Change attribute game.X to random(1,3)

For example, attribute X will be set to 1,2 or 3 every second. If the same number is randomed twice, then change X to one of the other 2 values. If this is not possible, at least change for e.g. If 1

Swap out the first Change Attribute behavior for a Constrain Attribute behavior. I originally had that but took it out in order to try and avoid constrains.

would just increase the column number: Change Attribute game.columnNum to mod(game.columnNum,4)+1

On the other hand, it may be even more beneficial that I run the site myself so that I can put more time into to it, tailor it to the wants of the community, and moderate it to ensure high quality mat

Your rule needs to change a boolean attribute (e.g. game.Change or whatever you want to call it) to true. Then in the other actor, have a rule that says If attribute game.Change = true then ... chang

that on your game over screen, add the Change Attribute behavior just before/above the Change Scene or Reset Scene behavior that you're using.

(Game.PAARTE is a real attribute changed for self.position.x)

Make a 'real' attribute ('A')

Attributes do not reset themselves. If you are using a game attribute such as game.score, you'll need to change it back to zero when your game resets by using Change Attribute game.score to 0.

I've bought a template that has custom attributes, and I see the custom attribute is a function. I am a coder and would love to learn and understand the functions behind the custom attributes -- wher

at the first 'change attribute' in the second box is standing: game.score1-game.keyboardinput

The way I did this was to make the input a text attribute and the rule for adding a digit (pressing a button) limited to textLength(game.input) < 2, or for your needs, < 3. It would tak

Change Attribute game.clickTime (real) to game.Time

attribute

Does anyone know how to use the network send and get attribute rules in the latest nightly build? I was looking at the json.txt file and this is what it sends to the php file

One more question.

Presuming your Speed attribute is a real attribute, you could use a Constrain Attribute behaviour along the lines of:

Make an integer attribute called game.playerTurn and set it to 1. It will switch between 1 and 2. Make two more integer attributes called game.player1Score and game.player2Score. Make a text attrib