Commands  ›  Clash Manager / Solver  ›  Clash Solver Connect Into Nearest Node2d By Revit Native

Clash Solver Connect Into Nearest Node2d By Revit Native

Clash Manager / Solver writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; source element resolvable; at least one candidate in 2D radius at same Z.

After it runs

Either one ConnectTo / NewElbowFitting or no change.

When to use this

Don't use this when

3D connects — use ConnectIntoNearestNodeBySystemMatch.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Validate element unique id.
2) Instantiate ConnectorOpsConnectIntoNearestNodeIn2dCommand, copy resolvers,
   set AllowCrossSystemWithWarning=false.
3) Delegate Execute.
4) Tag tracker with strict_system_match=true + delegated_to.

What you'll see in the chat

on start
Plan-view connect with strict system match…
thinking
Delegating to ConnectorOpsConnectIntoNearestNodeIn2dCommand…
on success
2D connect delegated, strict gate enforced.
on failure
Plan-view connect failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_solver_connect_into_nearest_node2d_by_revit_native
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverconnectintonearestnode2dbyrevitnative · 2d connect revit native · plan view strict connect

PillarClash Manager / Solver