this without spawning I would need to create 2 constrain attributes for the gun's position and then a move to behaviour to move the particle to wherever the gun is in the scene. So will replacing one

i see you added an attribute to the bullet,god thats been testing me for hours

when you use the( if )does that mean change attribute

create a self bolean attribute called rotate

in your bullet have it set attribute,game.shoot to false

3 actors bullet,aircraft,fire button( 1x boolean attribute,(shoot)

You can try making your own boolean attibute (ill call it lock) that turns true and false when you want. Then have a rule in the actor when attribute lock is true constrain attribute self rotation to

make 2 game level attributes of type "real". I'll call them PlayerX & PlayerY

If you mean, does that app splice the 2 corresponding project files together at the XML Level, whilst adjusting every ID Tag of every file. Whilst renaming every attribute object, asset, image, file,

If you mean, does that app splice the 2 corresponding project files together at the XML Level, whilst adjusting every ID Tag of every file. Whilst renaming every attribute object, asset, image, file,

You can create one instance and have it constrain a global attribute you created to the camera attributes (or any other scene attributes).

If you mean, does that app splice the 2 corresponding project files together at the XML Level, whilst adjusting every ID Tag of every file. Whilst renaming every attribute object, asset, image, file,

Basically, The layer movements are constrained - relative to the camera's position. You can't get that data unless you edit an actor in the scene itself, as it's a scene attribute.

Thanks a lot. It works perfectly with change attribute behavior. Great (Image)

3 actors bullet,aircraft,fire button( 1x boolean attribute,(shoot)

self fixed rotation is a boolean attribute. You need to change between true and false, not numbers.

How big a head ache do you think it would be making a game like 'Game Dev Story'. I've only briefly thought about it and can see it would need a lot of attribute tracking, and lots of maths.

you can trigger actors with other actors simply by creating attributes.

1. Can you use less timers? For example could you use a timer to set an attribute to true from false or 1 from zero and then have that attribute change trigger other actors rather than putting timers

Basically, in any one scene I have 3 actors spawned, 6 destroyed, up to 4 timers and a bunch of constrain attributes. I know its better to start an actor off screen and then move it in when needed ins