Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[OpenMW] Support .omwaddons, .omwgames, and omwscripts #95

Closed
poperigby opened this issue Dec 28, 2024 · 9 comments
Closed

[OpenMW] Support .omwaddons, .omwgames, and omwscripts #95

poperigby opened this issue Dec 28, 2024 · 9 comments

Comments

@poperigby
Copy link
Contributor

  • .omwaddons are basically just renamed .esps
  • .omwgames are renamed .esms
  • omwscripts are for loading Lua script mods. Their position doesn't matter relative to plugins, so they should probably be sorted before .esms/.omwgames
@limo-app
Copy link
Owner

  • .omwaddons are basically just renamed .esps

  • .omwgames are renamed .esms

Does this mean they are also supported by LOOT? Would be nice to allow showing plugin conflicts for them.
If they behave like normal plugins, adding support would be as simple as adapting a regex. Otherwise the deployer will manage them separately.

@poperigby
Copy link
Contributor Author

I don't know if LOOT recognizes them, but yes, they perform the same as normal plugins. The binary structure is I believe almost identical so if LOOT doesn't currently recognize them, it would probably be an easy upstream fix in libloot.

@limo-app
Copy link
Owner

I did some searching and found this mod. It contains multiple .omwscripts files in subdirectories. The installation instructions say that these do not need to be added to openmw.cfg. Is it generally the case that only the .omwscripts directly in the Data directory need to be added manually?

@poperigby
Copy link
Contributor Author

You can safely ignore the individual module-specific omwscripts and the module-specific empty l10n folders. They exist only to make it as easy as possible for me to maintain this modpack, and to keep all individual modules up to date.

I think this just means the mod author kept them in there so they can easily keep the individual mods in-sync. They do nothing in this compilation pack version of the mod.

@limo-app
Copy link
Owner

7e184ac changed the OpenMW Plugin Deployer:

  • Added support for .omwaddon, .omwgame and .omwscript plugins
  • Removed LOOT support: Since .omwaddon and .omwgame plugins are unsupported by LOOT, showing conflicts and sorting by them would not work anyways
  • Added the ability to manually tag plugins as groundcover via the context menu in the Deployers tab
  • Added color grouping for script plugins, groundcover plugins and normal plugins
  • Plugins now get auto-tagged with: ES-Plugin, OpenMW and/ or Script

@poperigby
Copy link
Contributor Author

Thank you! Once this issue is fixed you can enable LOOT support for OpenMW again :)

loot/libloot#98

@poperigby
Copy link
Contributor Author

@limo-app .omwscripts files don't seem to be getting added 🤔

@limo-app
Copy link
Owner

Sorry, i somehow misread and thought the file extension was .omwscript instead of .omwscripts. Fixed in 9358735

@poperigby
Copy link
Contributor Author

No worries, thanks!

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

No branches or pull requests

2 participants