Case study

OpenMW: replacing Morrowind’s engine while reusing original content

Provides an independent engine for playing Morrowind and an alternative editor, OpenMW-CS. It loads original game content through its own runtime and documents script and mod compatibility differences; it is an engine replacement rather than a recovered Bethesda source tree.

Requirements and limitations

Playing Morrowind requires the user’s original game data, including Morrowind.esm and the installation settings. Tribunal and Bloodmoon are optional expansions; the installation guide recommends both for best results. OpenMW-CS can also support separately authored projects.
The pinned README and build files identify version 0.52.0; this is a source-snapshot identifier, not a claim that a release was tested. The README lists Windows 10+, macOS 14.8+ and Linux, with no 32-bit support.
The source configuration uses CMake 3.16+, C++20, SDL2 2.26+, OpenSceneGraph 3.6.5+, Boost 1.70+ and OpenAL; launcher/editor/wizard builds use Qt6. Additional dependencies depend on enabled components.
The project reports the main quests as completable, but warns about side quests and mods that depend on original-engine quirks. Example Suite integration tests and the separate Morrowind-content test setup cover selected behavior, not complete original-game or mod equivalence; none was rerun here.
The official GitHub mirror points to the main GitLab project. GPLv3 covers project code, with separate font/dependency terms and original-game data rights. No REA or coding-agent involvement is established by the reviewed sources.

About this entry

Type: Case study
Category: Independent reconstruction cases
Relationship: Independent reconstruction project
Targets: Game

Sources reviewed 2026-10-17

The description was reviewed against primary sources. This does not establish runtime testing, security auditing or verified compatibility.

Requirements and limitations

About this entry

Primary sources