Update NUSGet Usage Directions - #192
Merged
Merged
Conversation
These images are NOT used anywhere in my updated version of the guide, but not having them breaks builds for translations that haven't been updated
grunt22fox
pushed a commit
that referenced
this pull request
May 16, 2026
* cIOS: Add NUSGet Instructions for offline setup * Adapt changes from #192
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.
Shortly after being added to the guide, NUSGet v1.5.0 was released and added a button to directly open the directory that it downloads to. This PR changes the directions for using NUSGet to leave the default download directory and use this button to open the directory rather than changing the download directory to where the NUSGet executable is located. This also makes things slightly clearer for macOS and Linux users, because depending on how NUSGet is installed (such as actually being in
/Applications/on macOS), using the same directory as the executable for downloads might not be desirable.I have updated all relevant screenshots to show NUSGet v1.5.0 so that the open output folder button is visible in any screenshot of the interface, and added a step pointing out the button. I tried to maintain the same writing style where I made changes to the steps, but I will reword things if necessary.