It’s the actor instance you’re sending the message to. Imagine there are 3 chairs and you want to sit on the target one - the one you’re close to, for example.
1 Like
to that makes sense but how would I do it for level blueprints
You want to target the level blueprint? There should never be a need for that. This would be an indicator of a flawed design choice for communication flow. Do note you can build complex logic without ever looking at the LB.
But it’s there for us to use, ofc:
- if you have actors in the scene, reference them in the LB. Drag them there from the scene or right click in the graph
- right click scene actors and bind dispatcher calls
- get (all) actors of class and bind dispatchers
- have a dummy actor in the scene and communicate with that actor instead
- use traces / overlaps hits to have actors communicate what is needed
- use a framework class aa a hub, thr LB can acess it, so can any other actor
All of these are better choices. If you absolutely must, GetActorOfClass (level) and send it an interface message. But this sounds like going in the wrong direction.
Another option is to tell us what you’re up to. Perhaps there is a more elegant way we can point you to. Perhaps theres none and you are, indeed, stuck with the now infamous LB comms.
ok ill redesign the part i was targeted and thank you very much for the help this has taken over a week for this little side quest