I'm making a game attribute - a boolean - which turns on at the beginning of an animation. At the end frame of the animation, I tell the game to basically switch the boolean rule back to false. This w

Yes. You can type it directly into the field in that behavior without opening the expression editor. If you do use the expression editor (I don't recommend it in this case), be sure to enclose the k

Your all codes looks perfectly fine there look no problem but maybe you can change your attribute to boolen from integer.

(Quote)

Make two Real attributes...call it Pos_X and Pos_Y

Here is the reset button. It changes an attribute that controls whether or not a game reset will be triggered:

If you show us all codes i will help you. Can you use any attribute for resets maybe problem stay on that.

XML can be messy, but when it comes to attributes, it will accept any change in their order without any errors, so long as the format stays the same.

That's my approach too, I never use tables and always prefer attributes, maybe it's just habit, but tables seemed to throw up a few bugs from time to time whereas attributes are a core mechanic of GS

I always thought that would be a useful attribute within the physics options, alongside friction, bounce, density and so on, you would have 'noise' where you would introduce a fractional amount of ran

(Quote)

(Quote)

I'm a fan of attributes, and favour them for things that people will often recommend tables for. Tables are hugely helpful and valuable, but sometimes they're just not needed.

I suppose tables are essentially attribute groups.

@ellison You can create a boolean attribute called game.firstRun and set it to true. Then use this rule:

You don't really need any of these rules, timers or attributes as they're not actually doing anything, for example why check - on a newly created actor - whether it is newly created, as the result wil

Now I have taken your proposal with the Timer + Change Attribute.

When move and velocity are used the actor becomes unstable. To see this use a text display to display self.position.y. It jumps around causing unintended collisions with the other actors.

It sounds like you're changing the value of one or more attributes and you have rules that destroy the tabs actors based on the value of those attributes. If you don't want the tabs to be destroyed,

I have noticed I am collecting a large amount of game attributes starting to build up in my new game, can you put attributes in groups yet or no? If no, will it ever be added?