Multiple Box Collisions created but only the last one created does the Event OverLap Begin fire

Hello! I’m sure there is something I’m just not understanding in my stupidity, but…
Building a Blueprint, and having issues

A. I have one blueprint, creating Multiple Box Collisions

  1. For the Add Node, selection of parent, I’ve used a Spline Component,
    and just a Scene Component (top of the heirarchy, spline component is also attatched to the scene component)
  2. For the collision, it’s set to generate overlap events (via a Blueprint Node)
    Collision is also set to be enabled as well (via a blueprint node as well)

All of this works, for the LAST Box Collision created, but ONLY for the last box collision created.

If I create 20 box collisions, only the 20th (relative to 1) will honor the Begin Overlap and fire the event,
or perhaps they are all firing the events, but the event is being tossed away, because in the event graph
there is not a node that specifically states Event Begin Overlap (name of variable)

So what I’m looking for, is a way, that as the box collisions are being created, they can be
set up in some fashion, such that either the box will fire the event (if it’s not), or that the
event graph can be set up, to catch the event.

I personally think there is something about the event graph that I am not understanding.

I think the box collisions are firing the event, but that there is nothing in the
event graph to catch it. For the last box collision is working as expected, and it
does have the variable name associated with the Begin Overlap Event, I can see this
in the editor when using PIE, the reported collision box is generating the event
and the event graph is responding to it, and the unique name of the last created
Box Collision is exactly the same as that assigned to the variable name.

I mean I guess, one method would be to create 500 dummy variable names, set them
all up in the event graph, and just put a limit on the blueprint. This I do NOT
wish to do, it’s extremely crappy coding, and feels like a hack. This also extends to
the End Overlap event, but once Begin Overlap is done, End Overlap can follow the
same path.

I’m using version 4.8 and 4.9 preview 4

Any thoughts, on my obvious quandry?