Mainframe Puzzle Guide: Tips & Steps

Work through the DERELIKT mainframe puzzle with a practical checklist, dialogue tactics, and puzzle-solving habits for the retro sci-fi horror shooter.

The DERELIKT mainframe puzzle is the kind of obstacle that stalls a run cold: a station system that will not cooperate, strange threats somewhere in the dark, and no obvious hint about what the terminal expects. It matters because this is a survival horror shooter first — supplies are thin and station systems gate your route deeper into the carcass. Below is a practical way to approach the DERELIKT mainframe puzzle, what the game's public material actually confirms, and the habits that keep a locked terminal from ending your expedition.

What We Know About the DERELIKT Mainframe Puzzle

Start with the setting, because it shapes every puzzle in the game. You are a one-person expedition sent into the remains of an enormous space creature discovered in orbit around Saturn. A research outpost was grafted onto its exterior years ago, and the scientists living there are nervous, paranoid, and oddly preoccupied with something they call "the old song." Your security weapon gets handed over, and a service elevator takes you down into ancient bone.

That context matters for puzzles. This is not a shooter with a puzzle minigame stapled on; searching, solving, and questioning people are listed as core parts of the loop alongside fighting.

DetailWhat it means for you
DeveloperVisuwyg, working as art director
PublisherHyperstrange
GenreRetro first-person shooter, sci-fi survival horror
PlatformPC (Steam)
SettingResearch outpost grafted onto a colossal creature's carcass in Saturn orbit
Core loopSearch for supplies, solve puzzles, fight threats, question survivors
DialogueBranching dialogue trees with NPCs
Visual styleAffine texture warping, dithering, animated textures, hand-painted vertex colors
InfluencesAlien Resurrection (PS1, 2000), Doom 3 (PC, 2004), cosmic horror

One honest caveat before you sink an hour into one door: publicly available material about the game confirms puzzles exist and that branching dialogue is a real, developed system, but it does not publish a step-by-step answer for a mainframe-style lock. So the rest of this guide teaches method — where clues live, what to write down, and how to stop looping.

If you want the atmosphere and the exact framing in the developer's own words, the official project page lays out the story setup and the PS1-style rendering work.

Prep Work Before You Touch the Terminal

Most puzzle frustration is a preparation problem. Before you commit to a locked system, make the room safe and gather everything the station is willing to tell you.

StepWhy it matters
Clear the immediate areaYou cannot read logs while something is chewing on you
Read the terminal text twiceSystem messages often restate the requirement in plain language
Sweep for notes and posted numbersSupply lists, shift logs, and memos are the usual hiding places
Re-talk to every scientistDialogue trees unlock new branches after you find items or rooms
Save before entering anythingA wrong entry should cost you seconds, not a run
Write clues in a real notepadThe station's clues are text, and text is easy to misremember

Treat the search for supplies and puzzle clues as the same activity aboard the failing outpost — the station's survival loop is built around scavenging, problem-solving, and reading the people around you.

The two-minute room sweep

Walk the perimeter, then the center. Check consoles, wall panels, desks, and anything with a screen. If a room contains a locked terminal, assume the same room or the hallway outside contains at least one readable clue. That single habit solves more locks than any guessing.

Reading the Room: Clues the Station Gives You

The mainframe puzzle will not ask you for information you have never seen. It will ask you for information you walked past. Train yourself to notice these categories:

  • Numbers on screens and notes — dates, unit designations, sequence labels, partial codes.
  • Repeated phrases — when dialogue circles back to one idea, the game is pointing at it.
  • Logged entries from staff — scientists under stress write things down, and their notes travel further than they do.
  • Environmental ordering — labeled doors, numbered bays, and directional signage often mirror the order a system wants.
  • Contradictions — a survivor who insists everything is fine is telling you where to look next.

The "old song" problem

