I have a consumable IAP (a Bomb). Works perfect in IOS, but on Android, the IAP is NOT being consumed, therefore when player clicks to buy a Bomb (after buying the 1st time), it automatically gives i

This bug can be avoided by just using an attribute instead, but I guess how viable that will be will depend upon the complexity of your project.

So, you would generate a normal / bump map from the original image, then render the image with the bump map applied from a number of angles (as many or as few as you need / want / like) . . . you imp

changed it to the spawn moment y position, and constrain the character position to it, it worked. Many tks

is easy, trivial even, it consists of a single constrain behaviour which constrains the image to the angle between the actor and the light source.

This looks cool! Looking forward to this when its released.

If you want it to spawn in the same place you could make a variable for when they die and a variable for EnemyX and EnemyY. You could then constrain those with "attribute EnemyX = self.positi

(Quote)

-Change Attribute self.Physics.Bounciness to 1

What are the names of your actual attributes? Perhaps it'll work when it's laid out properly, rather than pseudocode.

don't use constrain. just set the Y value when the object is spawned with a change attribute. change the y value just before you spawn. it's that easy.

(Quote)

I've never watched that tutorial so I can't offer any specific advice on it. However you can simply use an Integer Attribute in place of the Index Attribute. The only thing an Index does that an Integ

So I set one of 5 characters are chosen with different attributes, also same with the enemies.

Everything Rabid Parrot said except the last bit I would not have the rule just the constrain attribute self.posY to self.MyY and make sure the building actor has fixed rotation. If they are all self

(Quote)

You can do it now ! You just need to constrain the image used to the vector to angle between the actor and the light source.

button and replace with the particular button's attributes (after trying the easy route of going though every behaviour to see if I could spot the mistake).

Change Attribute game.Value to (game.Value%game.Top)+1

Constrains can slow things down but shouldn't cause logic not to fire off. The best thing to do is put in some debug behaviors and see if rules are firing or not. From time to time rules can get corru