What the official sources disclose
Steam lists Mandragora as developer, tinyBuild as publisher, and Indie and Simulation as the relevant product genres. It explains the repair shop, devices, finances, parts browser, customer stories, choices, and system requirements. The page does not include an engine field or an engine credit in the reviewed snapshot.
The Game.Press resource supplies structured credits, release date, hashtag, platform requirements, and press-pack access. It also does not name Unity, Unreal Engine, Godot, a proprietary engine, or another technology. The studio's official public material reviewed for this task supplies no engine statement either.
Absence from these sources supports one limited conclusion: the engine is not publicly confirmed here. It does not prove that the project uses a secret proprietary engine or that a credit cannot appear inside the game's full credits. The correct public status remains To be confirmed.
Why visuals are not reliable proof
Lighting, materials, user-interface style, camera behavior, and three-dimensional assets can resemble games built with a familiar engine. Similar results can be produced by different engines, renderers, middleware, plugins, and custom pipelines. A visual resemblance is therefore a clue for investigation, not a verified credit.
ReStory's detailed device layers and period-styled browser describe design goals rather than implementation technology. A developer can build those features in several commercial or internal environments. Screenshots cannot reveal source-code architecture, editor tooling, build system, or licensing arrangement.
Even performance characteristics are ambiguous. Frame drops, ultrawide behavior, loading times, or graphics settings can arise from game code, content, drivers, middleware, operating systems, and engine configuration. A patch fixing one symptom does not identify the underlying engine.
Mod loaders do not settle the question
The collected community mod page mentions BepInEx, MelonLoader, and a ReStory-specific framework. Those projects describe how community plugins are loaded for particular mods. Their presence does not constitute a Mandragora or tinyBuild engine disclosure.
Loaders can support more than one runtime, be adapted by a community framework, or interact with a packaged game through techniques that do not reveal the original editor. A mod author's compatibility claim may still be technically useful without becoming an official engine credit. Keep loader requirements in the mods guide and engine attribution in this evidence guide.
Community documentation could eventually offer reproducible technical evidence, but it should name files, runtime behavior, version, and method. Even then, describe it as community analysis unless the developer confirms it. This page will not convert a plugin label into a first-party statement.
System requirements are separate
The Windows minimums list Windows 10 x64, a two-core and four-thread processor, 4 GB of memory, GTX 750 Ti graphics, DirectX 11, and 1 GB of storage. The current Mac table lists macOS 14 or newer, Apple M1, 8 GB of memory, integrated M1 graphics, and 1 GB of storage. These fields tell players about supported environments, not which editor or runtime created the game.
DirectX 11 compatibility is used by many technologies and does not identify a single engine. Apple M1 support likewise describes target hardware and operating system rather than a development tool. Storage size cannot distinguish an engine because asset compression, content volume, packaging, and updates all affect it.
Do not use a minimum GPU or API to reverse-engineer an engine credit. Those values can narrow technical troubleshooting but cannot settle authorship of the software stack. The only reliable public answer is a direct credit or documented developer statement.
What would confirm the engine
A statement from Mandragora or tinyBuild naming the engine would be the clearest confirmation. A full in-game credits screen, official technical presentation, developer interview, job post explicitly tied to ReStory, or licensed middleware notice could add supporting evidence. Each source should identify this game rather than the studio's unrelated projects.
Store disclosure from an engine vendor can also help when it directly names the title and developer. A generic showcase image, social-media tag, or list copied between databases is weaker unless it links back to a primary record. Record the publication date and exact wording because projects can change technology during development.
If official credits name several technologies, distinguish primary engine, rendering tools, audio middleware, analytics, localization, and other components. One middleware logo does not necessarily identify the core engine. The answer should preserve the role each credit actually states.
Why the unknown status is useful
Marking the engine unconfirmed prevents compatibility guesses from becoming support promises. A player should use published system requirements and official patches, while a mod user should follow the exact loader and plugin documentation for that version. Neither task requires a guessed engine name.
The unknown status also protects developer credits. Assigning a commercial engine without evidence can misstate licensing, tooling, performance responsibility, and the work of the team. A short accurate answer is better than a detailed but invented technical profile.
Executable metadata or packaged library names may narrow an investigation, but they can belong to middleware, launchers, crash reporters, or unused dependencies. Publishing such a finding requires a reproducible method and a clear limitation statement. This project does not bypass access controls or inspect private source code to answer the keyword.
An official developer talk would provide stronger context because it could explain why a tool was selected and which systems were custom. Even then, confirm that the talk refers to the released ReStory build rather than a prototype or another Mandragora project. Technology can change during production.
The unknown label also keeps troubleshooting practical. Players can report hardware, operating system, settings, version, and exact reproduction steps without knowing the engine. Developers need observable behavior more than a guessed technology name when investigating a bug.
Databases that require an engine field should leave it empty or explicitly unconfirmed. Copying a community guess into structured metadata makes the claim spread into search results. A future official credit can be added without first undoing that misinformation.
Do not use a question mark as hidden confirmation. Write unconfirmed plainly. Readers should not have to infer the evidence status.
Check Mandragora's official site, the Steam product page, and official announcements for a future disclosure. Until one names the technology, the ReStory game engine remains To be confirmed. Community claims can be noted as analysis only after their method and limits are documented.