you are free to ignore that method and instead constrain individual character elements to each other . . . here's project I made to help GS users link objects, hopefully it might be some help to you

Now I just need to figure out how constrain the sword properly...

Create and integer or boolean attribute when your game starts for the first time it goes straight to the tutorial screen when the player exits the screen change the attribute and save it to a table so

And I'm not looking to interpolate everything you need for the tutorials on timers and if attribute statements. I was thinking of a more suitable overlay, maybe even a different screen.

@Muphins(Quote)

Or is the coin constrained to the pelican's bill?

Right but this is an attribute that we would set up completely separate from that. It would make no sense for Gamesalad to arbitrarily change boolean attributes. If that were the case then we would

Get the unlocked actor to pass some useful information into a '.game' level attribute (which any actor can access).

@jmachado999 A sort of workaround to this would be to place an actor on the right of the scene at the edge and have a global attribute for scene width you create. Then constrain the attribute to self.

You'll need to constrain an invisible actor to the Roll actor and have it move up and down in sync with the animation. Then create a rule on your main character actor that checks for collision with t

(Quote)

game.RollY to check its value and make sure the constrain is set up properly.

Create attribute Roll.Y

You could also create a custom hit box. Create an invisible actor and constrain it to the "things" x and y and say when player collides with custom hit box then game over.

You need to make sure there is no extra space in the image file below the visible portion of the "thing." Or, you can just code it so that the main character actor is only affected

Attribute Boolean: Pro? = False (Show Ads)

There a couple of ways to do this but the easiest way I think is just to create a Game Attribute (Boolean). Name it Show Ads and set it to True. Then on the screens that you want to show ads you cre

"Index" in this context refers the Table Row, not the type of Attribute. As @CodeMonster and @colander said, use an Integer Attribute. I also never use the Index type.

Change attribute. self.motion.linear velocity. X To 0

Create a real attribute called game.raceTime and another one called game.bestTime. Set game.bestTime to a large number (e.g. 9999).