Documentation

dream-ini reads a Morrowind.ini and writes what OpenMW needs from it into an openmw.cfg. The command line, the GUI and the library run the same importer, so everything here about what an import does applies to all three.

Learn it#

• Start here: download it, import your Morrowind.ini, and check the result before OpenMW reads it.
• What an import does: every key it reads, where it finds your content and archives, the load order it writes, and what it leaves alone.

Use it#

• Writing the cfg: preview, a separate file, or your cfg updated in place, and what each keeps of the cfg you started from.
• The GUI: every field, the three output modes, languages and controllers.
• Handhelds: the PortMaster build and the muOS app.
• Embedding Luau: giving scripts @dream/ini through l3i.

Look it up#

• Command line: every option and command, and the exit codes.
• Differences from OpenMW’s importer: where dream-ini and mwiniimporter part ways, on purpose.
• Platforms and performance: what each download can do, the license, what is tested, and what an import costs.
• Rust API: the importer, the parsers and the cfg writers.
• Luau API: the @dream/ini module and the extension that provides it.