I do prefer using a counter attribute with a Timer behavior with 1/FPS for the every timer, or the mod+Rule condition trigger to increment the counter, because you can control the start and end of the

the actor acts in every way that it's self attribute is its own. But if I delete the self attribute from a copy, the other copies on the top level still have the self attribute visually but it break

I also like how some attribute formulas can use math to do interesting things. I managed to make an awesome attack that changes size and shrinks depending on a power meter and depletes when the energy

You sound like you have been at this more than I have, I think I understand though, I am still learning the relationships of each attribute and behavior; and how they relate to each other. It is weird

When X(the game attribute you create) is true

Make two game attributes for your characters self.x and y. Use constrain attribute to do this. Then make another character and constrain their x and y positions to the game attributes that are linked

I hate to argue but this is not so much a "bug" as a design choice. @slowcut explained it well above. Prototype attributes are available to their instances but each instance doesn'

(Quote)

By "instance" I think he means unlocked. No if you are spawning the actors they can't make the screen shake. You would need them to trigger an attribute that n actor controlling the

I should add that the self attribute from other copies stays, but all references in the logic to that self attribute are changed to 0 values.

No, you misunderstand. This bug occurs with prototype objects, not with unlocked unique versions in a scene. Copying a prototype as a new prototype, and then removing a self attribute has the effect o

Right now, I am setting my original camera / x,y attributes when mouse button is down rule. Then I do the constrain camera stuff that is discussed above. It scrolls when you touch and drag until edg

Hi it would not slow down your performance if you use some constrain behaviors in your game.

I was wondering if I could get your thoughts on what would be more efficient requiring less work for game salad. Having a simple constraint to do a process, or adding a line or two of code but removin

In the GS version that I use, it is only possible to delete self.attributes from a prototype.

To give context, what I did originally was I created a "universal" object/actor, and placed within it general properties that may or may not be used across objects/actors that I woul

Ok I think I'm missing a loading attribute.....and it would be put in the high score actor ?

You can make a game attribute (call it something like 'train_moving') and check if it = 1 then play animation. then have a rule that changes the 'train_moving' attribute to 0 when the train stops...

Ah, thanks for the feedback. I put the kph display for fun, but since I had put the x-speed value as a real attribute, it shows up with decimals and changing it to an integer attribute makes me fear h

You forgot to reset your score attribute. Game attributes do not reset when you change scenes. You have to do it manually (change attribute game.Score to 0).