It's a fixed text attribute. You cannot concatenate attributes to the end of it.

create an integer attribute (game.NumberOfActors)

Ok is there a trick to copying 5 actors in each level in the scene, each of which have a different interger value in its attribute and pasting them into the next level's scene? I have 20+ levels and I

Attributes don't really kill you. It's what you constrain to them that can be the real factor.

Haha. I figured out how to do exactly what i wanted. For anyone interested, yes when you create the prototype actor you cannot make it change any scene attribute. Only it's own. (previously stated by

ultimately it is just how creatively you use global attributes and the save attribute behaviour. there is no 'one way' to do it, depends entirely on your game and the attributes in it.

Yeah the number of Actors isn't really the issue, there's several factors. In one of my Scenes I have close to a hundred Actors, but the frame rate stays at 60, and the RAM is under control. You have

make sure theres not an empty attribute in the actor.

---Constrain game.CharacterPosX to self.positionX

Simply constrain the x and y of the character to two attributes, then constrain the x and y of the box to those two attributes (Image)

I have seen some threads that say that a scrollable actor cannot spawn a non-scrollable actor, unless a clever workaround method involving a game.boolean attribute is used. I do not understand how to

First make a game integer attribute named "shoot"

I currently is using a attribute and set to true when button is pressed, and in the ship actor, using a timer to check for the attribute and spawn when it's true.

Try changing an attribute where you are expecting the destroy to happen. Have this displayed in an actor on the scene and see what happens.

TIP 1) All attributes that were made by the user (ie NOT self.position, game.Time, self.rotation, etc) will NOT copy over. Instead GS will put "game" where it used to say "g

Based on my limited experience with GameSalad, a fairly large game could conceivably have a extensive number game attributes. It would be nice to have the option to create attribute groups or folders

double check the scene that is failing. It sounds like you might have a rule somewhere that has a bad attribute or trying to play a sound file you've deleted. The GS Program seems to handle these bett

Couple of ways to achieve what you want though. I made the gravity continually change during a game by using accelerate instead of the gravity option. By giving an actor an accelerate behaviour in the

Well now don't take this the wrong way but i found if you can edit the rules for an actor once it is in the scene and click that unlock and you can use the constrain attributes behavior and I set it t

That value could be controlled by an attribute and then you could use interpolation to control that value similar to an acceleration behavior. Then if the pause button is pressed...the interpolation