Add new launch flag ("binary-dir") & Change the path for loading mods #1439
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 updates the old code from using
(m_tempDirName / m_metadata.getBinaryName()
to usingthis->getBinaryPath()
, which essentially does the same thing.This also adds a new launch flag titled
binary-dir
Example usage:
--geode:binary-dir="Z:\home\fire\custom-binary-directory"
All mod binaries will be loaded from that directory, rather than
geode/unzipped/[mod id]/[mod id].dylib
as an example.