-
If you have an object checking for collisions with a tag it belongs to and itself, it will activate the collision event on itself.
-
If you have an object checking for collisions with a tag it belongs to and itself, it will activate the collision event on itself.
@thecheater887 what do you mean it will activate the collision effect on itself? Surely it's not activiating without colliding with anything?
-
@thecheater887 what do you mean it will activate the collision effect on itself? Surely it's not activiating without colliding with anything?
@jack8680 that’s exactly what it’s doing.
I’m not certain if it’s once or lots of times, but It occurs just after it spawns itself.
-
I think I know why this happens...
HyperPad may see this as an intent of the object itself since the object is in the tag's group. Similiarly to using the loop behaviors to iliterate each object, it does it to only one object at a time.
In this case, the collision behavior will activate the following events because of each object that is collided within it's tag, it will have the intent of that object that it has collided to.
For example, two objects are going to be used. Object 2 is in a group. Object 1 has a behavior where when it collides within that group to change the color of it's tag. If object 1 collided with object 2 with the tag, it will change the color of object 2 as object 2 was the intent of this case.
This may be confusing, but I learned from experimenting with tags and looping properties.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login