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

SkyUI BSA script conflicts #2691

Open
sibir-ine opened this issue Jan 15, 2023 · 0 comments
Open

SkyUI BSA script conflicts #2691

sibir-ine opened this issue Jan 15, 2023 · 0 comments

Comments

@sibir-ine
Copy link
Member

We have two message informing users when a mod they've installed overwrites an essential SkyUI script, ski_playerloadgamealias.pex, with an older version that interferes with SkyUI's operation. In combination, they check if a user has the old script installed loose or a BSA loaded that is known to contain it. However, as of v0.19.0, LOOT takes BSA asset overlaps into account when sorting similar to record overlaps. Now that LOOT takes these overlaps into account, it'd be helpful to do so to some extent when considering load rules between plugins. In this case, we could simply remove Sky UI from the Fixes & Resources group & load it after the plugins known to load BSAs with the old script, avoiding the need for users to remove the script & repackage the BSAs themselves. We could then remove one of the messages & simplify the condition of the other drastically.

SkyUI doesn't overwrite any vanilla records, & it only overwrites some vanilla interfaces, so adding these rules shouldn't have many unforeseen consequences. The only thing we may want to check first is if the load rule placing iNeed.esp after SkyUI is really necessary. It was added in #747 & appears to be necessary, but it may be worth double-checking, possibly with iNeed Continued as well.

@sibir-ine sibir-ine self-assigned this Feb 9, 2023
@sibir-ine sibir-ine removed their assignment Apr 27, 2023
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

1 participant