There is a new option in the latest update to do 'better collisions' have you tried turing that on for your actors?

I was hoping that when the radiant vs angle bug was fixed that it would help somehow. I was also very hopeful when I read about the options of assigning better collisions to actors, but unfortunately

You've tried checking the better collisions and unchecking the can sleep options?

(Quote)

detections could happen at the same time. I can constrain detection actors to each by updating all of their positions in the table but I don't see how it's possible for anyone of those actors to know

(Quote)

@IceBox your example reduced game.health which would probably be the players health. You wouldn't want to have a game attribute for each enemies health

* For a game with many enemies on the screen at once, I won't be able to track each enemy's health in a way that the projectile actor can do the health subtraction. If the enemy can't be the holder o

The rule would have to first be false again (no collisions) in order for it to trigger on the second collision. If you move the rule to the projectile actor instead, it will trigger when that actor

constrain motion linear velocity x to 0

@Icebox I changed the code from "Change Attribute" to "Constrain" still having the same issue. I have attached my walking rules and my jump rules. (Image)

My method for both is similar to those I've linked, but is different in a few ways. Most notably, it relies on no constrain attributes for the Stretch method. A huge thanks to both, though, for sharin

@Icebox Thank you for your help. when i get back to my machine i will try swapping it from change attribute to constrain. Thanks again for your help. I will update you on if it worked later on this ev

Change attribute fires once if the condition is true , constrain updates constantly. It might be something else thats causing this though , test it

Mine is setup as a Change Attribute. It works great when using the keyboard for the left, right, and space bar. but buttons not so much. So should i change it from Attribute to Constrain. if so what i

is it a change attribute or a constrain ? can you show the rules ?

Use constrain motion linear velocity x instead of change attribute or move for movement right and left

Hi Everyone!

change attribute self.color.green to

The difference is that I reset (change) the value of the attribute each time the timer runs: