OMORI looks like it should have been built in Unity or Unreal. A 20-hour story RPG with hand-drawn animation, an original emotion-state battle system, two interlocking worlds, and over 1 million copies sold as of December 2022 sounds like a custom-engine project. It was not.
OMORI was built in RPG Maker MV, the JavaScript and HTML5 entry in the long-running RPG Maker series. It launched for Windows and macOS on December 25, 2020, about six years after its initial Kickstarter funding, after repeated delays and a backer-only demo on April 9, 2018, then arrived on Nintendo Switch, Xbox One and Series X/S on June 17, 2022 and PlayStation 4 on June 24, 2022 in North America with added content. That choice explains both why the game exists at all and why it feels so unsettling.
The facts first: what OMORI and RPG Maker MV actually are
OMORI is a 2020 single-player role-playing game developed and published by indie studio OMOCAT, directed by Omocat. You control Sunny, a reclusive teenager, and his dream-world alter ego Omori. Gameplay splits between Faraway Town in the real world and the surreal Headspace dream world, where a four-person party — Omori, Aubrey, Kel and Hero — explores top-down maps, solves puzzles, does side quests, and fights turn-based battles. Outside battle you save and heal at a picnic blanket with Mari. Your choices lead to several endings.
The battle hook is emotions, not just elements. Neutral is baseline. Angry raises attack but lowers defense. Sad raises defense but lowers speed and shifts some Heart damage to Juice. Happy raises speed and luck but lowers accuracy. They form a rock-paper-scissors triangle: Happy beats Angry, Angry beats Sad, Sad beats Happy, with stronger intensities on top. The official Steam description sums up the pitch in one line: explore a strange world full of colorful friends and foes, and when the time comes, the path you have chosen will determine your fate. Steam also carries a blunt content warning: depictions of depression, anxiety and suicide, plus bright flashing imagery that may affect photosensitive players.
Minimum PC requirements tell you how light the tech footprint is: Intel N4100 or similar, 4 GB RAM, DirectX 9 / OpenGL 4.1 capable GPU, and only 2 GB of storage.
RPG Maker itself is a Japanese game-creation series originally from ASCII, later Enterbrain and Gotcha Gotcha Games. Every PC version centers on the same three tools: a tile-based map editor, a simple event system for NPCs, puzzles and quests, and a battle editor, plus premade tilesets, characters and audio you can replace. The series is written across generations in Ruby, JavaScript and HTML5, and even its own history notes that adventure games like Yume Nikki were built by bending the RPG template.
RPG Maker MV is the generation OMORI used. Its Steam documentation lists exactly what changed from the older Ruby versions: make on Windows or macOS, then export to Windows EXE, macOS APP, Android APK, iOS IPA, or HTML5 for browsers. It has an improved map editor with an automated upper layer, a simple intuitive event system, built-in Fantasy and Sci-fi art and audio, a checkbox to switch between Front View and Side View battles, mouse and touch input, higher default resolution at about 1.5x, and a plugin manager where you drop in a .js file and configure it in the editor. In short: defaults for everything a JRPG needs, JavaScript when you want to break the defaults.
What MV gave a tiny art-led team
Speed where it mattered. OMORI grew out of Omocat's Omoriboy webcomic, with hand-drawn characters, surreal maps, and music as the core value. MV handed the team Headspace for free: top-down maps, doors, NPC dialogue, switches, treasure in the form of Clams in dreams and dollars in reality, and a working save-and-heal loop. They did not have to write a renderer, a tile collider, or a dialogue queue to test whether White Space felt empty enough or Headspace felt crowded enough.
A narrative grammar players already know. Anyone who has played EarthBound, Yume Nikki, or any RPG Maker horror game recognizes the loop instantly: walk, talk, check the bookshelf, rest at the save point, enter battle. MV's Front View and Side View defaults meant OMORI could spend its customization budget on one system — emotions, follow-up attacks from shared energy, Heart as health and Juice for skills — instead of reinventing menus, turns, and damage formulas.
An escape hatch, not a cage. MV's plugin system accepts JavaScript. The docs explicitly invite you to get plugins from the maker, from fans, or write your own. OMORI's emotion intensities, animated faces, lighting tricks, and photo-album sequences are exactly the kind of thing you would overwrite defaults to get. You take the map editor and event system as-is, then write code only where the game is different.
A performance ceiling that did not matter. Turn-based battles, mostly static sprites, and small maps do not need a 60 fps action engine. That is why the Intel N4100 / 4 GB RAM minimum is credible. The web-tech base — HTML5, JavaScript, deployed on desktop through an NW.js-style wrapper — never has to stream an open world or simulate physics. The design hides the engine's weakest point.
What MV cost
Stigma and visual sameness risk. RPG Maker games are often dismissed as asset flips because the default tilesets and chimes are so recognizable. OMORI had to over-invest in original art, custom UI, and music by Pedro Silva, Jami Lynne and Calum Bowen to escape that association. The engine saved programming time and moved the cost to illustration and audio.
JavaScript plugin fragility. MV was the first major RPG Maker to drop Ruby RGSS for JavaScript plugins. That opened browser and mobile export, but the ecosystem is fragmented: plugins conflict, break on updates, and assume you can read someone else's minified code. Anyone who has managed ten MV plugins knows the feeling — the editor says drag-and-drop, the console says undefined is not a function. OMORI's six-year development with numerous delays fits that pattern: maps and story move fast, custom battle and effects become long-tail debugging.
PC-first, console-later tax. Windows and macOS shipped in December 2020. Consoles needed another 18 months until June 2022, with added content to justify the gap. MV exports cleanly to PC and HTML5, but Switch, Xbox and PlayStation wrappers need extra work around input, save, resolution, and certification. If your plan is day-one console, MV is the wrong bet. If your plan is prove it on Steam first, the delay is acceptable.
My read: OMORI weaponized familiarity, and that is why MV was the right horror engine
Here is where I depart from the usual “RPG Maker is bad for commercial games” takes. I think OMORI is scary because it is in RPG Maker, not in spite of it.
Most horror engines try to make you afraid of the unknown: volumetric fog, photorealistic basements, motion-captured monsters. OMORI does the opposite. It starts inside the coziest grammar in games — the JRPG town, the cheerful battle jingle, the picnic blanket that heals you — and then lets that grammar rot. When a save blanket appears in a nightmare hallway, or a familiar emotion icon flips from Happy to Afraid, or a photo album page distorts, the violation lands harder than a new monster would in Unity, because you already trusted the menu. It is the sitcom-laugh-track theory of horror: corrupt a signal people have heard a thousand times and they feel it instantly.
That is my term for it: familiarity-as-horror. RPG Maker MV gave OMORI a shared language with players for free. An indie team cannot teach a novel UI language and a novel trauma narrative in 20 hours. By borrowing MV's towns, doors, switches, and turn order, OMORI saved all its teaching budget for the one new idea — that feelings are combat stats — and for the story question of whether Sunny confronts or suppresses memory.
A second, less romantic point: I see MV as a creative filter, not just a shortcut. Because JavaScript plugins are painful to chain, you are forced to ask which custom system is worth the pain. OMORI answered: emotions and dreams. Everything else — walking, talking, shopping for Clams, flipping between Front and Side View logic — stayed stock. Constraints like that produce the picnic-blanket save and the White Space door loop, ideas that feel inevitable now but look like scope discipline in hindsight. A Unity team with no constraints might have added crafting, jumping, and multiplayer and lost the tone.
Finally, turn-based pacing is a performance shield. Web-based MV games stutter when you ask for hundreds of projectiles or real-time lights. OMORI never does. Damage numbers, emotion shifts, and follow-up attacks happen on human decision time, not frame time. Low requirements are not an accident; they are proof the design and the engine's ceiling were matched on purpose. It is the inverse of the bullet-heaven story where a web stack breaks under spawn counts. Here the stack survives because the fantasy is slow dread, not fast action.
None of that means MV is “secretly powerful.” My blunter version: MV is boringly competent at exactly one thing — letting two artists and a writer test a 2D story loop this afternoon — and OMORI had the taste to keep the boring parts boring so the scary parts could be strange.
What indie devs can steal without cloning OMORI
- Prototype the loop in the grammar players know. If your horror needs doors, notes, keys, and a safe rest spot, build it in tiles and events first. You will know in a week whether exploration feels lonely.
- Defer code to one signature system. Let maps, dialogue, and saves stay default. Spend JavaScript only on the mechanic that makes your game unmissable. For OMORI that was emotions. For you it might be memory, debt, hunger, or reputation.
- Budget for de-stocking. If you ship in MV, assume 30-40% of art and audio must be custom or heavily edited, or players will read your game as “another RPG Maker game” in screenshots.
- Quarantine plugins early. Pick a fixed MV version, lock plugin versions, keep a one-page list of which plugin owns battle, lighting, and save, and test battle plus save on every change. Do not add a cool minimap plugin in month 30.
- Plan PC first if you use MV. Ship Windows and macOS, prove the story, then pay for console wrappers and extra content. Do not promise simultaneous console launch on Kickstarter unless you have porting help.
If you want to feel these ideas in 10 minutes in a browser
OMORI is a 20-hour commitment about anxiety, depression, trauma and suicide, and its flashing imagery is not for everyone. If you want to study its tools without that weight, these free browser games isolate one OMORI muscle at a time.
Choice-and-consequence is OMORI's spine — the path you choose determines fate. Fleeing the Complex is a point-and-click prison-break story where every scene pauses for a choice, wrong tools end in funny fails, and five endings plus 60 unique fails reward replay. Play one stealth solo run and one team-up run back to back. You will feel how early helper choices split routes, the same way answering Kel's knock or staying inside splits Sunny's three days.
Framing is OMORI's second trick — what you photograph and remember changes the world. We Become What We Behold is a five-minute game by Nicky Case where you photograph Squares and Circles and your coverage steers the crowd toward calm or panic. It is the fastest playable lesson in selective attention I know, and a good warm-up for OMORI's photo album, where a missing picture matters more than a boss.
Atmospheric dread plus puzzles is the third muscle. Horror Tale Kidnapper drops you in fog-covered Lakewitch to find missing children, search dark forests and abandoned buildings for clues, hide, manage supplies, and solve locked-door puzzles toward different endings. It is first-person and louder than OMORI, but its observe-hide-solve loop mirrors Headspace exploration: check every room, read the environment, stay calm when the presence grows.
None of these replaces OMORI. Together they let you practice branching endings, moral framing, and horror search in short sessions before you decide if a long psychological RPG is for you.
Open questions and limits
I could not verify from primary pages exactly which MV version and which community plugins OMORI forked, or how much of the emotion system is bespoke versus extended. The Kickstarter page itself was not retrievable at writing time, so I rely on the documented six-year span from funding to December 2020 release and the April 2018 backer demo rather than a funding total. Console port engineering details for the June 2022 releases were also not disclosed in the sources I could retrieve.
What is solid: engine identity as RPG Maker MV, dual-world story RPG structure, emotion triangle mechanics, release timeline, 1-million-copy scale as of December 2022, MV's HTML5 and JavaScript plugin model with multi-platform export, and the low system footprint. Everything in the “my read” section is opinion — a way to explain why boring tech plus familiar menus can be scarier than new tech — not a claim that MV is the best engine for horror in general.
If you are making a story-first RPG with a small team, no day-one console requirement, and one custom system worth plugin pain, MV in 2026 is still a rational, unfashionable bet. If you need real-time combat, procedural worlds, or simultaneous console launch, pick something else and keep OMORI as a lesson in what to keep boring on purpose.
Top comments (0)