Commands  ›  Clash Manager / Solver  ›  Clash Solver Connect Into Nearest Node By System Match

Clash Solver Connect Into Nearest Node By System Match

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

Coming soon

Before you run this

Active document; source resolvable; at least one candidate with matching system type in radius.

After it runs

Either one ConnectTo inside one Transaction or no change.

When to use this

Don't use this when

Cross-system connects — use the ConnectorOps 3D command directly with AllowCrossSystemWithWarning=true.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Validate element unique id.
2) Instantiate ConnectorOpsConnectIntoNearestNodeIn3dCommand, copy resolvers,
   set AllowCrossSystemWithWarning=false.
3) Inherit command runner (caller's Revit UIApplication).
4) Delegate Execute(); pipe its tracker outputs into this command's tracker.
5) No extra logic — this command is the strict-system wrapper.

What you'll see in the chat

on start
Connecting to nearest system-matched node…
thinking
Delegating to ConnectorOpsConnectIntoNearestNodeIn3dCommand with strict gate…
on success
Strict-system connect {connected}.
on failure
Strict-system 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_node_by_system_match
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

strict system connect · clash solver connect · in-system 3D connect · system match connect · no cross-system

PillarClash Manager / Solver