The short answer: SCP – Containment Breach (April 15, 2012) was built by Finnish developer Joonas Regalis Rikkonen in Blitz3D, not Unity, Unreal, or Godot. That dead BASIC engine choice shaped everything from the blink meter to the game's decade-long mod afterlife.
The infobox lists it plainly: original author Joonas Regalis Rikkonen, developer Undertow Games, release April 15, 2012, final release 1.3.11 on August 19, 2018, written in Blitz3D with early versions in BlitzMax, engine Blitz3D, Windows XP and later, 235.53 MB, requirements 1.2 GHz, 256 MB RAM, 300 MB storage, license CC BY-SA 3.0 Wikipedia — SCP – Containment Breach. The public repo still states the build requirement as Blitz3D v1.108 and jokes that the source code is perhaps more horrifying than the game itself GitHub — Regalis11/scpcb.
This article explains what Blitz3D actually is, why it fit a solo SCP game, and what I think most engine debates miss about blinking as a mechanic.
Who this is for
You are an indie or hobbyist developer choosing a low-cost 3D path, or a technically curious horror player wondering why a 2012 free game still feels tense on a toaster. You do not need to know BASIC. You do need to care about shipping scope: one developer, a free license, a procedurally generated facility, and monsters that punish looking away.
Scope as verified in November 2026: single-player indie survival horror based on the SCP Foundation collaborative writing project. You play Class-D test subject D-9341 in a covert containment facility. A system failure releases the anomalies. You must escape through Gate A or Gate B across four endings while managing blink, sprint, inventory, keycards, and documents.
What Blitz3D actually is — and how niche it is
Blitz BASIC is a BASIC dialect devised by Mark Sibly, designed to be easy for beginners, game-oriented, with dialects including Blitz2D, Blitz3D, BlitzPlus, BlitzMax, and AmiBlitz. Windows Blitz Basic shipped in October 2000 with built-in 2D graphics and audio on 200 MHz and 32 MB RAM. Blitz was shelved commercially around 2015 and released as free and open-source software.
In other words: a 2000s hobbyist BASIC with direct DirectX 7-era calls, no editor, no asset store, no modern console pipeline. By 2012 it was already unfashionable next to Unity 4 and UDK. Rikkonen chose it explicitly for simplicity and familiarity after his smaller SCP-087-B prototype gained traction Wikipedia — SCP – Containment Breach.
How niche? Google suggestions today still include scp containment breach what engine, what engine does scp containment breach use, and scp containment breach game engine, while Bing adds what engine does scp containment breach use and scp containment breach engine. Players are not just asking how to survive SCP-173. They are asking what forgotten tool made it possible.
Why BASIC fit a containment facility
Rikkonen focused on atmosphere through environmental design, sound, random map generation, and randomized events to keep tension unpredictable Wikipedia — SCP – Containment Breach. Blitz3D mapped almost 1:1 to that goal:
Rooms as code, not levels. The facility layout is procedurally generated each playthrough via seed generation. In Blitz3D that is straightforward: spawn prefabricated room meshes, connect with doors, scatter keycards and documents. No lightmap bake, no navmesh rebuild fight. For a game where disorientation is the point, generation beats hand-authoring.
Blink as a global timer. The first-person game has a blink meter that depletes and forces blinking at intervals. SCP-173 can only move when not in your line of sight; if you blink or look away it advances rapidly and kills if close. In Blitz3D BASIC that is a few lines: decrement meter, trigger overlay, allow SCP-173 pathing when overlay active or camera dot-product fails. A modern engine would add post-processing and animation graphs. BASIC made it a counter.
Permadeath as save theology. Three difficulties structure saving: Safe allows save anywhere, Euclid only at designated points, Keter forbids saving except Save & Quit with permadeath Wikipedia — SCP – Containment Breach. In-universe documents explain respawn via memory erasure and the Spiral Gestalt. That is not lore decoration. It is a tool-native solution: when your engine has no cloud save or checkpoint system, you turn save rules into difficulty and fiction.
The game equips you with facility gear, SCP objects, documents, keycards, and terminals that reveal the Chaos Insurgency double agents, SCP-106's pocket dimension, and SCP-079's takeover of facility systems. All of that is readable text and inventory flags — exactly what BASIC handles well.
My analysis: horror is a blinking problem, not a graphics problem
Here is where verified facts end and my own reading begins. I label it clearly.
Verified: Office-free roaming, defenseless Class-D, blink meter, SCP-173 line-of-sight kill, SCP-096, SCP-106, Nine-Tailed Fox squad, keycard gating, four Gate A/B endings including nuclear detonation against SCP-682.
My take: Most horror postmortems talk about ray tracing or photogrammetry. Containment Breach proves the scariest renderer is your own eyelid.
Blinking does three jobs at once that no shader can:
- It is a render cull you cannot disable. Every few seconds the game blinds you by design. You pay attention to afford attention.
- It is an anti-AFK mechanic. Campers who stare at SCP-173 forever are forced to look away. Safety expires.
- It is a fairness contract. Unlike random jumpscares, the rule never changes: if you did not see it move, you know why you died.
My provocation: Containment Breach is less like Resident Evil and more like trying to read in a windstorm. Unity horror templates default to hide-and-seek in detailed 3D. Blitz3D defaulted to look-and-lose in blocky corridors. If you are designing horror, ask: what involuntary body function can I tax? One taxed blink creates more dread than 4K textures.
Second divergent idea: a dead engine is containment itself. Blitz3D was abandoned commercially around 2015, open-sourced, frozen at v1.108. The facility in-game is also abandoned, frozen, running on old systems taken over by SCP-079. Players feel that match even if they cannot name it. Jank becomes lore. Low-poly concrete, humming fluorescents, and stuttering doors read as Foundation brutalism, not low budget. What would your game feel like if you were forbidden from updating your tool?
Open questions I cannot resolve from public sources: exact tick rate for SCP-173 advancement per blink frame, whether seed generation reseeds mid-run after Gate A, and how 1.3.11 preserves timing on Windows 11 vs XP-era DirectX. Those need source dives. I leave them open — they are good modding prompts, which is why scp containment breach mod db and version-specific downloads persist in suggestions.
Moddability as survival, not feature
The game and source are licensed CC BY-SA 3.0 except SCP-173, with the repo public GitHub — Regalis11/scpcb. BASIC source is readable. The result is a decade of forks: SCP – Containment Breach Unity remake, multiplayer mods, Ultimate Edition, custom SCPs.
This is not a footnote. It is a survival loop: kids who cannot afford Unity Pro can open a .bb file, swap a room, add an SCP, post a build, and drive attention back to the SCP Wiki. Unity games can be modded, but IL2CPP and AssetBundles raise the bar. Containment Breach lowered it to editing BASIC.
My question for you: did Rikkonen choose Blitz3D because it was forkable, or did forkability emerge and then preserve the game after final release in 2018? I suspect the latter, and that is the lesson. Pick a stack your community can maintain after you stop. If your engine requires a subscription, NDA, or proprietary bundle, you are taxing your archivists. Blitz3D taxed nothing, so the internet kept the facility open.
Try the pressure in a browser (no download)
You do not need to install the 235 MB build to train the three skills it rewards: door discipline, sound listening, and room search. These free browser games isolate one each:
If you miss containment doors and keycard gating, play Doors Castle. Every locked, trapped, or safe door in a haunted fortress forces the same question Containment Breach asks constantly: do I open this now or explore elsewhere first? Limited light, listening for footsteps, and remembering dead ends train the exact paranoia of facility navigation without any download.
For SCP-173-style sound-driven stalking turned up, play Evil Neighbor 3. A sinister neighbor stalks halls and reacts to sound and movement, item locations shift, and rushing is ringing a dinner bell. The lesson transfers directly: move in layers, keep a safe line to a hiding spot, and never loot without an exit plan — the same discipline as breaking line-of-sight cleanly before blinking.
If you want to practice document-and-key search under pressure, play Escape or Die 3. You search drawers, boxes, and patterns to solve riddles and escape. Treat each drawer as a containment file: check, do not commit, keep an exit in mind. It separates search patience from monster pressure so the original's keycard loop reads clearer when you return.
None clone SCP. They separate doors, stalking, and search so the facility design reads clearer when you return.
What to steal (and what not to copy)
Steal this if you are solo or small:
- Choose boring tech that removes rendering debates. No PBR, no netcode, no store. Blitz3D removed the excuse to polish.
- Make the body a resource. One blink meter every system touches beats five hidden cooldowns.
- Ship procedural disorientation. Seed generation gives replay without more art.
- Keep source readable. Future modders are future maintainers.
Do not romanticize:
- Blitz3D gives you Windows-only, single-threaded DirectX 7-era 3D, no modern debugger, and frame logic that tangles past large maps. The 1.2 GHz / 256 MB minimum is charming until you port.
- BASIC typing hides errors until runtime. What is joyful at 5,000 lines is fragile at 50,000 — the repo joke about horrifying source is honest.
- Blink fairness needs transparency. Without a visible meter and audio cue, players call it unfair. UI is trust.
Verdict
SCP – Containment Breach did not succeed despite Blitz3D. It succeeded because a dead, simple BASIC let one developer iterate on rooms, blink, and saves without fighting an engine built for someone else's shooter. The store description for the idea is still a test subject navigating a facility that lost control of its anomalies Wikipedia — SCP – Containment Breach — that loss of control is engineering as much as fiction.
If you are starting a horror prototype in 2026, ask the SCP question: what can I delete? If the answer is the editor, the graphics race, and half your save system, BASIC-style constraints still deserve a prototype weekend — even if you later port to Godot or Unity for consoles.
What involuntary cost would make your game scarier if watching it drained you? I do not have a rigorous answer. I think the question is more useful than any benchmark.
Sources and verification date
Core facts verified November 12, 2026 via direct retrieval (Wikipedia SCP – Containment Breach + Blitz BASIC, GitHub scpcb, EasyHub game pages). Analysis and provocations are my own and labeled as such.
- Engine, release dates, dev, size, requirements, and facility loop
- Blitz BASIC beginner BASIC lineage and open-source status
- Blitz3D v1.108 requirement and CC BY-SA licensing
- Browser-trainer descriptions from EasyHub Doors Castle, Evil Neighbor 3, and Escape or Die 3
Top comments (0)