Is there a reason you're using a table? It's much simpler to use a single attribute:

Just make a game level attribute, let's call it FinalScore . . . . then at end of each level add the level.score to the FinalScore.

Use the attributes to re-spawn the actors in the correct location.

The demo saves the attribute, but I cannot get it to save the spawned actor. When the player taps on the actor to spawn it does spawn in the new saved attribute. I want it to spawn to the same place

I tried that. It remembers the position, but when I come back to the scene, the already spawned actor is gone. When the user spawns a new actor it is spawned to the saved attribute of the last one sp

I just need to make it stop at the top and bottom but I think I will be ok with that by using a 'If Y = >top extreme then constrain to a Y value' type thing.

I have seen before where it doesn't always work, mainly because while its programed to go too to bottom they run somewhat simultaneous. Which means if you have a lose change attribute it may be able t

(Not at a computer right now) you can put the Constrain x, y and such on a rule that does when mouse is up.

You might want to consider using triangles to figure out whether the kill shot has been hit depending on the location of the player/archer and the enemy. Constrain game.playerX to self.position.X and

change attribute high score to score

* constraint attribute, self position x, to (whatever position here)

Some of the problem may be due to the fact that collisions rules act up when a constrain attribute is in effect. There is a tutorial by GSHelper on how to get around this. Check out the video below. (

are properly cropped. Even so, you may need to constrain a transparent actor to each one of your interactive/collidable actors. Essentially Hitboxes. You can resize these until you get the desired co

Constrain Attribute: self.Motion.Linear Velocity.Y To: ((game.Mouse.Position.Y+self.offset Y)-self.Position.Y)*100

I don`t think we can do that. As you said, with interstitial is an easy task, just condition the change scene with a rule referring to a boolean attribute and you are good to go. But the problem with

few actors you won't want to deal with Save/Load Attribute behaviors. It's much more efficient to then use a table instead since table data is automatically loaded at run time and a single Save Tabl

In the rules of santa you can find change attribute behaviour down

The problem is that you are using a timer to set the attribute to "no" every second but the player won't necessarily click/tap at exactly one second intervals. For example, let's sa

(Quote)

Just replace "game.Time" with your own counter attribute. Something like this: