Hi, I'd like to make a suggestion that the field shown next to the word "Attribute" under "When" in Rules, as well as any fields in attributes similar in size, for

Couple of things here: personally I'm still not sure if there's a simpler way to solve this prob; for certain, to do this in a program using some sort of Basic language would take only 2 or 3 lines of

- Create a Game integer attribute (I'll call it `10SecTimer`)

I had an invisible actor constrained to the sled to tell me that the tracks were on the ground. The actor was located on the track area extending a bit below. That actor had a rule that when it overla

Create a boolean Attribute, called something like 'dragging' (without the quotes).

too, but no change. I also noticed you named the attribute DragAnd Drop with space. Mine is all one word, but I can't see that mattering. I will try the same code with a smaller project size and see

1st. how to save and load any attributes?

Ok sorry mis understood I think. Are you using mouse touch attribute???

Hi Chrisal, thanks for prompt reply, but I dont understand, If I use Contrain surely I would still have to have a boolian 'speed1' to hold the constrain and then release it with another touch? The pr

Try to contrain attribute instead

will not Change Attribute speed1 to true. to restart the actor.

Then there is such a lack of access to things in script. I can't even just toggle collision on an object. I should be able to set an offset on the camera constraint. I had to add an actor to constrain

do you have an otherwise function in the accelerate attribute for the actor?

-change attribute selfposition.X to cameraOrigin.X+300

@ck ... I am definitely using change attribute to make the self.DragAndDrop = true, and constrain attribute with self.Position in the bottom rule, per the Wiki. I had double checked that because that'

ok so do i need to create an intiger attribute?

This may not be your issue, but I spent three hours trying to sort this problem yesterday. I finally realised I had used Change Attribute, rather than Constrain Atrtribute.

you could fix this by constraining an x and y attribute for where you want the trail to spawn, and then have these figures updated depending on the movement of the plane.

receives event - touch is pressed, then Move attribute.

It is possible: check out Save Attribute and Load Attribute. Basically, you set it up (which I personally haven't done yet in practice) all of your variables in game attributes. What's Saved is then L