but constrain the max y of the ball to the y position of the line.

You would use the same key name for each attribute. So if you are saving the score, you might use Score and then if you are loading it, you would use Score again. Each attribute needs its own key.

I'll save and load in the easy way... and I'd like know... if I can use the same Key on save and load attribute to save all things in my game (levels unlocked, points, lives...) or I need create a dif

I have an actor with the code: control camera and also constrain self.position x to touch + scene camera origin x (same thing for y). Scene width is 2000. The actor moves perfect with the touch until

ok, thank you, the funny thing it's, a file that I downloaded have this attribute, but I can't create another one. weird...

Why in the windows version, don't have the attribute "index" ?

A good way to find out if it's working or not is to put a display text in the controller and have it display the "up" attribute. You should see it switch back and forth from True and

Change Attribute NewPowerUp.Position.X to ??+width of powerupimage * tableRowCount(game.YourTable)

From my own experiments (and perhaps related somewhat) I do know that cycling through the colours of the rainbow (using 3 constrains (R, G, (Image)

(Quote)

I tried to switch to a constrain on self.id but of course that then just changes all the self.id's to the total count so they would all change to 3. Hmmm

When attribute scene.completed=true --> change attribute game.velocityX to self.motion.linear velocity.x; Otherwise --> change attribute self.motion.linear velocity.x to game.velocityX

I'm not seeing anything unexpected on the Mac version in Preview. The bullet spawns on top of the actor rather than at the mouse click location, but moving and shooting seems fairly smooth. I did no

The idea is to have a rule that says When attribute self.Image = [some image name] --> [perform some action]. self.Image is any one of the animated frames that you're using.

Without that, I'd need to know the shape (e.g. circle) of the area you're trying to constrain the eye actors within.

@EricTippett A white box usually means that your Change Attribute expression doesn't match your image name in the library.

if you are using a ton of images, it can cause the ram to skyrocket and crash. if you have a bad attribute or rule (caused by deleting an attribute), that will also cause it to crash.

My Adhoc keeps crashing for my game. I am not sure if it is image optimization or attribute issues. What would be any other reason for this happening before I take my game apart for diagnosis?

@Braydon_SFX - You mean you go to delete the attribute and see which actors it's referenced in?

I tried the Change Image suggestion however it does not work. The image is now just a blank square. I didnt want to use constrain because you said constrains are bad. Why isnt the Change Image work