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

[Feature Request] Add the option to compile with a separate ModOrganizer.ini #2597

Open
aljoxo opened this issue Jul 10, 2024 · 3 comments
Open
Labels

Comments

@aljoxo
Copy link

aljoxo commented Jul 10, 2024

Is your feature request related to a problem? Please describe.

N/A

Describe the solution you'd like

I would like the ability to make it so that the ModOrganizer.ini that Wabbajack uses in the compile is different from the developer's

Describe alternatives you've considered

Manually changing the ModOrganizer.ini before and after compile in order to ship with settings that are more desirable for users.

Additional context

This request stems primarily from the EXPERIMENTAL ARCHIVE PARSING feature of MO2. While this feature is nearly essential for development, especially when working with a large amount of BSAs like I do, it massively slows down MO2's VFS system (increases boot times, game launch times, any refresh, etc). This feature is not essential for most users, and many would benefit from it being disabled on their end.

Discussion in Wabbajack lounge channel that may have additional context:
https://discord.com/channels/605449136870916175/782016989681942538/1260220659762724875
https://discord.com/channels/605449136870916175/782016989681942538/1260223825996681288
https://discord.com/channels/605449136870916175/782016989681942538/1260358390513799219

@JanuarySnow
Copy link
Contributor

Looked into this just now and its not as low-hanging fruit as I thought. I thought maybe that modorganizer.ini was handled as a special case by WJ and preserved and recreated, I assumed I could just intercept that case and swap it out with an overrided optional ini instead when it is first accessed.

But no - WJ reads some values from mo2.ini and then just treats it as if its any other file to be hashed, so itd need some special handling thatd feel a bit ugly to replace the modorganizer.ini with the overriden version after installation somehow...

@aljoxo
Copy link
Author

aljoxo commented Jul 21, 2024

Rip

Well this is a relatively low priority feature request. If someone could eventually get around to it that would be nice, but it's not the end of the world.

Copy link

Marked as stale due to no interactions in the last 90 days. If the issue still exists, please provide any possibly still needed information or excuse the devs for not getting around to addressing this issue yet. If this issue is still considered unsolved a dev will soon remove the stale tag from this issue.

@github-actions github-actions bot added the Stale label Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants