So I am working on a turret defence game. I have where the turret rotates to game.attribute coordinates which are the enemy's coordinates. The enemies have self health attributes and there are bullets

That normally brings it to a nice stop. In most cases a change attribute will work too.

I've attached an example of one way you can do it. I set a 'Coin Spawner' actor that contains a 'Spawn switch' boolean attribute.

Thank you. I've neglected to use TAGS. Def keeps everything cleaner at least!> @AlchimiaStudios said:

On the home pane you can click on tags and create one for collisions, and drag in all collision actors there.

One way you could do it is to create an actor with two attributes e.g. "Cell read contents" and "Cell write row number"

If you have a long list of individual collisions is there a way to consolidate them all and maybe help optimize your game?

* Really complex constrains (nested constrains, expressions with tons of complex math used multiple times).

When [Attribute] [Devices>Platform>Language] contains [Russian]

It counts total seconds since timer is started. The date/time that the timer is started is a saved attribute so you can use the GameSalad viewer to test on a device.

I've created an actor to write the scene's camera X and Y to global attributes (so I can refer to them in other actor prototypes).

One way you can do this is to set Answer1 and Answer2 as global attributes.

As far as using attributes goes, you can't drag and drop from different expressions like before and even copy and paste has problems - it'll usually fail to copy the correct attribute and seems to ign

create a boolean self attribute name it parent set it to false

You can also "pass" attribute values to spawned actors through the use of game attributes. These rules will spawn three balls of different sizes...

2.0 online environment was I published my Custom Collisions game and then went to my Published Project Library (creator.gamesalad.com) and chose to import the published game into the creator 2.0 libr

"Custom" under the physics attributes for an actor and it pops up a window to nav to the JSON file I've created using PBE. However, in the GSC 2.0 when I do this, I can select &

Sorry but I gotta bother you one more time. In my tilt rules I can't put game.accelerometer.x-game.starting.x as the first attribute, so I made a new attribute called tilt.x and constrained it to game

What you can do is to refer to the original values. The way to do this would be to access the accelerometer value when the game starts and store this in a custom attribute such as game.startingX. Yo

That's initially what I was wanting to do. Is the (#ofTimes) a game integer attribute? Could you post a screenshot of what it would look like?> @Valan said: