makes sense. Just use the device screen size attribute

@tatiang, you kinda of lost me, where do i put in the change attribute? on the image that i want to display for the value in the table for the stars?

You can do change attribute self.Image to tableCellValue() where tableCell Value is an integer and your image files are named "1.png" "2.png" etc. I think it's not

How is this possible? Because i say the video on how to constrain an image to a column and use a trigger to move it to the next row. But that is something different than what i am trying to accomplish

The way you communicate between actors is through the use of game attributes (or unlocking actors but that's another story). Have one actor change a game attribute (often a boolean but it's up to you

sounds like a plan - but how do I change the opacity using a change attribute?

You have to constrain not change to. I use that method all the time and it works, but you have to constrain. And I don't believe it will show up properly in preview. You have to test it on the device

I used the integer attribute when touch is pressed change attribute game.music to (game.music+1)%2

want the bar to grow. Set the copies to your XP attribute*. Set the spacing to self.size.width.

(Quote)

Okay, you'll need to make use of the game.Screen.Device.Orientation attribute which changes from 0 to 1 when rotated. If you add that as a condition, you'll be able to have two separate rules for neg

(Quote)

To add to what @kevincross said, when you add your game.score.count attribute change the number next to it to whatever you want it to start on like what you said of 5,000,000. You can also start at 0

Change Attribute: game.totalScore = game.totalScore - 1

Hello, fellow Salad's! So, I've been working on this advertise-purpose app for my company which is pretty much based on the "button game" where you had to press a button 1 million ti

use a random "spawn actor" attribute along the x axis to make actors fall from the sky. Is there any way to dynamically update this equation's minimum and maximum values to fit the

You will need a text attribute. An actor that is the box. A rule for when actor touch is pressed. Inside that rule put Keyboard Input. Have the Keyboard Input feed it into your text attribute you made

and not see anything happening even though an attribute is storing the information. It may seem like a no brainer that that needs to be included with a custom keyboard but it's not a trivial matter

The trigger fade actors are just separate actors that change a game attribute's value. That way, the black rectangle actor can "keep an eye" on that attribute and act a certain way

(Quote)