Connect SCPs to Desks

The Red Triangle Connection Mechanic

When you select a placed SCP or desk in build or management mode, red triangles appear on valid connection nodes. Click a triangle on the SCP, then click a matching triangle on a Lab Station desk to establish a research line. Successful links show visual pathways confirming data flow from containment to analysis station.

Triangles enforce directionality and compatibility. Not every desk accepts every SCP class until research unlocks. Euclid anomalies may require upgraded Lab Stations distinct from basic Safe setups. Attempting invalid connections produces no link—check research requirements on the SCP catalog entry.

Connections persist until you manually sever them or demolish linked structures. Rebuilding containment without reconnecting silently kills income until you notice empty revenue charts.

Scientists, Laptops, and Desk Roles

A connected desk still needs a assigned Scientist to run protocols. Hire Scientists from personnel menus and assign them to specific stations—not global auto-assign unless you accept inefficiency. Scientists without connections idle while paid.

Laptops on desks enable advanced monitoring and sometimes boost test throughput depending on beta patch state. Place laptop furnishings during desk setup so upgrades do not break triangle alignment. Moving desks after linking requires re-establishing triangles.

Class-D personnel execute physical test phases along the connection chain. Ensure pathing from Class-D quarters to linked SCPs stays secure and monitored. Long unsecured walks invite escapes that sever connections violently.

Routing Multiple SCPs

Mid-game facilities run parallel Safe tests for steady Money while one Euclid project ramps. Each SCP needs its own valid triangle path to an appropriately tiered desk. Sharing desks across incompatible classes fails or triggers breach modifiers—consult SCP class pages before consolidating.

Vertical layouts complicate routing. Multi-floor research hubs centralize Scientists but require elevator-aware pathing for Class-D. Keep triangle chains short; convoluted routes increase incident chance when riots break containment doors.

Server Rack research later multiplies income from all active connections. Maximize connected desks before investing in rack infrastructure to amplify returns.

Common Connection Mistakes

Placing containment adjacent to desks without clicking triangles leaves money on the table. Proximity alone does not connect. Forgetting Scientist assignment after linking is equally common—always verify both triangle glow and scientist icon on station UI.

Demolishing a single corridor tile can break triangle paths in non-obvious ways. After major renovations, audit every active SCP line. During beta, reconnect bugs occasionally appear after server hops; relog if tests stall despite visible links.

Connection Verification Checklist

Before declaring a wing operational, walk through five checks: containment tier matches SCP class, red triangles link SCP to desk, Scientist assigned and present, Class-D path secured, and test income appears in the ledger within one cycle. Skipping any step produces the illusion of progress without revenue.

Advanced directors label wings numerically in their mental map—Wing A Safe farm, Wing B Euclid project—to trace failures quickly. When income dips site-wide, compare wings instead of panic-demolishing random corridors.

Laptop upgrades shift triangle node positions slightly in some beta builds. After placing laptops, re-click connections even if lines looked valid before furnishing.

Teach friends joining your public server session this checklist before co-building. Split roles—one director handles triangles, another staffing—so multiplayer chaos does not break silent misconfigurations.

Record a thirty-second clip of a working triangle click sequence when you first connect an SCP—future you will reference it after beta UI moves buttons between patches.