[physfs] Getting every instance of overlapping files

Sik the hedgehog sik.the.hedgehog at gmail.com
Sat Aug 23 07:07:27 EDT 2014


Then load the archives in separate directories and handle the
overriding manually (using a wrapper function for opening files would
be helpful here).

2014-08-23 6:37 GMT-03:00, Haydn Harach <hharach at gmail.com>:
> Can't - I wont know exactly which files to load until run time (.map files
> can refer to other .map files, and that information wont be known until the
> player is in the .map).
>
>
> On Sat, Aug 23, 2014 at 3:10 AM, Sik the hedgehog <
> sik.the.hedgehog at gmail.com> wrote:
>
>> Then just take the second option (load .map files when you just mount
>> the archive, leave the .png files for after you've mounted
>> everything).
>>
>> 2014-08-23 5:33 GMT-03:00, Haydn Harach <hharach at gmail.com>:
>> > Problem is, I want .png files to be overwritten, but not .map files.
>> When
>> > the mod is loaded initially, it's just a big .zip archive, there could
>> > be
>> > .png or .map files within it's sub-directories.
>> >
>> >
>> > On Sat, Aug 23, 2014 at 2:13 AM, Sik the hedgehog <
>> > sik.the.hedgehog at gmail.com> wrote:
>> >
>> >> Two options:
>> >>
>> >> - Mount them in separate directories and just deal with the fact (I
>> >> ended up doing this to prevent mods in my game from overwriting
>> >> configuration and savegame files).
>> >>
>> >> - If the data is going to permanently stay in memory (i.e. you won't
>> >> need to read the files after initially mounted), then load the files
>> >> the moment you mount them (before mounting the subsequent archives).
>> >> The obvious upshot is that if you want you can unmount them after
>> >> loading (since the data is in RAM already).
>> >> _______________________________________________
>> >> physfs mailing list
>> >> physfs at icculus.org
>> >> http://icculus.org/mailman/listinfo/physfs
>> >>
>> >
>> _______________________________________________
>> physfs mailing list
>> physfs at icculus.org
>> http://icculus.org/mailman/listinfo/physfs
>>
>


More information about the physfs mailing list