Updated July 2026
Map & Facility Zones
SCP Architect X does not ship a single static world map like an open-world RPG. Instead, players construct modular facility zones on buildable tiles while accessing separate wilderness spaces for Euclid capture missions. Understanding this spatial split prevents costly layout mistakes—confusing interior grid planning with exterior capture routes wastes research unlocks and staff time.
Foundation Core and Build Grid
Your foundation occupies a expandable grid where tiles accept floors, walls, SCP chambers, desks, amenities, and utility objects. Power routing implicitly defines viable zones; chambers placed far from power backbones require extensions that consume build budget. Treat the core as concentric rings: utility and staff amenities near the center, SCP wings radiating outward, security checkpoints at wing entrances.
Multi-floor research stacks grids vertically with stair or elevator connections depending on beta build features. Each floor needs independent amenity coverage under NPC needs rules—single cafeteria on floor one does not satisfy floor three scientists. Map planning should sketch vertical amenity pairs before placing SCPs upstairs.
Foundation management UI maps logical zones even if the visual build view lacks labels. Mentally divide areas: testing wings, staff quarters, security posts, and utility clutter zones for generators or racks.
Support Wings and Service Corridors
Support zones house medbays, cafeterias, restrooms, maintenance closets, and security stations. Corridor width affects riot propagation—narrow hallways channel Class-D unrest directly into SCP chambers. Service corridors should bypass public test observation paths where possible.
Personnel type dictates zone adjacency: doctors near medbays, maintenance near high cleanliness-loss furnishings, security near Class-D dorm areas. Item pages list furnishing costs to budget wing sizes before opening build mode.
Decorative VIP furnishings from 2026 packs alter aesthetics without changing zone logic. Place cosmetics after functional zoning works; repainting before planning causes rework when amenities must squeeze into tight tiles.
Wilderness and Euclid Capture Areas
Wilderness spaces exist outside the primary facility grid for Euclid retrieval gameplay. Access requires research unlocks and equipped staff teams. Capture attempts consume session time away from idle test income—schedule them during stable facility periods, not during active riots.
Route planning matters: after capture, entities transit through holding infrastructure before reaching test chambers. Missing holding tiles forces improvised paths that breach more often under beta pathfinding edge cases. Consult the Euclid capture guide for squad loadouts.
The wilderness is not ideal for permanent base building in current beta iterations. Treat it as a mission instance tied to progression rather than a second city to decorate.
- Interior grid: SCP wings, desks, power, amenities
- Vertical stacks: per-floor amenities and security
- Wilderness: Euclid capture missions post-research
- Checkpoints: isolate high-risk anomalies
Map Planning Tips
Screenshot top-down views after each major expansion. Beta patches rarely wipe saves but frequently nudge object sizes or door behaviors—documentation speeds rebuilds.
Use the facility checklist tool to verify zones before unlocking expensive research. Mark medbay, security, and cafeteria coverage per floor explicitly.
When visiting multiplayer servers, observe how top players separate Safe and Euclid wings. Copy principles, not exact dimensions—tile unlock counts differ by save progression.
Frequently Asked Questions
Is there one official map image for the whole game?
No single static map covers both your custom facility and wilderness instances. Planning is player-generated on the build grid.
Where do Euclid captures happen?
In wilderness mission areas accessible after relevant research, separate from your main facility tile grid.
How big can my facility grow?
Growth depends on unlocked floors, tile research, and performance limits. Very large builds may lag on low-end devices.
Should Safe and Euclid SCPs share wings?
Avoid shared hallways when possible. Isolated wings reduce chain breach damage and simplify security staffing.