Account for dependencies when deciding what maps to cook #47
Labels
bug
Something isn't working
cooking
Related to mod asset and Highlander cooking
incremental
Rebuilding does extra or not enough work.
Since switch to the DLC cook (#46) we need to figure out which maps are dirty and are in need of recook ourselves. Currently this logic only considers the map file only, ignoring the dependencies since we don't know what they are (except for collection maps, where we do know the, at least the direct ones).
One approach would be to have the mod devs manually specify the dependencies. This is simple for X2MBC, but error-prone for mod devs. A better approach would be to automatically infer the list of dependencies. If only there was a way to do it...
What's even better, is that it also lists transitive dependencies, not only the direct ones - in this case the map itself only referenced
TEST_mat_CI_2
, while an object there referenced something inUILibrary_StrategyImages
. This command also accepts multiple packages/maps to check in one invocation.I suggest the following workflow:
When a map is dirty/(re)cooked:
PublishedCookedPCConsole
)When deciding whether a map is dirty:
Of course, the output of the command will need to be parsed and cleaned - we don't want to check the timestamps for:
The text was updated successfully, but these errors were encountered: