I've been able to resolve these issues in the past by doing some live debugging statements. I add a display text to an actor and keep concatenating letters to the end of an attribute within my other r

you're referencing a table cell and you have an attribute for the row or column. And then another actor is changing the value of that attribute and at some point, it might become zero briefly, well,

2) Change attribute IMAGE to its corresponding size and type

I will also check "linked to an unlocked actor using constrain in relation to an actor".

this. it was linked to an unlocked actor using constrain in relation to an actor that wasn’t on that particular scene. may not help but just throwing it out there in case it does.

Make an attribute called BeginTime (type = real)

1. I set an actor to display attribute:timer decimal.

I have of course set the attribute self. Nearest to = 9999

answer adds or subtracts from an index/integer-attribute (stored in another table, perhaps) for each of your characteristics, you can compare the users answer-attribute to the attributes you set in y

* Crash in pause (not Pause Game Attribute, make custom pause game)

What would be required to weight the answers like this? I can imagine the basics of having each response tied to a particular attribute, for instance, but there would then need to be a rule set up to

I believe the Save Attribute and Load Attribute behavior keys are case-sensitive, so "x" and "X" will be treated as separate keys.

For example save attribute to "x"

Do you really want to have to drag-and-drop 100 Load Attribute and Save Attribute behaviors and keep track of 100 different keys? (Image)

Figured it out - I just made a 2nd text attribute! So 1 text attribute gets the questions from column 1, and the 2nd text attribute gets the scores from column 4. A display text behavior for each, and

it's storing all of the data in a single text attribute.

* Fixes to a dynamic collision bugs (i.e. when you use rules to change collisions and stuff just disappears).

(Quote)

Change attribute game.whichRow to random(1,10) * 2 - 1

It moves because you constrain its position to the mouse, before spawning the new one. It leaves the spawned actor where you pressed the original one.