summaryrefslogtreecommitdiffhomepage
path: root/data/shatter/Campaigns/04/Scenes/M1-New-Job.def
diff options
context:
space:
mode:
authorAki <please@ignore.pl>2022-08-09 23:52:11 +0200
committerAki <please@ignore.pl>2022-08-09 23:52:11 +0200
commita1bb81360e7f1964498de82dfc0c3f6ff3037182 (patch)
tree64ef562cf7bbcb41d10a0e7d1bc3ec59dce1448c /data/shatter/Campaigns/04/Scenes/M1-New-Job.def
parenta88cfc3a560f372f5abcff09fcbf8393c1f0bd55 (diff)
downloadstarshatter-a1bb81360e7f1964498de82dfc0c3f6ff3037182.zip
starshatter-a1bb81360e7f1964498de82dfc0c3f6ff3037182.tar.gz
starshatter-a1bb81360e7f1964498de82dfc0c3f6ff3037182.tar.bz2
Added methods to inspect blocks in the archive
This actually yields predicted tendency to leave a single unused block at the start of the archive in case where directory starts to need more blocks and none of new files can fill it in. Interestingly it also shows a long sequence of unused blocks just before the directory that is right at the end of the archive. The cause for that can be pointed out in original implementation of FindDataBlocks method.
Diffstat (limited to 'data/shatter/Campaigns/04/Scenes/M1-New-Job.def')
0 files changed, 0 insertions, 0 deletions