Updated July 2026
Capture Euclid SCPs
Euclid-class anomalies in SCP Architect X are not always bought from a menu. Many require wilderness capture missions outside your primary facility footprint—tracking anomalies in exterior zones, securing them for transport, and integrating them into researched Euclid containment cells. This guide covers unlock prerequisites, team composition, capture UI flow, and post-capture connection steps so new Euclid investments pay off instead of becoming breach statistics.
Prerequisites Before Hunting
Unlock Euclid research in the Research Tree for approximately 40,000 before attempting captures. Without the unlock, wilderness interactions remain disabled or fail silently. Pair the research with appropriate containment chambers and upgraded Lab Stations—capturing an Euclid you cannot house forces release or breach scenarios.
Assign Security and ideally Task Force escorts for capture teams. Scientists identify targets in the field but do not tank anomaly effects. Class-D may participate in bait roles depending on mission type—budget for morale hits and post-mission Medbay care.
Stock Money reserves for capture consumables and emergency rebuilds. Failed captures damage equipment and staff, creating hidden costs beyond the catalog price of the SCP itself.
Wilderness Zones and Map Navigation
The facility map includes exterior wilderness areas where roaming Euclid candidates spawn during beta events or persistent cycles. Open the map overlay from management UI and filter for capture-eligible icons. Travel paths from your main gate to wilderness entry points should be secured to prevent unrelated riots during expeditions.
Multi-floor directors: ensure ground-level egress remains staffed while teams are abroad. Empty Security coverage at home invites Class-D incidents while you hunt externally.
Some anomalies rotate seasonally with beta patches—verify target availability on Discord when pursuing specific high-income Euclids.
Capture Mechanics Step by Step
Initiate capture mode from the wilderness interaction prompt when your team reaches the anomaly. Mini-games or progress bars vary by SCP—follow on-screen instructions without skipping tutorial callouts added in recent beta updates. Interruption from disconnects may reset progress, so capture on stable servers.
Successful captures transition to transport phase. Route back to your facility along monitored corridors. Dropping containment mid-transport releases the SCP into your hallways—essentially a self-inflicted breach.
Place the anomaly directly into a prepared Euclid cell before running tests. Connect red triangles to staffed desks only after doors seal and Security posts are active.
Some Euclids resist capture if your team lacks minimum Security rating—hire additional guards or bring Task Force before repeating failed attempts that injure staff without payoff.
After Capture: Integration and Profit
Treat first Euclid tests as calibration runs with reduced intensity. Push throughput only after happiness and Security metrics remain green across a full shift cycle. Integrate capture income with Server Rack multipliers once your research tree supports passive scaling.
Link capture planning with research progression order so you never capture more Euclids than your staff can manage. One successful capture beats three rushed failures.
Recommended Capture Team Composition
Minimum viable teams include two Security, one Scientist, and optional Class-D support depending on target behavior. Task Force escorts replace standard Security when capturing higher-threat Euclids flagged with skull icons on the wilderness map.
Doctors waiting inside the facility—not in the field—stabilize teams returning with injuries. Pre-position Medbay access near entrance airlocks to shorten recovery downtime between capture attempts.
Capture during low-riot periods when Class-D happiness is green site-wide. Launching expeditions while home morale is amber invites simultaneous domestic riots and wilderness failures.
Wilderness weather or beta event modifiers occasionally boost capture difficulty—check event banners before spending transport consumables on a timed mission.
Label captured SCP cells on your map the day they arrive—directors running multiple Euclid projects lose track of which desk pairs with which anomaly after transport adrenaline fades.
Return routes from wilderness should mirror outbound security coverage—shortcuts through unpatrolled tunnels cause transport breaches even after successful captures.
Never run capture missions during active home riots—the wilderness timer does not pause domestic emergencies.
Frequently Asked Questions
When can I start capturing Euclid SCPs?
After unlocking Euclid research (~40,000) and building appropriate containment plus Security/Task Force support.
Where are wilderness capture zones?
Exterior map areas outside the main facility, marked on the management map during beta.
Can I capture Keter-class SCPs in the wilderness?
Keter requires separate late-game research near 500,000 and is not recommended until Euclid operations are stable.
What happens if capture fails?
Staff injuries, equipment damage, and possible partial breaches near the capture site—budget reserves accordingly.
Do captured SCPs need reconnecting after server hop?
Connections usually persist, but verify triangle links and Scientist assignments after major beta updates or disconnects.