Here is what I would suggest doing. In every single one of the actors on the scene put a Log Debugger behavior. Doesn't matter what you put in it. Just put it at the very top of every single actor in

Hi thank you KevinCross. Are you putting this attributes in each actors? For example:

So i created a game.character attribute in the global, so now i have to create all of the rules in the actor itself now correct? What about the character select screen? dont i have to input something

It's tedious, but basically the weapon would need an attribute for ammo. Then, an actor could be added to overlap the icon. This actor would change shape based on how much ammo is left.

I haven't done this but I would think it be in the animation. Otherwise if the body of the actor doesn't move you could draw an arm and a sword animation in a separate actor and constrain it to the bo

Seems like you would need to have a "save attribute" behavior in there. Have you tried that?

Okay. So just so I understand what you're saying I would create an attribute -- it would be real? integer?

Hey thanks @SampleTest yh I am still adding in those features with head collisions and scene change. And which objects do I destroy to remove some lag? The only objects I can think of are boxes and e

"When you say "my items do not constrain with the menu itself" are you talking about the square menu choices that can be dragged (like inventory items)?"

(Quote)

(Quote)

Don't delete all of the actors. Try closing GameSalad and re-opening first. This fixes the self attribute problems where when you change one on the scene they all take on the change.

When you say "my items do not constrain with the menu itself" are you talking about the square menu choices that can be dragged (like inventory items)? What are you trying to constr

If you need to make complex rules such as collisions or changes to attributes such as game.power, game.lives, game.multiplier, etc., then consider using a text attribute. The advantage there is that

actor and stick in a timer and some change attribute stuff to make them change colour every second . . . but this change is not reflected in the actors on stage, they still think they just have the r

---in your 3-image actor----MainLoop either starts as 1 or change attribute to 1 in a go button or similar----

I got it working, the only problem is that my items do not constrain with the menu itself. I am kind of thinking that it's the Actor Tags that I have messed up because those are the only things that a

Change MyUniqueXPosition to a real attribute rather than an integer (or constrain it to floor(self.position.x) rather than simply self.position.x).

Great tip, I'd always constrain a larger actor to the main actor and use this larger actor as the hit area, but your method is much neater and saves two constrain behaviours too, a simple but excellen

This video goes over how to save attributes using the save/load attribute behavior. I used it and it works but I have had a few issues with it so I switched to tables which were easier in every way.