Constrains override the physics engine so collisions will not effect constrained actors. You will need to constrain the shadows to the velocity of the actors movement. There is a video over at gshelpe

I'm working on a project wherein I've created an actor, and have constrained its various body parts in order to get perfect collisions. It's working and its constrained perfectly but I have three issu

I would make a index attribute. call it Wave. Then have something trigger that attribute to change +1 after each level is complete.

Yep, the only reason I posted that was that when doing the 2 Interpolate rules version I noticed how much nicer it looked with ease in and ease out engaged (especially at higher frame rates) . . . but

Nice! I like the cosine method, but is there any way to make the sequence play linearly using one constrain? Since cosine tapers off the framerate doesn't stay the same and the last frames are shown f

which permanently increase a characters attribute, although slightly.

I have a question. Is there a known issue with tables at the moment? I have been having a rough time with one of my very simple tables. All I have coded it to do is record best times for each level of

* It would be nice to add a little bounce on (especially side) collisions. Currently it just 'sticks' to the obstacle and looks slightly strange.

A bad expression, trying to access a zero row/column or addressing a attribute wrong. Common errors that cause that kind of crash.

the viewer is more forgiving of bad code than an actual app. All it takes is a missing attribute in a rule, or an invalid table call to wreak havoc in an adhoc app.

And since you are changing the game.remove ads to "true", and saving the attribute, it will remain "true" as long as you load the attribute at the beginning of the

It´s basically the same thing wether you use a Table or attributes, but with tables it´s much easier / less work.

@NipaDidIt I already tried turning off the iAp & it didn't happen. My purchase table only has the ID & the consumable checked. 3,4,5 are blank. I turned of the change attribute game.b

Are you sure there´s nothing else changing the bank/star attribute?

Constrain rotation to rotation +1

You could also dump the two Interpolate rules and do it with a single constrain behaviour, like this, Constrain image to . . .

Try constrain rotation to self.time * X

* You do not need to save the PurchaseTable. Instead, save the game.Bank / star attribute.

Constrain self.image to round(X)

production speed not falling speed with a custom attribute. the script reads if attribute game slowdown is true produce every second, else normal production. the attribute slowdown I made is boolean