Bill of materials to be done before starting this ticket:
awareness of #370
Have 500 maps/games in data folders. Get a new engine. Run a startscript with some specific map/game (snippet):
gametype=Zero-K $VERSION;
mapname=Adansonia v4.1;
Now engine will scan all the 500 archives to figure out which one contains "Zero-K $VERSION". Maybe it's splinter_faction_v1.28.sd7? Maybe it's testmod_debug.sdz? Maybe it lurks in maps/speedmetal_final.sd7? This takes a while.
At some point it discovers that "Zero-K $VERSION" lives in ZK.SDD, which is extra frustrating because I knew that all along.
The request is to make the scan less bothersome. Note that each of the below looks independent so you don't need to choose one.
stopping the scan when the archive is found would probably be decent, IF further search is a no-op for purposes other than building the cache (I am not sure if it is a no-op. For example what if a duplicate - different file, same archive metadata - is found?)
being able to specify an archive via file path (instead of via game/map name) such that the engine doesn't need to look everywhere would be decent.
the cache could be per content folder as described in #370.
Bill of materials to be done before starting this ticket:
Have 500 maps/games in data folders. Get a new engine. Run a startscript with some specific map/game (snippet):
Now engine will scan all the 500 archives to figure out which one contains "Zero-K $VERSION". Maybe it's
splinter_faction_v1.28.sd7? Maybe it'stestmod_debug.sdz? Maybe it lurks inmaps/speedmetal_final.sd7? This takes a while.At some point it discovers that "Zero-K $VERSION" lives in
ZK.SDD, which is extra frustrating because I knew that all along.The request is to make the scan less bothersome. Note that each of the below looks independent so you don't need to choose one.