Morroblivion FAQ

Morroblivion Frequently Asked Questions

Frequently asked questions about the Morroblivion mod and its installation, gameplay, compatibility, and development.

Last reviewed: August 21, 2026. Current public release: Morroblivion v068.

Version notice: Installation, load-order, compatibility, patch, and add-on instructions are release-sensitive. Before installing or updating, use the current Morroblivion Project Release page and the Installation Instructions as the source of truth.

Index

General Questions

What is Morroblivion?

Morroblivion brings the world, quests, characters, creatures, items, and stories of The Elder Scrolls III: Morrowind Game of the Year Edition into the original The Elder Scrolls IV: Oblivion engine. It preserves the Morrowind setting while using Oblivion's renderer, combat, user interface, AI packages, scripting environment, and other engine systems.

Legal installations of both games and their required expansions are necessary. Morroblivion does not bundle the original commercial games and is not designed for Oblivion Remastered.

What is the current project status?

Current public release: Morroblivion v068.

Quest-status clarification: All quest groups listed below are implemented in Morroblivion, but many are not fully debugged. Implementation does not mean that every quest is free of errors or guaranteed to be completable. Some quests may still contain progression defects, script errors, broken conditions, missing supporting content, or game-breaking bugs. Numeric completion percentages are therefore not used.

Morrowind content implemented

  • House Hlaalu
  • House Redoran
  • House Telvanni
  • Fighters' Guild
  • Mages' Guild
  • Thieves' Guild
  • Tribunal Temple
  • Imperial Cult
  • Imperial Legion
  • Morag Tong, including the “Threads of the Webspinner” Sanguine items
  • Ashlander clan quests
  • Daedric shrine quests
  • Vampire clan quests
  • Wilderness miscellaneous quests
  • City, town, and fort quests

Tribunal content implemented

  • Tribunal main quest
  • Tribunal miscellaneous quests

Bloodmoon content implemented

  • Bloodmoon main quest, including both paths
  • Bloodmoon miscellaneous quests
  • East Empire Company quests

Bug reporting and continued testing remain important because a converted quest can exist in the master file without every branch, condition, stage, package, item, or dialogue result functioning correctly in live play.

Is morroblivion.com the official project site?

Morroblivion is a fan-created community project. Morroblivion.com functions as the project's principal community, release, documentation, and support site, but neither the site nor the project is affiliated with or endorsed by Bethesda Softworks or its related entities.

The original Morroblivion work is associated with Galadrielle. Skywind and Skyblivion later developed as separate TES Renewal projects and now operate through their own websites and development communities.

Requirements and Installation

What do I need to own?

  • A legitimate installation of The Elder Scrolls III: Morrowind Game of the Year Edition, including Tribunal and Bloodmoon.
  • A legitimate installation of the original The Elder Scrolls IV: Oblivion, version 1.2.0416, with Shivering Isles.
  • xOBSE, the actively maintained continuation of the Oblivion Script Extender.

CD/DVD, Steam, and GOG installations are supported. These instructions apply to the original 2006 version of Oblivion, not Oblivion Remastered.

How do I install Morroblivion v68?

  1. Back up existing Oblivion saves, load-order data, and any manually installed files that you need to preserve.
  2. Download the current complete installer from the Morroblivion Project Release v068 page.
  3. Extract the installer archive and run the installer.
  4. Allow the installer to detect the legal Morrowind and Oblivion installations. When selecting paths manually, choose each game's main folder, not its Data folder.
  5. For a direct installation, select the Oblivion directory as the Morroblivion installation directory. A different staging directory may be used when required by a managed-mod setup.
  6. Install xOBSE separately.
  7. Install the OBSE/xOBSE plugins required by the Morroblivion options and add-ons you enable.
  8. Use Wrye Bash, LOOT, or another Oblivion-aware tool to review plugin activation and load order.
  9. Launch Oblivion through xOBSE.

Do not install v67 Patch 1, Patch 2, Patch 3, or the v67 Dagger Galore package over v68. The v68 installer already includes the applicable v67-era corrections and currently has no separate patch download.

Older instructions that require the v67 Nexus API workflow do not apply to the rewritten v68 installer.

Which OBSE/xOBSE plugins are recommended?

Check the current Project Release page before installing because recommendations can change. The v68 release page currently lists the following:

Install only one silent-voice solution unless the relevant readme explicitly instructs otherwise.

What should the load order look like?

Use LOOT for automated sorting, then review Morroblivion-specific placement manually. A safe baseline begins as follows:

  1. Oblivion.esm
  2. Morrowind_ob.esm
  3. Other ESM files
  4. Other gameplay, worldspace, and compatibility plugins
  5. Morrowind_ob.esp
  6. Morrowind_ob - UCWUS.esp, if installed
  7. Morrowind_ob - Conversation.esp, if installed
  8. Morrowind_ob - MorroblivionTreeReplacer.esp, if installed
  9. Morroblivion map replacers

