.png?1726587305){kind=logo}
You’ve seen the screenshots. The low-poly, grimy aesthetic of the Tulpar. The way the light hits the decaying corridors. It’s a vibe that feels like a lost PlayStation 1 game found in a dumpster behind a derelict freighter. When players first start asking what engine was Mouthwashing made in, they usually expect to hear "Unity" or maybe "Unreal." It’s the standard answer for almost every indie hit these days. But Mouthwashing is different.
Wrong.
The game was actually built using the Godot Engine.
It’s an interesting choice for a psychological horror game that managed to capture the internet's collective nightmares in 2024. Most developers reach for Unity because of the massive asset stores or Unreal for that high-fidelity shine. Wrong Organ, the developers behind Mouthwashing, went a different route. They stuck with Godot, an open-source engine that has been gaining massive traction among indie devs who are tired of the corporate licensing drama surrounding bigger platforms.
Honestly, the engine choice is exactly why the game feels so distinct. There’s a specific "Godot look" when it comes to 3D—a certain way the engine handles lighting and textures—that lends itself perfectly to the surreal, crunchy visuals of this specific story.
Why Godot Was the Perfect Engine for Mouthwashing
If you’re a developer, you know Godot is the "little engine that could." For a long time, it was seen as a 2D-only powerhouse. People used it for platformers and top-down RPGs. But over the last couple of years, especially with the release of Godot 4, the 3D capabilities have skyrocketed.
Mouthwashing uses Godot to create a claustrophobic, lo-fi atmosphere. Think about the textures. They aren't trying to be "realistic" in the modern sense. They are trying to evoke a memory of realism from 1998. Godot’s render pipeline allows for a lot of flexibility without the heavy overhead of more "bloated" engines.
You can really see the engine’s strengths in the game’s lighting. The way the red emergency lights flicker against the low-resolution walls of the ship isn't just a filter. It’s a calculated use of the engine’s spatial nodes. Since Godot is open-source, devs can get "under the hood" in a way that’s much harder with proprietary software. If something feels slightly "off" in the movement or the way a door swings open, that’s often because the developer had total control over the physics script rather than fighting a pre-built engine template.
The PSX Aesthetic and Engine Limits
Let’s talk about the PSX aesthetic. It’s trendy. Everyone is doing it. But doing it well is hard.
In Mouthwashing, the "crunchiness" of the visuals isn't just about turning the resolution down. It involves specific shaders that mimic the "jitter" and "warping" of early 3D hardware. Godot uses a shading language called GDShader, which is remarkably similar to GLSL. Because Wrong Organ chose Godot, they were able to write custom shaders that handle vertex snapping—the thing that makes 3D models look like they’re "shaking" slightly when they move.
It adds to the instability. It makes you feel like the world is breaking.
- Custom Shaders: Godot’s shader language is incredibly efficient for retro effects.
- Lightweight Build: The game runs on a toaster. That’s the beauty of Godot; it doesn't require a 4090 to render a hallway.
- Scene System: Godot uses a "node" and "scene" architecture. Everything is a scene. A character is a scene. A room is a scene. This makes it very easy to swap out environments, which is crucial for a game that jumps between different timelines and hallucinations as frequently as Mouthwashing does.
Comparing Godot to the Big Players
If Mouthwashing had been made in Unreal, it might have looked too "clean." Unreal’s Nanite and Lumen systems are incredible for making things look like a Hollywood movie, but they can actually work against a developer trying to make something look purposefully degraded.
Unity is usually the middle ground. However, back in late 2023, Unity had that massive PR disaster with their "Runtime Fee" announcement. It sent a shockwave through the indie community. A lot of developers who were halfway through projects started looking at Godot as a life raft. While Mouthwashing was already deep in development by then, its success serves as a huge case study for why the industry is shifting.
Basically, Godot offers freedom. No royalties. No per-install fees. Just the code and your imagination. For a small team like Wrong Organ, that financial and creative independence is everything.
Performance and Accessibility
One thing people overlook when asking what engine was Mouthwashing made in is how it affects the end user. Because Godot is so lightweight, the game’s file size is relatively small. It loads fast.
The engine handles memory management in a way that is very friendly to lower-end PCs. If you’re playing on a Steam Deck or an older laptop, you’ll notice that Mouthwashing stays at a consistent frame rate. This is partly due to the dev’s optimization, but the engine provides the foundation. In Godot, you aren't fighting "engine bloat." You aren't loading thousands of background processes that the game doesn't actually need.
The Technical Reality of Indie Horror
Horror is about control. You have to control what the player sees and, more importantly, what they don’t see.
In the Godot Engine, the "Viewport" node is a powerful tool. In Mouthwashing, the developers use this to manipulate the player's perspective. There are moments where the environment shifts in ways that shouldn't be possible. Because Godot’s scene tree is so flexible, you can "instantiate" (basically spawn) new rooms or objects instantaneously without a loading screen if you’ve pre-loaded them into memory.
This allows for the seamless transitions between the "dream" sequences and the "reality" of the ship. You’re walking down a hallway, you turn a corner, and suddenly you’re somewhere else entirely. That’s not just clever level design; it’s an engine-level capability that Godot handles beautifully.
The Language Behind the Game: GDScript
Most of Mouthwashing is likely scripted in GDScript. It’s a language unique to Godot that looks a lot like Python.
For many developers, GDScript is the secret sauce. It’s fast to write and easy to read. This means the team can spend less time fighting with C++ syntax and more time fine-tuning the timing of a jump scare or the pacing of a dialogue box. When you’re making a narrative-heavy game, the speed of iteration is the most important thing. You want to be able to change a line of code and see the result in the game two seconds later. Godot’s "Live Edit" features allow for exactly that.
Common Misconceptions About Mouthwashing’s Tech
A lot of people think that because a game looks "retro," it must have been made in something like RPG Maker or a specialized "PS1 Engine." That’s almost never the case for modern commercial hits.
Mouthwashing is a fully 3D, modern application. It just happens to be wearing a vintage skin. The "engine" isn't what makes it look old; the art direction is what makes it look old. The engine is just the car that carries the art. You could make a 4K, photorealistic game in Godot if you wanted to (though it would be harder than in Unreal).
Another misconception is that Godot isn't "professional" enough for Steam hits. Mouthwashing, alongside games like Cruelty Squad and Cassette Beasts, has effectively killed that argument. It’s a professional-grade tool used by professional-grade developers.
Is Godot the Future of Indie Horror?
Honestly? Probably.
With the way the industry is moving, the "what engine was Mouthwashing made in" question is going to become more common as people see Godot's logo more often. The horror genre, in particular, thrives on "jank" and "grit." Godot provides a platform where that grit feels native rather than forced.
Developers are finding that they can achieve "The Aesthetic" much faster in Godot than by trying to strip away the high-end features of more complex engines. It’s about using the right tool for the job. For a game about five crew members trapped in a dying ship, a streamlined, community-driven engine like Godot was the perfect fit.
What You Should Do Next
If the tech behind Mouthwashing has inspired you, or if you're just curious about how these types of games come to life, there are a few concrete steps you can take to explore this further.
Check out the Godot Documentation. It’s surprisingly readable. Even if you aren't a coder, looking at how "Nodes" work will give you a much better understanding of how your favorite indie games are structured.
Follow Wrong Organ on Social Media. The developers often share behind-the-scenes glimpses or talk about their process. Seeing the "gray box" versions of the ship levels helps demystify how the horror is constructed.
Try out the Godot "PSX" Shaders. If you’re a hobbyist, there is a massive library of community-made shaders on GitHub and GodotShaders.com. Many of them are designed specifically to recreate the look seen in Mouthwashing. You can literally drop them into a project and see your 3D models start to "jitter" in that classic way.
Support Indie Horror. The best way to ensure we get more games that push the boundaries of engine tech is to buy them. Mouthwashing is available on Steam, and its success sends a signal to other devs that they don't need to rely on the "big two" engines to make a masterpiece.
Forget about the shiny, AAA polish for a second. Sometimes, the most effective tools are the ones that let the developer’s raw vision bleed through without any corporate interference. That’s Godot. That’s Mouthwashing.