This is just…
Yeah, it really is. Now only this needs to get fixed for perfectly looking blueprint:
Wires which don’t stay at the same height.
Haha, thanks, glad you like it. However, I still recommend using custom events or variable set + variable get in almost all cases where you want a wire to loop backwards 
Cheers,
Michael Noland
I’m using it inside of macros that i want an loop inside of it that emulates tick behavior, so i can’t use events. What exactly do you mean by variable set and get for it?
This makes me mad, oh my OCD, I spend hours trying to fix it.
:p](&d=1434473560)
@: Variable set + Variable Get when moving a data line backwards (versus an execution line). @Both: This also has the added benefit of allowing you to control the value the first time the loop is executed, instead of it defaulting to the ‘0’ value for the type, as it will if you try to use an output from a node before it has been executed.
For execution wires, the benefit of a custom event is readability. You could name it something like ProcessNextActor, and call it both from the loop start code and the loop continuation code. A backwards wire works fine, it’s just hard to trace if the body of the loop is large.
RE: Usage in macros. Yeah, a backwards wire is often the way to go there, there’s no getting around it.
Cheers,
Michael Noland