Skip to content

Conversation

@LukeFrankio
Copy link

Added automatic support for .omwaddon, .omwscripts, and .omwgame by creating dummy ESP files on first run. The tool now detects changes and automatically exports updates. Optional performance mode uses a cache to reduce export overhead. Note that you may need to launch Mod Organizer 2 more than once for the dummy ESPs to register correctly.

ignamiranda and others added 4 commits January 17, 2024 01:53
If you create a file alongside your omwaddon/omscripts with .esp added at the end, the exporter will add the relevant file at that point in the load order without the .esp extension. This preserves addons/scripts position in the load order according to where you have the dummy plugin in MO2.

This does not yet create the dummy esp files for you.
…g Features

- Implemented automatic export functionality that keeps OpenMW.cfg in sync with mod and plugin changes, utilizing smart debouncing to optimize performance.
- Added verbose logging option to provide detailed diagnostic messages during plugin operations.
- Introduced dummy plugin creation for .omwaddon, .omwscripts, and .omwgame content types to streamline OpenMW compatibility.
- Updated README.md to reflect new features, including highlights of the plugin's capabilities and settings for user customization.
- Improved code structure and readability, ensuring better maintainability and clarity in the OpenMWExport.py file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants