I’m struggling with what I think is a super basic communication issue. I have a bit of blueprint scripting that I want to trigger a notification that is being listened for in a different part of the blueprint. I want a “Start The Thing” notification to fire off of the first bit of scripting, and elsewhere in the Blueprint it’s listening for “Start The Thing” as a trigger for a separate bit of scripting. I know I can just make a bunch of spaghetti to achieve what I want, but I’m looking for a clean solution. I’m surprised by how difficult this simple task is!
If you’re communication is simply talking to another part of the same blueprint use a custom event.
Knowing exactly what you want to achieve here goes a long way, as does showing code.
I knew it would be something easy that I was overlooking. I was trying to use Event Dispatchers but Custom Events are doing exactly what I want. Thanks!
Dispatchers and Interfaces are for Actor to Actor communication.
Dispatchers require binding, which means the two or more actors communicating must know of each other (requires casting).
BP Interfaces don’t care about who’s calling. They don’t need to know (no casting required).
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.