Without EngineBugFixes, Morrowind_ob.esm must load directly after Oblivion.esm. EngineBugFixes removes that strict engine requirement, but retaining the legacy order remains a safe baseline.

Morrowind_ob.esp loads the Morroblivion BSA archives and is required. It contains one intentional identical-to-master record; do not clean that record with xEdit.

Can I install Morroblivion in another language?

Translations and localized plugins are version-sensitive. The legacy FAQ identified English and German, but the current v68 release page does not publish a consolidated translation-support matrix. Do not assume that a translation made for an older master is compatible with v68. Confirm that the translation explicitly supports the current Morrowind_ob.esm before installing it.

Can Morroblivion run on Linux through Wine or Proton?

xOBSE includes Linux/Proton launch guidance, and Oblivion can run through Wine or Proton. Morroblivion adds a Windows installer, large resource deployment, OBSE plugins, and load-order requirements, so Linux installation may require manual path and prefix management. Follow the current xOBSE Linux instructions and verify each native OBSE plugin separately; compatibility should not be assumed solely because the base game launches.

How should I use Wrye Bash?

Wrye Bash remains useful for BAIN installation, conflict tracking, plugin management, and Bashed Patch workflows.

  1. Install and launch Wrye Bash.
  2. Open the Installers tab and initialize BAIN when prompted.
  3. Drag a supported archive onto the Installers tab or place it in the generated Bash Installers directory.
  4. Verify the package structure and selected sub-packages before installing.
  5. Use package order to control which conflicting loose files win.
  6. Use the Mods tab and LOOT to manage plugin activation and load order.

Install order controls loose-file conflict priority. Load order controls ESM/ESP record priority. They are separate systems and both matter.

How do I update from an older Morroblivion release?

Back up saves and the existing mod setup, then follow the update notes on the current Project Release page. Do not layer v67 patch files over v68. Verify every Morroblivion add-on against the current master because mods built against an older Morrowind_ob.esm may be incompatible. A new game may be required when a release or add-on changes persistent quest, worldspace, or reference data.

Troubleshooting and Performance

Why do I see yellow exclamation marks, purple objects, or missing floors?

  • Yellow exclamation marks or missing body parts: a required mesh is missing or installed to the wrong path.
  • Purple objects: a required texture is missing or installed to the wrong path.
  • Falling through floors or the starting ship: core resources were not deployed correctly, were placed one directory too deep, or are being overridden by an incompatible package.
  • Unexpected solid-color or black rendering: review HDR, anti-aliasing, display-wrapper, shader, and renderer settings; then test with a minimal visual stack.

Verify the installed file paths, BSA loading, Morrowind_ob.esp activation, package conflict order, and the v68 installer log before reinstalling.

Why does the game crash or run slowly?

Morroblivion places substantially more content into Oblivion's 32-bit engine than the original game was designed to manage. CPU single-thread performance, memory pressure, cell-buffer limits, distant land, high-resolution textures, scripts, and additional shaders can all become bottlenecks.

  • On a 64-bit version of Windows with at least 4 GB of system memory, apply the 4GB Patch to Oblivion.exe.
  • Install the current recommended engine-fix and display plugins from the Project Release page.
  • Reduce distant-land, shadow, texture, and shader load when testing wilderness crashes.
  • Test with a minimal load order before assuming that a particular Morroblivion cell is defective.
  • Do not use old hardware recommendations such as specific 2008–2010 GPUs as a current performance standard; diagnose the actual engine bottleneck instead.

What information should I provide with a bug report?

  • Morroblivion version and installer date
  • xOBSE version
  • Complete load order
  • Installed Morroblivion add-ons and compatibility patches
  • Exact reproduction steps
  • Quest name, current stage, and recent journal entries when applicable
  • A save made before the failure, when practical
  • Relevant crash, xOBSE, or plugin logs
  • Results from a minimal-load-order test

Search the Morroblivion Problems forum before opening a new report. State clearly whether the defect prevents progression, corrupts a save, causes a crash, or is visual only.

Gameplay

Where does a new game begin?

With Morrowind_ob.esm active, a new game uses Morroblivion's alternate start and begins in the hold of the prison ship at Seyda Neen rather than in the Imperial City Prison. The Oblivion main quest therefore does not start automatically.

How do I travel between Vvardenfell and Cyrodiil?

