Hi @kipdev Yes, you can use Tables for saving and loading any sorts of attribute values.

Have you tried moving your windows bar to the side of the screen or changing the size of the star bar. IF that doesn't work you can try toggling your screen settings to move the actual display further

fun gameplay, but work on the collisions and ad some sounds and/or music

know what you want loaded from a table. Any attributes you need loaded to run the game must be loaded from the table with the Change Attribute action. Place an actor off screen on your first scene ca

Can someone please help me understand tables. I have a game where i have figured out how to save/load attributes and it works fine, even did testing on my phone. The problem is that i still have alot

"after 0.1 load attribute, made sure that "run to completion was checked. Also i put all of my save attributes into the SAME kind of timer. The most important step is AFTER you've m

Thank you for the reply.

And constrain all these shapes to the main actor.

@Braydon_SFX‌ @Socks Thanks guys, you just gave me another free lesson, the GameSalad Pass the Buck attribute.

the behaviours (by copying and modifying attributes to EXACTLY match a manual duplicate of my none-spawnable actor, and surprise, it started spawning the new one fine (and I double/triple checked - A

Constrain X to A x cos ((B-self.Time x D) x sin (self.Time x C)-E)+ X pivot point

Constrain X to 100 x cos ((70-self.Time x 10) x sin (self.Time x 250)-90)+512

Rule: When Attribute scene.SceneFin is trueChange Attribute game.FinalScore to game.FinalScore+scene.TotalTime

Thanks for getting back to me Matt. Unfortunately, I was already trying the "move to" attribute and that works to get the character to the base of the slide. However the problem I am

goes down by 5. and then i thought maybe a constrain position x, sin function of bouncing sin(self.time(bouncing *10))+start position x. Based on orbits, the idea is that bouncing is the period of th

I've seen that effect, but I know ive beaten it while still using constrain positions. I'm honestly can't remember what ive done differently now, though....

dead attribute when touching the red

Really? I;ve never had them fall through. Are you sure its the constrain position that does it?

@‌Tosanu The reason I always do constrain self.motion.linear velocity.Y rather then just constrain.self.position.Y is because it allows the player actor to collide with the ledge better. in my expe

If the platform doesnt have to move in Y at any point, you can instead first get Core Y, and then constrain Position Y to Core y.