Official game
Play Ringwyrm
This game is hosted by Steam. Continue to the official page to play or download it.
Wishlist on SteamOverview
Ringwyrm is a first-person action horror game from solo developer Scumhead, whose previous game Mohrta landed at Very Positive (91% of 1,300+ reviews) in October 2025. Ringwyrm blends arcade FPS combat with survival mechanics, disease management, and a nonlinear narrative set in a grim, Soviet-tinged fantasy world. The studio's own pitch line doubles as the strategy thesis: as the horrors slowly boil, so will the player's power. You start weak, scared, and undergunned. The game escalates you alongside its threats.
It launches in 2027 on Steam for Windows. No demo date is confirmed, though the developer has said more intensive playtesting ahead of launch is the plan, and a demo or playtest window is likely. One structural fact matters before anything else: Ringwyrm runs on a GZDoom-family engine, which is why the store page lists no achievements and why the developer has said achievements are "very unlikely" to ever arrive. Your progress is the save file, nothing else.
Core identity: You cannot aim and move at the same time. Every shot counts. One questline will lock out all other endings and quests. This is not a game you blast through; it is one you survive.
Who it is for: Fans of methodical survival horror (classic Resident Evil), players of Mohrta and Dread Delusion, and anyone who liked the idea of STALKER's atmosphere inside a Morrowind-shaped world.
Who it is not for: Run-and-gun players, achievement hunters, and anyone who needs a Linux build. Native Linux support is not planned, a real break from Scumhead's earlier games (Shrine I/II, Vomitoreum, Lycanthorn II all shipped Linux builds). Proton will likely handle it given the engine family, but that is community expectation, not confirmation.
| Fact | Detail |
|---|---|
| Developer / Publisher | Scumhead (solo) |
| Genre | Action horror / survival FPS |
| Platform | Windows (no Linux build planned; partial Xbox controller support) |
| Release | 2027 (unreleased) |
| Price | To be announced |
| Players | Single-player only |
| Setting | Umbral Isle, 16 years after the Iron War |
| Key constraint | Cannot aim and move at the same time |
| Systems | Durability, disease, eldritch alignment, questline lockout, 30+ NPC questlines |
| Achievements | None planned (engine limitation, per developer) |
| Minimum specs | 2.4 GHz dual-core, 4 GB RAM, OpenGL 4.0 GPU, 4 GB storage |
Story and Setting
Sixteen years after Schovekia's defeat in the Iron War, the young nation of Nordin-Gotts learns that remnants of the defeated Schovek have migrated to the Umbral Isle, far to the north. There they found Milk, a strange, reality-altering arcane element that rapidly transformed their society and technology. You are Edna Gotts, a war orphan conscripted alongside your sisters for a military recon mission. The mission becomes an unending nightmare, and everyone, including the people who exploited Milk, learns what a mistake its use had been.
The developer has named the touchstones directly, and they read like a build guide for the game itself. Gameplay: Resident Evil 4, Ocarina of Time, Dark Souls, Morrowind, and STALKER. Aesthetics: oil paintings, Soviet film and animation (Tarkovsky and Lopushansky), Makoto Kobayashi, Kirkbride, Eastern European architecture. The hub city, banners and flying whales and all, is modeled on the Wawel Cathedral in Kraków. Literary influences: The Sparrow, The Road, the Strugatsky brothers, and the developer's own experience with chronic physical and mental illness. That last one explains the disease system's framing: illness in Ringwyrm is not a status bar, it is a condition you manage, fear, and plan around.
Core Mechanics Explained
The stand-still-to-aim system
Ringwyrm's defining constraint: aiming plants your feet. To move you lower the weapon. Hip-fire exists but spreads. This one rule rewrites every FPS habit you have.
| Scenario | Standard FPS reflex | Ringwyrm answer |
|---|---|---|
| Enemy rushing you | Backpedal and spray | Plant, fire once, sidestep during the recovery, repeat |
| Three enemies in a room | Kite in circles | Pre-clear from the doorway; pull one at a time |
| Boss fight | Circle-strafe forever | Learn the pattern, punish a window, reposition between windows |
| Tight corridor | Walk forward firing | Never enter un-cleared; use geometry so only one reaches you |
The tactical consequences stack. Positioning beats reflexes, because your firing position must exist before the enemy does. Damage per shot beats fire rate, because exposure time is the real cost. Sound beats sight, because infected announce themselves before they render. And every missed shot is doubled waste: the ammo and the extra second you stood still.
Equipment durability
Every weapon degrades. Fire enough rounds and guns jam, then break. The confirmed loop makes workbenches the strategic anchor points of the map; finding and mapping them is worth more than any single weapon pickup.
Four durability rules carry a run:
- Never enter a danger zone with one functioning weapon. Carry backup, even a bad backup.
- Repair early, not critically. Wear accelerates near the breaking point.
- Rot weapons, not just ammo. Scavenged guns exist to die so your good gun doesn't.
- Learn workbench locations before you need them. The run to a broken gun is when you meet every enemy between you and the bench.
The disease system
The titular Ringwyrm is the thing to avoid at all costs, and it is only the headline ailment. Contaminated zones, specific enemy attacks, and unsafe consumables all inflict conditions. The system is diegetic: symptoms are information, screen blur near an object marks that object as contaminated, and NPCs can cure specific diseases that supplies cannot.
Management framework:
- Carry medicine and antidotes into every unexplored area, no exceptions.
- Treat early. Stacked infections compound and early treatment is cheaper than cures.
- Rotate exposure. Leave contaminated zones to let timers reset rather than pushing through.
- Befriend medical NPCs. Some cures exist only through questlines.
- Read your own body. Symptoms are the game's contamination radar.
Eldritch alignment
Certain actions build alignment with the island's eldritch forces, producing strange stimuli: flickering lights, distorted sound, objects that move unobserved. Low alignment keeps NPCs trusting and conventional content accessible. High alignment unlocks unique endings, unique questlines, and content unavailable any other way, at the cost of how the world treats you and what your own senses report.
The game does not telegraph which choices shift alignment. That is deliberate. For a first playthrough, roleplay consistently, all resistance or all surrender, and let the run cohere. Optimization is for the second playthrough, with knowledge.
The questline lockout
One specific questline locks out all other endings and quests. Which one is not flagged, and other choices ripple through the 30+ NPC roster in ways the game rarely announces. Characters you helped early can survive or die hours later based on decisions you did not know were decisions.
Two practices follow. First, keep multiple save files from separate story beats, not just recent ones. Second, treat every conversation as a commitment. The game rewards intimacy with its setting, reading item descriptions, grabbing books off shelves, exhausting dialogue, but intimacy is not the same as generosity. Helping everyone is itself a build with its own failure modes.
Getting Started: First Session Plan
Ringwyrm has no classes. Your build is equipment plus alignment plus which NPCs still trust you. The first two hours set all three.
- Learn the stop-and-shoot rhythm in the opening area. Stop, aim, fire, move. Drill it on weak enemies until it is muscle memory. Every later death traces back to unlearning this.
- Loot everything. The opening teaches scarcity. Ammo, food, medicine, broken guns. Inventory space is a resource; being unable to pick up a cure is a death scheduled for later.
- Find and use the first workbench. Repair the starting weapon and internalize the maintenance loop before combat demands it.
- Exhaust every NPC conversation. Thirty-plus characters each carry questlines with evolving dialogue. Early connections pay off hours later, and the first conversation is the cheapest one to get right.
- Avoid skippable combat. Early resources are too tight to spend on fights that give nothing. Stealth and routing are free.
- Pick an alignment direction and commit. Mixed playthroughs produce muddled stories and locked content in both directions.
Progression Strategy
Phase 1: Initial recon (first hour)
Learn the rhythm, map the opening, find the first workbench, establish the NPC baseline, commit to alignment. Do not optimize anything yet; learn what the island costs.
Phase 2: Foothold (hours 2-4)
Complete the first major questline, which shapes which endings stay reachable. Unlock at least two shortcuts between zones for safe traversal. Stockpile disease treatments from medical NPCs. Take one permanent upgrade, health or stamina by taste. Gauge which way your early choices are pushing alignment.
Phase 3: Consolidation (hours 5-10)
Specialize the loadout: two weapons maintained and upgraded, not five half-broken ones. Recruit at least one NPC companion; a companion makes stand-still aiming dramatically safer by holding attention. Clear contaminated zones from least to most severe, building resistance as you go. Explore off the critical path; the best gear hides in optional areas. Maintain save files per story beat.
Phase 4: Endgame (hours 10+)
Identify which ending is still reachable before investing in the final push. Max the primary weapon's durability; final areas restrict workbench access. Stack disease resistance for the late-game contaminated zones. Complete remaining NPC questlines tied to your intended ending. Save before every major choice, because the game will not warn you.
Builds and Loadout Philosophy
Specific weapon lists arrive with the game, but the confirmed systems define what "best" means. The evaluation table:
| Priority | Stat | Why |
|---|---|---|
| 1 | Damage per shot | Fewer shots = fewer stationary seconds = less exposure |
| 2 | Accuracy | Missed rounds waste durability and time |
| 3 | Durability and repair ease | A jammed gun in a horde is fatal |
| 4 | Ammo economy | Scarcity punishes wasted fire |
Three loadout archetypes follow from the systems:
The Gunslinger. Precision firearms, headshots, minimal stationary time. Rewards players who trust their aim. Weakness: durability pressure from constant firing, and ammo dependence.
The Survivor. Health, disease resistance, healing stockpile. Wins by attrition and tolerates mistakes the other builds cannot. Weakness: slower kills mean longer exposure per fight.
The Scholar. Exploration, NPC depth, lore. Unlocks shortcuts, secret areas, and ending access the other builds never see. Weakness: less combat margin; wrong choices compound.
Best-in-slot reasoning: the best weapon is not the highest damage-per-second on paper. It is the gun that kills what must die in the fewest stationary shots while its ammunition stays sustainable. In this combat model a precise, ammo-efficient rifle outranks a high-RPM sprayer almost always, because every second standing still is a second you can be swarmed.
Step-by-Step Strategy
Sequence 1: Clearing a room under stop-and-shoot rules
- Stop at the doorway and listen. Enemy audio tells you the count and type before you see them.
- Pre-clear from the threshold: fire at the nearest threat the moment a sightline opens, then retreat a step.
- Reposition to a choke point where enemies must approach one at a time.
- Plant, fire, sidestep. Repeat per enemy. The sidestep after each shot is the whole technique.
- Loot only after the room is confirmed empty. Never loot mid-fight; the animation is a death sentence.
Sequence 2: Surviving a horde on limited ammo
- Identify the bottleneck the moment the horde spawns; geography is your only ally.
- Let them stack into a line. Highest damage-per-shot weapon, one kill per trigger pull.
- When they close, melee stagger the lead enemy. The stagger buys the reload.
- Fall back through a doorway and re-clear. Narrow geometry turns a horde into a queue.
- Leave the loot until the last body drops. Hordes and greed kills are the same kill.
Sequence 3: The disease resistance loop
- Establish a safe zone as the rotating home base.
- Before entering a contaminated zone: medicine carried, one inventory slot empty.
- Clear the least contaminated areas first; resistance builds with survived exposure.
- Symptom appears? Return immediately. Pushing deeper converts a treatment cost into a cure cost.
- Exhaust medical NPC dialogue every visit. Their cures exceed their shop inventory.
Sequence 4: Managing the alignment branch
- Commit during the first major questline.
- Log every choice you suspect shifts alignment, in a real notebook or a mirrored save.
- Never mix resist and embrace choices in one run if you want a coherent ending.
- Keep a fallback save before the suspected branch point.
- Accept that the first run is for coherence, not completion. Both alignment paths hide content the other cannot reach.
Sequence 5: NPC questline triage
- After each conversation, note what the character wants and what they fear. Questlines hang on those two hooks.
- Help characters whose goals align with your route; detours for strangers cost supplies.
- Revisit NPCs after major story beats. Evolving dialogue is where follow-up quests hide.
- Watch for characters who mention each other. The roster interlinks; one questline often unlocks another's next stage.
- Before the point of no return, walk the full hub. Every face you never talked to is an ending you locked.
Sequence 6: Final zone preparation
- Confirm the reachable ending from quest state and alignment before the push.
- Repair the primary weapon to ceiling; carry the backup repaired too.
- Fill medicine and resistance consumables to capacity.
- Complete remaining questlines tied to the intended ending; missed quests are missed endings.
- Save, then commit. The final area limits workbench access, so what you carry is what you have.
Advanced Tips
- Sound is the primary sense. Infected types make distinct noises. Learn the vocabulary and you will see through walls.
- The hip-fire reticle tightens if you stand still a beat. Snap shots between full aims are the middle gear most players never use.
- Symptoms are radar. Blur near an object means contamination. Fear is data.
- NPCs remember everything. A betrayal in hour two has consequences in hour twelve. Treat every interaction as permanent, because it is.
- Books and item descriptions are manuals, not flavor. Weakness hints, cache locations, and shortcut triggers live in text the impatient player skips.
- Melee is a resource tool. A stagger converts to distance, and distance converts to a reload. Ammo-free.
- Alignment accumulates silently. Small choices push it. There is no meter to watch, only patterns to notice: if the lights flicker more, you are leaning eldritch.
- A zone that feels too hard is under-leveled routing, not under-leveled stats. The nonlinear map lets you walk into endgame areas early. Leave, explore elsewhere, return.
- Save names are strategy. Name saves by story beat, not timestamp. "Before hospital choice" beats "save 27" at hour twelve.
What We Know About the Threats
Enemy specifics are unconfirmed before release, but the store copy and the developer's inspirations define the design space. Otherworldly infected beings haunt every corner of the map. The Resident Evil 4 and Dark Souls lineage implies enemies built to punish greedy positioning, with encounter design around arenas and sightlines rather than raw numbers. The STALKER lineage implies environmental hazards and anomaly zones that damage the unwary regardless of combat skill. And the disease system implies at least one enemy category whose real weapon is the condition it leaves you with.
| Threat category | Expected behavior | Counter-strategy |
|---|---|---|
| Basic infected | Rush and melee | Headshot, stagger, conserve ammo |
| Ranged threats | Projectiles from distance | Break line of sight, close carefully |
| Contaminating enemies | Leave disease on hit or in an aura | Kill at range, never melee |
| Armored/durable | Slow, heavy damage | Weak points, best weapon only |
| Bosses | Unique patterns | Study telegraphs, punish openings, reposition between |
Similar Games Reference
| Game | Shared DNA with Ringwyrm |
|---|---|
| Resident Evil 4 | Named inspiration; methodical combat, resource tension |
| Morrowind | Named inspiration; nonlinear world, strange NPCs, text-driven depth |
| Dark Souls | Named inspiration; consequence-heavy world, punish-and-reward pacing |
| Ocarina of Time | Named inspiration; hub-and-region world structure |
| STALKER | Named inspiration; atmosphere, contamination, anomaly zones |
| Pathologic | Disease as a system, grim Slavic atmosphere, impossible choices |
| Mohrta | Same developer; creature design, uncompromising old-school structure |
| Dread Delusion | Community-pointed; lo-fi world with outsized atmosphere |
FAQ
When does Ringwyrm release? 2027 on Steam. The developer has pointed at a late-2027 window. No specific date.
Will there be a demo or playtest? The developer plans more intensive playtesting ahead of launch, and a demo or test phase is likely. Nothing scheduled yet.
What platforms? Windows at launch, with partial Xbox controller support. No native Linux build is planned, a change from Scumhead's earlier games. Proton likely works given the engine, but that is expectation, not confirmation.
Are there achievements? None planned. The developer has said they appear impossible on the current engine and would be added only if that changes. Your save file is the only record.
Is there multiplayer? No. Single-player only.
How long is the game? Unknown. Mohrta ran roughly ten hours; Ringwyrm's branching structure, alignment content, and the questline lockout point to multiple playthroughs for full coverage.
Is Ringwyrm connected to Mohrta? No. New IP, separate universe, same design philosophy.
Can I play it on Steam Deck? Not confirmed. The low minimum specs (OpenGL 4.0, 4 GB RAM) suggest the hardware handles it, and the engine family has a good Proton track record. Community is hopeful; nobody has promised anything.
What is Milk? The reality-altering arcane element found on the Umbral Isle. It transformed Schovek society rapidly and catastrophically. It is the reason the island is what it is.
Is the game out? No. Everything above is strategy planning grounded in official store copy, developer statements, and confirmed systems. The guide gets verified against the final build after launch.
Final Tips
Ringwyrm is a game about restraint. You cannot run and gun, so you think before you shoot. You cannot help everyone, so you choose whom. You cannot see every ending, so you commit to one and let the others stay locked. The systems all push the same direction: patience, positioning, and intimacy with a hostile world. Learn the stop-and-shoot rhythm, map the workbenches, carry the medicine, exhaust the dialogue, and keep fallback saves, because one questline locks out everything else. Wishlist it, watch for the playtest, and go in prepared when the Umbral Isle opens in 2027.
Last reviewed by Game How To Editorial. We research each game against official sources and developer statements. Ringwyrm is unreleased; mechanics marked as planning frameworks will be verified against the final build and this guide revisited after launch.






