Is overlaping does not loop nor trigger actions. It test for overlap with another object like the description say. And returns true or false.
I'm clearly using "trigger" as a verb. It means to cause an event or situation to happen. It states in the manual that the conditions must be met for the action to run.
That directly contradicts what you were arguing before.
Here's some examples, In this case Is overlapping is allways true because the layout starts with the two sprites already overlaping:
1- Only run actions one time On start of layout
2- Only run actions one time every second passes
3- The sprite doesn't have animations so action will never run.
4- Will trigger once.
5- Only run actions when sprite2 is created and also overlapping. Only once.
6- This event will call a function that will run once every time a blue sprite is destroyed on screen.
That's only applicable to your case, in the examples it will not "loop" the actions even tho is allways overlapping. So that will be a wrong description.
That's not at all what I meant. I was talking about actions and only using IsOverlapping as the condition. By adding more conditions, you're just proving my point that conditions have an effect on the actions. Besides, everyone else has already said the reason the animations were looping was because of the IsOverlapping condition. I trust them. I can't tell if you are trying to be helpful or just argumentative, but I don't really care to continue this conversation with you any longer. All the best.
(Edited for clarity and kindness)