As for custom collisions, for the most part they seem to be working. The problem is actually with other behaviors such as Accelerate. It applies a force to the center of an object, so if the CoM is of

Can you just change the attribute value from 13 to 4 and then check it with your 4, 4, 4 rule? And if you need the 13 to display an image or something else, just use a second attribute to store the 1

I have 3 actors, each with a self.choose attribute...after 3 seconds it chooses (random 1,13)...lets say it choose 4....and that is worth 20 credits...but One of my "13" it chooses f

Can't remember which, but a GS staff member confirmed not that long ago that attributes - even quite a few of them - are more efficient than using a table. The big reason to use a table is easier orga

Not sure how that works still though if you've saved and loaded attribute behaviours, closed GSC then opened it again - surely reset would do just that - start you at the beginning again...

Im not sure if other people are doing additional or different stuff with their ball and flippers, so it might/might not work for others... or it might just be difference of opinion of how things shoul

You can save to one and load to another. You are saving to a Key, and loading from that Key. It doesn't matter which attribute the data related to the key is placed in.

So how I would do it is build my sections of track as shapes and use custom collisions. Then spawn the random shape based on the previous actor location. So each section of track will spawn it's locat

Hi @bernardo.chuecos Save and Load Attribute Behaviours only work on the device, not in GSC on your computer.

Also, does it work between scenes? Like can I save an attribute in one scene and load it in another one?

Can you save the value of an attribute into a key and then load it into a different attribute? Because I've been trying all night but now I realize maybe it isn't possible.

I appreciate your suggestion. I looked over your videos and it seems like it does not fit my problem. All i want is for the actor to collide with the wall. However, since I have many constrains that s

(Quote)

(Quote)

When you constain or use interpolate you override the physics engine which handles collisions. I recommend you watch my video series on the physics engine so you understand how it all works.

Change attribute game.row to random (1,7)

Change attribute Rand to random(1,6) - let's call this 3

(Quote)

Change attribute Rand to random(1,6)

Yep, you're close! On the game over scene, change attribute game.finalScore to game.score. Then use game.finalScore in the Display Text expression. The fact that game.score keeps increasing every 0