(Quote)

To set the attribute at 0.3 to begin with, would i be modifying the Music Volume attribute underneath the Devices tab (highlighted in my screenshot) or do I create a new attribute within the Attribute

Rather than having the attribute set to 1 and then changing it to 0.3 with a change attribute action, I would simply set the attribute at 0.3 to begin with.

I have it set to play after .8 seconds of game start and because it's too loud, I've used "Change Attribute" to lower the volume to .3.

When changing boolean attribute it doesn't give me a true or false option. (Image)

Create a boolean attribute. Lets call it. goingtoscene2 and we will make it true by checking the check box.

the video was requested, and when the reward attribute is set, give the player the relevant reward. I recently implemented reward ads into a game that triggers them in three different places - though

Yes, attribute B would need to be an integer or a 'real' or 'index' attribute or basically anything that can hold a number . . . a boolean attribute can only be true or false.

(Quote)

Boolean (An on and off type attribute, good for switches and true/false type rules)

I make self.A and self.B as boolean in actor attributes (windows pc), however when I stumble upon your last rule:

Self.A and Self.B in my example code (in the other half of this conversation elsewhere on the forum) are two attributes I made, to make an attribute double click on the actor in the Actors window that

Working on pc. When changing an attribute, how to get self.A and self.B?

So rule> attribute > actor > then I cant find the collision. I am a total noob, sorry. Also do I need to type in ''true'' or some kind of number? (Image)

Make an attribute, change it to true when the actor collides with the floor, then use a rule that plays the animation when this attribute is true.

--Change attribute.

react to the changes. I have tried Bool and Constrain in many forms to try and have the reaction i am looking for. Any leads or suggestions would be greatly appreciated. I am thinking a numbered acto

By the way, have you considered using the MoveTo behavior? It will give you the same functionality as your current setup, and you won't have the overhead of all those constrain behaviors.

Probably the easiest way is to change attribute self.Motion.Linear Velocity.Y when the jump button is pressed.

Could it be that you use game.Time in some of the constrain behaviors (instead of self.Time)?