Fix client_config.json not used in packaged builds#140
Open
pyrogamer0209 wants to merge 1 commit into
Open
Conversation
now reads the client_config file correctly in packaged games
|
The important changes are in |
This file contains hidden or 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
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.
Normally you put the client_config.json next to the LeapC.dll and it is used automatically. This works in the Editor but not for packaged builds.
The provided solution mimics the expected behaviour. The LeapWrapper checks the expected path in the Plugin's Directory and initializes the
server_namespacewith the file content. If no file is given the default behaviour is used.We tested it with: