Exactly what @Armelline said. Create a global attribute called game.save and in every actor you are placing have a rule that says when save is true, save position to table. Add a button to toggle the

I wanna now how to save an attribute that someone else (maybe even more than one person) has changed.

Basically you want to constrain the players x and y position in game attributes and when the player collides with an invisible detection actor (a large circle/square actor centred on the cannon) shoot

Self.time and real attributes can be just as intensive(or more) as an after timer. And yes, rules like that may help to alleviate the cpu load as GS will continually trigger logic on an actor that has

if you have a billion of them on screen yeah it will mess with the performance. If you have "constrain, loop" or other constantly running rules in all those actors the performance wo

I found out that my coins are causing the performance issue. They are small 32x42, but I have made loads of them. I even use self.time and real attributes, instead of ''after'' timer to save that cpu.

Just create a normal runner style game , then create an actor , place it on screen, unlock it and change scene.camera.rotation to 24 or whatever value, put a change attribute on the ground actors and

Make a global/scene real attribute for Enemy position x = Ex

also allows you to swap any other actor to be constrained to the movement control actor in it's place and the camera can float freely for cutscenes or to other actors positions if needed more easily

I could recode GameSalad's 41 000 files using GS creator with just about a few 1000 timers, change attribute, constraints and the oh so important buzz actor.

(Quote)

Almost all such issues can be resolved by adding an extra actor to the mix. Control all the movement with an invisible actor, and constrain the hero image to that just like the eyes.

(Quote)

(Quote)

* Just go into attributes and make linear velocity Y = -100

As to how, I'd probably make a text game attribute and then run a loop that does:

If you want to do it without unlocking the main actor , you can create 2 real attributes

the distance beetwen the players. I've tried to constrain it to scene size but it didn't work... I also tried creating a rule wich says (if atribute "distance" is < 500 chang

What I call "floating" behaviors can be a real killer, or basically, logic/behaviors that's always going with no rules. Such as constrains in an actor with no rules. So try and reall

(Quote)