i made made a integer attribute, set at 0.

If you use spawning prototypes in your game, which also have scene-attributes inside them, your prototypes will become uneditable.

IF you resize your background actors, then yes. That's why I specified you're better off using a properly scaled image for backgrounds. Instead of resizing the background, change image attribute to p

1.) Create a boolean game attribute called "isPad", or "isiPhone" or simliar. (I went ahead and made booleans for iPad/iPhone/Android/etc. so that when the options

You want the Save Attribute and Load Attribute Rules

Not sure I completely understand the question. But you might try making the visible battle ram one actor. Then constrain two invisible actors to it where you want the different collision effect to o

Crop off the transparent parts of the image. GameSalads touch and collisions are based on the Actor size and the actor size is set by the image dimensions including the transparent areas.

^ it makes a lot of sense, but I can't see the main actor as selectable option in the change attribute, all I see is "Game, Devices, mini actor".

Create an attribute (INDEX) eg: counter

Constrain self.rotation to vectorToAngle(self.Motion.LinearVelocity.X,self.Motion.LinearVelocity.Y)

Now in each actor let's start with Red do if touch is pressed and BlueTouched = false and GreenTouched = false change attribute RedTouched to true otherwise change attribute RedTouched to false.

Add two 'change attribute' behaviours to the mini actor.

If two actors are trying to constrain the same attribute, it will flicker... as they constantly overwrite each others data.

I want to know what exactly constraint is doing (code wise if possible). It seems to do something that either was not intended or makes no sense to me at all, this case would be....

Use two integer attributes: randNum and oneOrThree

I think I got it to work.. Don't know what was actually wrong but I deleted the attribute and all the load/save behaviors then create a new attribute with the same name and placed new behaviors in the

have a game or scene integer attribute that each of the buttons puts 'their' number into when touched but in the rule for touch have a second condition that only if the game integer is zero. This way

I need to apologize if there is any confusion with the save/load attribute issue. I misspoke when I stated (in a past thread) that this was a "known issue". I meant that we were awar

Make an attribute called Good? and set it to 0

Here is I am doing it. Would be Great if some of the GS expert can suggest. I save the last level complete with save attribute and a key. At the beginning of the code, I am loading the level complete