Launcher: remember the position of disabled content files (!5592) · Merge requests · OpenMW / openmw

The launcher only writes enabled files to openmw.cfg, so a disabled plugin loses its position every restart.

This adds a per-profile order= key to launcher.cfg holding the full content list in the order the user set it, disabled files included.

A file that is not in the saved order goes to the bottom. A partial list interleaves and can put a plugin above its own master.

The 0.51 launcher without the key ignores it and drops it on save. Unit tests cover the config layer. Checked through the GUI on Linux, Windows and macOS.

To test: disable a plugin, drag it, close the launcher, reopen.

I have read the CONTRIBUTING guidelines
My code runs locally
My code passes CI on my fork

Launcher: remember the position of disabled content files

Merge request reports