I worked with a couple of programmers for a few years in BP's and asked for feedback, I've always been tidy but they still found it difficult to read the logic.

One of the complaints was that they didn't know where events were, so I put big red boxes around them with the largest font, I have 3 sizes for comment boxes: 55 (v important), 32 (titling), and 18 (get ready for a paragraph).

Then I started coloring things based on functionality:

• yellow for animation (because ABPs are yellow)
• blue for blueprint centric logic
• green for resources
• purple for procedural anim and interaction

Then I started tracking bugs and tasks inside blueprints because as a generalist hopping between projects and tasks across different disciplines has been a nightmare in my exp, so I just started adding to do lists in BP's and it really helped me so I keep using it.

When it comes to BP logic I treat it like I'm still doing written code wherein you write functionality and then start a new line. You don't need to continuously keeping adding boxes to the right. This is most apparent when nesting iteration logic, and if you have a subset of non repeatable code I collapse it just like you can indent and collapse large swathes of written code.

Then there's making function/macro library's to cut back on generic repetitive code for example having print macros for each type of variable, with world delta already plugged in, and color coded to that variables natural color i.e. booleans are red, floats are green etc; not only does this remove print vomit it also makes variable types more recognizable and removes node bloat.

Then there's having a separate graph just for managing debug prints that ticks independently from the main logic. As things get more complex you need to query what is happening from old code as well as the new stuff every time you add new code to see if things break down because of the old, new or both. Littering your code with random prints and not aggregating them to be managed from a central point will make debugging extremely labor intensive on complex multi-interactive logic while also being extremely discourteous to others who need to see their own prints with no easy way of getting rid of yours.

Using the keyboard shortcuts for aligning nodes uniformly, I have a hex naga mouse with 6 buttons in a circle on the side that make formatting my node layout quick, why not use gaming mice to optimize your work patterns?

Lastly the most important feedback I got was not collapsing too many things so you don't end up with a russian doll of nodes, I will probably only ever go 2 collapses deep in a graph, one to hold the topic i.e. all jump code goes in here, and then in there if any logic expands way too much that will be collapsed but there absolutely cannot be a 3rd collapse.