You could try creating an attribute "resume." if resume is true, then #keys=saved #keys; if resume is false, then #keys=0.

I have tried to test Load\Save Attribute in GS Viewer and it seems it dosen't work. It should properly only in ad hoc?

So iam trying to see if the level unlock system save attribute saves the game state when you exit the game.I tried it on the viewer but it dosent seem to work.How can i see if its saving the last high

You'll see "Interpolate attribute" There you will click the "e" and do Self.Position.X, then right across you will see "to" and put the position y

You need to create self.start.x real attribute that you change to your x position because self.x is constantly moving, so will always be going up and if your start x is 100 and midway through is 250,

Yeh everything will always load like the 1st time unless you use the save and load attribute behaviours. If you're saving attributes you can load them how you wish. The way you want is in your button

I have 5 attributes:

TSB offers a free template that shows how to position an actor while still allowing it to collide with other actors. It is really an elegant solution to the constrain problem. The he demonstrates it

Constraints rule over everything including collisions. I would suggest some other way to make your game work without constraints.

hmm try putting the save attribute behavior in a timer every 0 seconds inside the mouse is down rule. I remember having a problem like that a while ago and that fixed it, but since then the issue has

Look at first shots of video in HD, you can see all game logic. I also tried to make a version where I load attribute on separate scene, same result.

Make sure you are saving the attribute AFTER it changes, also check to make sure that the keyword is the same in both the load and save.

Yes, But then it won't have collisions with any actors? GoodLuck with the physics, for doing things like the shocks/suspension or the wheels rotating/spinning with a physical connection and friction f

And not to keep harping on the issue, but I would like some more information or a PM regarding the camera stuttering/jerky movements on constrained actors. I submitted my project right after the last

I created a single actor on a blank template and gave him a text attribute called Key, and put in a load attribute behavior (loading self.key into game.test, also a text attribute).

co-ordinates from the player character, via a constraint behaviour. Could it be that the fact it gets it's co-ordinates via this constraint mean that the collision box for the beam is not updated wit

I have an actor I need to drop into all of my scenes to save the stats for the game. My question is this: If I have a text attribute on the actor, say, called key, could I type in the key (say the key

And not to keep harping on the issue, but I would like some more information or a PM regarding the camera stuttering/jerky movements on constrained actors. I submitted my project right after the last

I dont think spawning a actor in front so you cant touch works, try this in your first level when ever is complete to set game.level2 to 1(means also true ). And save attribute level2 key: level2.(is

Theres most likely a game attribute that tells it weather or not to follow the canon ball.