Travel between the worldspaces requires a current World Transport option or another compatible transport add-on. The v68 release documentation identifies World Transport as being updated, so use only the transport package and instructions linked for the current release. Do not install a legacy transport plugin merely because it worked with an older Morrowind_ob.esm.

How do I start the Morrowind main quest?

Morroblivion's Morrowind main quest is configured to begin when the player reaches level 4. This differs from the original game's less restrictive start and is an intentional Morroblivion design decision.

How do I start Tribunal and Bloodmoon?

Tribunal is configured as higher-level content. The player must complete either the Morrowind main quest or a major faction questline and reach level 15 or higher.

Bloodmoon can be reached by traveling from Khuul to Solstheim or by reaching Solstheim through another valid route. It does not use the same level gate as Tribunal.

Are quest markers available?

Yes. Morroblivion includes quest markers for many quest stages, and they can be disabled through the Morroblivion configuration. Not every possible stage or branch is guaranteed to have a marker.

Is map-based fast travel available?

Yes. It can be enabled or disabled in the Morroblivion configuration, and a destination generally must be discovered before it can be selected.

Do NPCs use Oblivion-style AI schedules?

Many Morroblivion NPCs use Oblivion AI packages and schedules, making them more dynamic than their original Morrowind counterparts. Package coverage and behavior vary by NPC, location, and quest state.

Is all dialogue voiced?

No. Morrowind_ob - Conversation.esp adds original Morrowind voiced lines where available. A separate Morroblivion Fully Voiced project is also available, but it is an optional add-on and must match the installed Morroblivion version.

For unvoiced dialogue, use Ely's Universal Silent Voice or VoiceFile Redirector so subtitles remain visible long enough to read.

Are creatures, loot, NPCs, and merchants leveled like Oblivion?

Morroblivion generally preserves Morrowind's fixed-world design for creatures, quest rewards, NPCs, and most loot rather than applying Oblivion-wide level scaling. Merchant inventories may include appropriate leveled additions so the player can access some level-appropriate items without converting the entire world to Oblivion's scaling model.

Gameplay overhauls can change this behavior, so verify the rules introduced by each overhaul and any Morroblivion-specific patch.

Why can an implemented quest still fail?

Morrowind and Oblivion use materially different dialogue, quest, AI, inventory, and scripting systems. Morroblivion quests therefore require converted records plus extensive manual scripting and validation. A quest may be present and substantially playable while still failing on a particular branch, stage, disposition check, package, item transfer, or engine edge case.

Do not interpret “implemented” as “fully debugged.” Report reproducible progression blockers with the evidence listed in the troubleshooting section.

Mod Compatibility

Where can I find mods made for Morroblivion?

Use the current Mods for Morroblivion hub and the optional add-on list in the Project Release thread. Confirm that every mod explicitly supports v68 or the current Morrowind_ob.esm.

Is Morroblivion compatible with Oblivion mods?

Morroblivion is located primarily in its own worldspace, so mods that alter only Cyrodiil or other Oblivion worldspaces are generally less likely to conflict directly with Vvardenfell. This is not a blanket guarantee: shared races, factions, scripts, global variables, leveled lists, animations, interfaces, game settings, weather, combat, magic, economy, and engine plugins can affect both games.

Generally lower-risk categories

  • Cyrodiil-only landscape and quest mods that do not alter shared records
  • Texture and mesh replacers that preserve expected paths and formats
  • User-interface mods
  • Custom equipment, spells, classes, birthsigns, and cosmetic content that do not overwrite Morroblivion records
  • Engine and utility plugins specifically tested with the current release

Categories requiring targeted testing

  • Combat, stealth, magic, leveling, economy, survival, and realism overhauls
  • Companion systems and custom races
  • Body, skeleton, animation, and first-person replacers
  • Mods that scan or classify only vanilla Oblivion creatures, food, diseases, ingredients, factions, or worldspaces
  • Mods that rebuild leveled lists, merchant inventories, or global game settings

High-risk or commonly incompatible categories

  • Most Morroblivion mods created before 2014 unless their page confirms current-release support
  • Original ESP Converter-based Morroblivion mods
  • Any plugin built against an older and structurally incompatible Morrowind_ob.esm
  • Mods that overwrite current Morroblivion quests, worldspace records, scripts, BSAs, or required file paths
  • Map-marker or map-replacer mods used together without an explicit compatibility design

Which optional add-ons are associated with recent releases?

The current release page identifies examples such as Custom Map Markers, Morroblivion Fully Voiced, Lost Magic, MultiSkill Trainers, and Morrowind clothing packages. These are separate projects, not proof of universal compatibility. Read each mod's requirements, version notes, load-order instructions, and bug reports before installation.

Modding and Development

How can I help with the project?

