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 allows limited manipulation of the search path without unmounting/remounting to get mounts in the right order.
It makes negligible changes to the API, repurposing the existing "appendToPath" parameter to
PHYSFS_mount*
and handling typical "flag" values (0, 1, -1) in such a way that current programs should have no change in function. An int is added to eachDirHandle
to store the mount's priority for later comparison.I had a use case in mind when I initially wrote this, but the specifics are lost to memory (that was almost 3 years ago). Something that comes to mind is dynamically mounted DLC and UGC: one might mount UGC at a high priority (say 5), so that it overrides DLC at priority 10, which in turn overrides base content at priority 20. If a new DLC package is mounted mid-game, also at priority 10, it won't inadvertently override mounted UGC.