Download

Curiosity: When To Use Additional Event Graphs? (In a Single Blueprint)

Blueprints can get messy, there’s no doubt about it. So far I’ve used Nodes, Macros and Functions to create more efficient code and to cut the amount of wires floating around the blueprint. One thing I never really explored was the functionality to create multiple event graphs within a single Actor Class Blueprint. I was just wondering out of pure curiosity, under what circumstances do you peeps start using multiple event graphs?

Most common usage I’ve seen revolves around grouping like-events in their own graph. IE- Input graph, RPC graph, physics/movement, etc.