Contributors can assist with quest testing, scripting, dialogue, object placement, meshes, textures, animation, compatibility work, documentation, and bug reproduction. Effective contributions require familiarity with both Morrowind's source behavior and Oblivion's implementation constraints.

Coordinate with the current project maintainers before beginning large-scale work. Use a separate plugin or agreed source workflow, document every changed record, and do not continue editing a submitted plugin after maintainers have begun merging it unless they explicitly request that workflow.

Which tools are appropriate?

Read the Oblivion Mods FAQ, current xEdit cleaning guidance, and the relevant tool documentation before modifying the master.

Should I clean Morroblivion files with xEdit?

Do not apply automated cleaning blindly. The current release documentation states that Morrowind_ob.esp contains one intentional identical-to-master record. Preserve intentional records and follow project-specific cleaning instructions rather than generic assumptions.

How do I convert a Morrowind mod to Morroblivion?

Conversion difficulty depends on the mod. A small item, dialogue edit, or simple quest may be faster and safer to recreate in the Oblivion Construction Set than to process through an old converter. Complex mods require manual review of forms, scripts, dialogue, cells, worldspaces, pathing, animations, assets, and engine-specific assumptions.

Most old ESP Converter-based Morroblivion plugins and plugins mastered against an older Morrowind_ob.esm should be treated as incompatible until rebuilt and tested. Never assume that a plugin is current merely because it loads without an immediate missing-master error.

Morroblivion Compared with Morrowind

Why play Morroblivion instead of the original game or OpenMW?

Choose Morroblivion when the objective is to experience Morrowind's world and quests through Oblivion's combat, AI, user interface, renderer, scripting ecosystem, and shared-character possibilities. Choose the original Morrowind engine or OpenMW when native Morrowind mechanics and compatibility with Morrowind-specific mods are the primary requirement. These are different implementation strategies rather than interchangeable copies.

Feature Morroblivion Original Morrowind Core gameplay systems Use one character across Morrowind and Cyrodiil Quest markers Map fast travel NPC scheduling Default combat World scaling Essential NPCs Cast-when-used enchantments Original Morrowind voice lines Script extender ecosystem Mod ecosystem Morrowind-specific mechanics
Oblivion engine and gameplay framework Native Morrowind engine and gameplay framework
Supported through a compatible World Transport setup Not natively applicable
Available for many stages; configurable Not part of the original default interface
Available and configurable Not available by default
Uses Oblivion AI packages where implemented Mostly static placement and limited schedules
Oblivion-style direct-hit combat and blocking Morrowind skill/chance-to-hit combat
Generally preserves Morrowind's fixed content, with some Oblivion-system additions Generally fixed content and limited leveled-list use
Some actors may use Oblivion essential protection Major characters can generally be killed, with a broken-thread warning
Restored through the recommended Morrowind_ob - UCWUS.esp setup Native feature
Available through Morrowind_ob - Conversation.esp; fuller voice projects are optional Limited original voiced dialogue
xOBSE MWSE for the original engine; separate Lua systems in OpenMW
Oblivion mods plus current-release Morroblivion add-ons Morrowind or OpenMW-specific mods
Some are recreated, adapted, or supplied by optional add-ons; behavior may not be identical Native behavior

Historical Information

Was Morroblivion shut down?

In 2008, early Morroblivion distribution and discussion were removed from Bethesda's official forums and Nexus hosting following concerns about distributing Morrowind assets for use in Oblivion. The project subsequently adopted an installer model that verifies legal Morrowind and Oblivion installations and deploys converted material from the user's own games.

Why do old guides conflict with current instructions?

Morroblivion has used several installers, resource archives, patch structures, master-file revisions, optional packages, and mod-management conventions. Instructions written for v58, v60, v64, v65, v66, or v67 may be historically useful but should not override the current v68 release documentation.

Examples of obsolete guidance include separate v67 patch layering, the v67 Nexus API workflow, BOSS as the primary sorter, old TESNexus URLs, old hardware recommendations, and the assumption that every pre-2014 Morroblivion plugin remains compatible.

Legal and Disclaimer

Morroblivion is a fan-created video-game modification and community project. Bethesda Softworks and other trademark holders are not affiliated with, and do not sponsor or endorse, morroblivion.com or the Morroblivion project.

Installing mods, engine patches, script extenders, and third-party utilities can cause crashes, save corruption, data loss, or other software problems. Back up saves and important files, follow each tool's documentation, and proceed at your own risk.

The legacy FAQ contained a full Terms and Conditions block with time-sensitive statements concerning advertising, donations, server costs, privacy practices, anti-spam providers, user-content licensing, jurisdiction, and liability. That text has been separated from this FAQ for independent legal and privacy review and should not be represented as current policy without approval.