Hello,
Many many times, it’s very easy to end up with spaghetti with blueprints.
For so long I’ve been looking for a solution like “Named Reroute Node” from the material graph.
What is stopping you from letting us have this feature in normal blueprints?
This would be a complete game changer for organizing and productivity using blueprints.
For me right now, blueprints are total mess when it’s getting big, and it’s very hard to not let it go out of control.
This is such a simple feature to allow flow without having tons of lines.
Please consider implementing this…
A suggestion would be to create functions whenever possible and keep the event graph as main one and call functions accordingly, or we can have multiple event graphs but oh btw, what does that node do actually? ‘named reroute node’
Isn’t “CustomEvent” exactly a named reroute node, but also with possible inputs? 
Rerouting is just for organization, events, functions, macros have all their own uses
Can have inputs for events, can’t have outputs
OP’s issue might be related to more than just named reroutes, one way to avoid it would be caching, but it means you need extra nodes whenever you’re caching the value, new variables
Even if you put them under a category it’s just redundancy for a feature that seems pretty simple by nature but definitely would have a place
YES! I’d love to have reroute nodes in regular BP. There’s so many places I could use them to make Blueprints MUCH cleaner.
I think the fear might be that if they add it, it could cause a lot of people who aren’t too familiar with blueprints to misuse them. In a material, every output needs to be calculated. So if you have reroute nodes all over, it doesn’t matter. But in a BP where you have execution nodes, it’s a bit different. If you reroute an output from one event and use it in another event, it wont work unless the other end of the reroute didn’t use any execution pins (ie. const nodes only).
In theory, this can be easily done based on UK2Node_Tunnel. You need to link them to each other, bypassing UK2Node_Composite (it is a child of UK2Node_Tunnel).
During the compilation process, the pins will simply reconnect to each other, as happens with the Composite node.
If there are unconnected Execute pins on the input side, the compiler will report that the data will never be calculated on the output side.
But again, I repeat, this is only theoretical. 