Make a rule with a list of 10 or 12 conditions, make the first one simple - for example if attribute X = 1, then with the rest of the conditions really make GS do some real work, a few long numeric eq

Did you replace this part with the game.ItemPurchased boolean and save attribute just without the timer?

Constrain N to N/1.005

Quick question. If I have score attribute. And I want it to change to 1 if score is = to either 0,4,8,12 etc,

you're probably missing that constrain in the else if you just want an attack to spin and not worry about water.

I have encountered an issue with the angle attribute for the attack actor. I'm aware that it was a new added attribute, but for some reason when I make an angle attribute for the attack actor it doesn

@taylorH1 you don't need tables at all. I use them because it helps me keep track of my game and seems to help with performance however it makes things very hard to read. Anyways no basically you put

@Armelline

What I was saying was don't use 5 digits per score (for 00,000), that along with a change from Constrain Attribute to Change Attribute dramatically lessens the strain on the processor, much less (of c

@TaylorH1 also if this wasn't understood set the damage attribute to a greater number when [game.HitCount > 3]

Since when you click Back in the Creator, nothing has actually happened yet - no table data has changed, nothing should have triggered your "bought" attribute - this implies it's an

constraint attribute

From what I remember the display text behaviour is behaving like a constrain with similar performance hits.

(Quote)

So naming the self attribute the same thing across the entire game in all the "next level" buttons will not have any negative affect whatsoever?

A self attribute would mean having to code every single "next level" actor in the "sub game". Doesn't a game attribute just make that a whole lot easier?

The only reason not to use a game attribute is becuase game attributes are always scanned and add to your code as where a self is only part of the code scan when the actor is on a scene.

I'm also confused about where I should place the "request purchase data" behavior, and the callback attribute (I made it a game attribute, not a self attribute).

(Quote)

(Quote)