Colludium already gave an example of this earlier in the thread. Using Overlap + Trigger Once, you may run into a situation where the the original object overlaps a second object while still having already overlapped the first one earlier in time. When this happens, Overlap + Trigger Once will fail to trigger.
This limitation can get exacerbated if you make use of families: Obj1 Overlap Family + Trigger Once.
For example, you have a Farmer object, and a Fruit Family which consists of three different objects Apple, Oranges, and Caimitos.
Your collision routine is:
- Code: Select all
Farmer Overlap FruitFamily + Trigger Once --> Spray the fruit with pesticide. (the fruit remains)
Here is a situation that might occur:
- Farmer is walking quickly through the garden
- Farmer overlaps an Apple
- Overlap triggers and fruit is sprayed.
- Farmer sprite is fairly large and overlaps an Orange
- Since the farmer is still overlapping a FruitFamily (the apple), the overlap event will not be triggered.
So basically, the overlap will NOT trigger again until the farmer is not overlapping *ANY
* FruitFamily objects. On collision does not have this limitation.