Improve the blueprint organizer

[Nicopara]

Right now, I believe the biggest issue is that monolith produces unorganizable spaghetti nodes. Please add something to fix this and make it like how a human would produce the blueprint. Thank you for your time.

[Alexbeav]

Chasing this in the source turned up a coupling that is worth knowing before anyone attempts it, because the obvious fix is a silent regression.

add_node defaults to [0, 0] (MonolithBlueprintNodeActions.cpp, the position parse), which is the pile @Nicopara is describing. But that default is load-bearing: auto_layout's new_only mode uses it to decide what it is allowed to move.

// MonolithBlueprintLayoutActions.cpp
// Pin nodes that are NOT at (0,0) and NOT heavily overlapping
bool bAtOrigin = (Node->NodePosX == 0 && Node->NodePosY == 0);
LN.bPinned = !bAtOrigin;

So if add_node starts cascading placement, every new node becomes non-origin, therefore pinned, therefore never repositioned — auto_layout(layout_mode: "new_only") reports success and moves nothing. Placement and layout have to change together.

The comment already describes the fix that was never written. && NOT heavily overlapping is not implemented — only the origin test is. Making new_only mean "unpinned if it overlaps another node" rather than "unpinned if at origin" is robust to any placement scheme and frees add_node to cascade. The machinery is already there: EstimateNodeSize computes EstWidth/EstHeight (300 default, 50 + pins × 24, real values for comments) and FLayoutNode already carries OrigX/OrigY, so an overlap test is a rectangle intersection over data that is already gathered.

---

Separately, for anyone hitting this today: the spaghetti is avoidable from the caller side, and treating it as a discipline rather than a tool bug has worked well for us —

• Always pass position. Exec chain left→right at ~350-400px steps; pure data feeders ~250px left of and ~150-200px below their consumer; events/entries at x=0; parallel exec chains separated by ≥300px vertically. Node width is not readable through the API, so spacing is dead reckoning — err generous.
• Then run auto_layout with layout_mode: "new_only", which cleans exactly the pile-at-origin case without disturbing hand-placed nodes. formatter: "auto" prefers Blueprint Assist when installed and falls back to the built-in Sugiyama pass.

That gets readable graphs out of the current build. It does not remove the case for a better default, which is what this issue is really about — a first-time user should not have to know any of the above to avoid a node pile.