Resolve BepInEx plugins being destroyed #240
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MrPurple6411
reviewed
Jun 2, 2021
…ues UNIX users have.
MrPurple6411
approved these changes
Jun 2, 2021
…ABLE, retaining QMod init time parity with QMM 4.1.4
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to resolve the issue where BepInEx plugins are being destroyed on game launch - it addresses this by distributing a default BepInEx.cfg file that sets the entrypoint for BepInEx plugins to an appropriate starting point, i.e. after the wipe.
Additionally, since the initialization of QMods was moved from QMMLoader into QModPluginGenerator to workaround this issue, I have moved the initialization of QMods back into QMMLoader.
Installer builds
Vortex builds
QModManager_BZ.EXP.zip
QModManager_BZ.STABLE.zip
QModManager_SN.EXP.zip
QModManager_SN.STABLE.zip