The outpost's residents describe the old song working its way into their heads. Whether that motif feeds directly into a specific lock is not documented, but the practical lesson holds: in a game built on paranoia and unreliable narrators, dialogue is evidence. Listen for the phrasing people repeat and check whether it matches anything on a wall.

Dialogue Is Your Best Puzzle Tool

Branching dialogue trees are a confirmed feature, contributed as a system in its own right rather than as flavor text. That means conversations have depth, and depth is where puzzle answers hide.

Conversation approachWhat you gain
Ask about the outpost's systemsNaming a system often reveals how it is controlled
Press on odd phrasingRepeated or defensive answers flag a topic worth returning to
Return after every new roomNew items and discoveries open new branches
Ask about other survivorsMotives and grudges explain locked doors and missing access
Leave a topic and come backSome lines only surface once a conversation resets

Do not sprint through dialogue hoping for a combat break. In a horror game with cosmic-leaning writing, the unsettling conversation usually is the hint.

Keep a short question list

Before you re-enter a conversation, decide what you actually need: a name, a number, a location, or an explanation for why a system was shut down. Ask for that thing. Vague wandering through dialogue trees is how players burn twenty minutes and retain nothing.

Habits That Crack Station Puzzles

The DERELIKT mainframe puzzle rewards patience over reflexes. These habits apply to any terminal, panel, or access gate you meet.

HabitWhat it doesWhen to use it
Restate the puzzle in one sentenceForces you to name the actual requirementThe moment you see the lock
List what you haveTurns inventory into candidate answersAfter a failed attempt
Try the obvious answer firstSaves time on simple gatesBefore deep searching
Change one variable at a timeIsolates what the system wantsMulti-part entries
Step away and exploreNew rooms supply new cluesAfter two or three failures
Re-read your notesCatches transcription mistakesWhen nothing you try works

How to stop looping

Set a hard limit: three serious attempts, then walk away. Come back with more supplies, more rooms explored, and more dialogue heard. The pattern in this genre is almost always that the answer lived in a room you skipped, not in a code you misheard.

Most failed attempts at the DERELIKT mainframe puzzle come down to one of a few predictable errors, and all of them are fixable.

MistakeThe fix
Entering codes without savingSave first, always
Ignoring written notesRead every readable object in the room and the hall
Treating NPCs as sceneryUse the dialogue trees for information, not just story
Charging in under-suppliedScavenge before you commit to a locked section
Assuming a bugRule out a missed clue first; the game is still in development, so builds change
Forgetting what a screen saidNote it the second you read it

When Nothing Works: Honest Next Steps

There is a real possibility that a specific mainframe puzzle has no published answer yet. The game is still in development, published by Hyperstrange, and its public materials focus on atmosphere, rendering technique, and story rather than walkthrough-level detail. That is a limitation of the available information, not a reflection of your play.

In that situation, do this in order: clear the current floor for notes, exhaust dialogue branches with every survivor, check whether a supply item doubles as a clue, save and test one careful theory, then move on and come back later. Progress in a horror shooter is often gated by exploration rather than by cleverness.

FAQ

Is there an official solution to the DERELIKT mainframe puzzle? Not one that has been published. Public materials describe puzzles as part of the core loop and confirm branching dialogue, but they do not provide a step-by-step solution. Work from in-game clues rather than outside answers.

Do I need to write down a code for the DERELIKT mainframe puzzle? Yes, treat any number you see as potentially important. Station logs, memos, and screen text are the natural hiding places for the details a locked system wants.

Can I brute-force the DERELIKT mainframe puzzle? Not reliably. Guessing burns time you could spend scavenging, and the answer is usually sitting in a room you have already visited. Sweep, read, talk, then test one theory at a time.

Does talking to NPCs actually help with the DERELIKT mainframe puzzle? Dialogue is one of the strongest tools you have. Branching conversations reveal the outpost's systems, the motives of its nervous residents, and the repeated phrasing that points at the truth. Return to survivors after every discovery.