if game.score is greater or equal to 100, change attribute cu1 to true (cu1 is just my code for character unlock and the numbers represent which character is unlocked i.e. cu3 is the third unlock). T

Your unlock is not a consumable, the attribute saves when the purchase is made. The product is is the save key. Etc... All of this information is in the documentation on the cookbook.

I think I may have solved it. Just not sure were to put the save attribute in terms of hierarchy in the rule when the IAP is finalised (see attached image). I got the load attribute all sorted.

save attribute show ads

I am not sure how to save the attribute change after IAP purchase and load it when the app loads again in the future.

If using iads or similar, use the attribute that tenrdrmer mentioned, after the attribute is changed, save it and have it load at the 1st screen your game goes into for future plays.

@tenrdrmer. Okay I made an actor on my home scene that says "Remove ads". When the user clicks this actor it prompts an IAP which changes the attribute game.showad to 0. When the att

I have to admit I do not use in-app purchases as I am not pro, but if there is no easier way, you could have the purchase to change an attribute, which would then cause a different scene to appear fro

I had a go for about two hours and have search these forums and didn't get anywhere. It might be simple but I think it can't be done as in app purchases change attributes and I am no sure if the banne

I've been playing around with it a bit. I changed the reset game button and put the whole time-stamp loop randomization into a rule 'if attribute game.button = true then randomize, And had the loop c

Constrain rotation to: AAA*sin( game.Time *BBB)

You're welcome, @Chakku, glad I could be of help!

Thanks a lot! My mistake was to put the Particles behavior in the timer IN ADDITION to the change attribute! I do need to do some tweaking, but you've been a great help (Image)

I see you have no touch or attribute trigger to start....but, for the record, I forgot to mention that another type of trigger is a Timer set to Every! (Like you have already...)

work because the Partical Behaviour hasn't any constrain capabilities built into it's code, if you see what I'm saying... and even if this attribute was constrained outside of the Particle Behaviour

My problem is trying to have the quantity of the be a continuously changing index attribute.

Hello @Chakku attributes in the Particles Behaviour, as long as they're put in via the expression editor - as you've done, all work well, but any new attribute value change means the Particles Behavio

So I was trying to increase the quantity of particles depending on a constantly changing attribute. I did it all as you would imagine, I hit the 'e' for expression editor and inputted my preferred att

Perfect!! The randomNumber attribute is exactly what was I missing! [Yes I only had 3 rows in my 'inventory' table (0,1,2).]

however, the problem is that the same collisions are occurring out of the players view when the moving objects leave the playable area. It isnt a bug, the code is working as it should. Im trying to fi