Hey Wes,
Thanks for the reply!
I’m at work at the moment so I can’t test this exact setup, but I tried something very similar and it had one glaring flaw.
If I have two objects with that blueprint right next to each other, when I go from looking at one, to the other, the first one I was looking at never notices I stopped looking at it, because the sender is still saying “yes, I’m hitting something that has this tag”.
What I’m currently trying to do is just make it so the object sees that the event is running on it, does a function (in my case, changes its material) and then changes it back to default once the event is no longer running on it.
the other solution I was playing with was maybe having my tracer always send to the last two objects it hit, that way they could compare names and see that they weren’t the current target, but I was unable to figure out how to store things in arrays, and I’m sure there’s some much easier solution.
I’m also worried about having a bunch of objects laying around that are running constant event-ticks, I’m not a programmer so I don’t actually know how bad it would be, but I would think having 10-20 of these objects around would be a significant performance hit due to all of them spamming event-ticks (again, I could be completely wrong)
Again, I haven’t tried your exact setup but I do think it will have the same flaw I mentioned above. I will try it later tonight and check back.
Thanks again!