Create a new Index attribute. Make it change to a random value between 0 and 1.

You can change the ID number for Game attributes in the project's object.xml file.

Setting them up in the new project first won’t work. The name of the attribute you see is basically just a name tag. The attributes actually have a unique ID. If you make a new attribute in the second

(Quote)

If you find an issue with this, you can always relegate some sounds to another actor through a game attribute.

Constrain Height to A*sin( game.time*B )+C

How can I constrain an actor at the bottom edge of screen and make him grow back and forth in height?

In my case, the number was 2416 wide. The first attribute addresses the Device screen size. The width of the iPhone X is 2689. That is a constant. The change attribute is the width that you want the

I'm don't know what goes on under the surface, but like I said in my (deleted) post each actor would need quite a few constrains (x, y, rotation, height, width . . . as well as a few others) to positi

Although I always assumed the Pivot aspect was just an in built constrain that GS added in. I didn't think there was a difference between using the in built one, and simply using the constraint behavi

When I enter an actor from the scene level, click on edit prototype, add a self attribute, and then hit the back button, the attribute does not show up in the self list for the actor on the scene. I c

(Quote)

I have to admit - not sure why it's working until I can have a play (unless it's simply because it's forcing the mouse attribute to be read and so updated, or forcing a 'click' once a finger is held i

(Quote)

Tried using it with 10.12.6 and it crashed first time using it, and I can't even remember last time the last version crashed. Also when I added a change attribute to actor attributes not showing up af

I tried your fix @Japster but I don't know how I can edit the scene camera's origin using the "change attribute" function or anything similar. I'd really appreciate it if you could e

TIP: Better have a non-action-useless actor unlocked somewhere in the game scene, and use him to constrain all scene.attributes to some game.attributes... that way you don't have to unlock every actor

That's pretty bloody far in, for any button to STILL not be recognised properly / fully. I'll test using TOUCH game/device attribute rules tomorrow, to see what my visual limits test goes out to, so

prec(attribute.a/attribute.b,5)

i have 2 attributes and wanna display them as text...