[Request] Maximum scan depth/file count option #189

New Issue

claunia · 2026-01-29T21:06:57Z

claunia commented

2026-01-29 21:06:57 +00:00

Originally created by @Deterous on GitHub (Dec 11, 2024).

Similar to #339 or perhaps in replacement of it, this is a request for a BOS option that limits file scanning to a certain depth from the initial scan folder path, or a limit on the number of files that will be scanned.

The motivation behind this request is the same as #339, to limit time spent scanning via capping how much "effort" BOS employs when scanning. This may persuade potential users to use BOS such as those who prefer to leave protection scanning off in MPF due to the current time spent scanning (e.g. coverdisc dumpers). For example in MPF, a default scan depth of 3 with a "full scan" option off by default, or even a custom maximum search depth option in MPF. Alternatively, it could limit BOS to scanning X number of files, with an option to remove the limit and do a "Full Scan".

The theory behind a maximum search depth (vs. bounded per-file scan time) is that protections/packers/etc are more likely to occur higher in the directory structure, while the mass of game assets that take up a large chunk of scanning time without any useful detections are more likely to occur at lower depths. The theory behind a file count limit is that it would work on folder structures that are deep but small.

Originally created by @Deterous on GitHub (Dec 11, 2024). Similar to #339 or perhaps in replacement of it, this is a request for a BOS option that limits file scanning to a certain depth from the initial scan folder path, or a limit on the number of files that will be scanned. The motivation behind this request is the same as #339, to limit time spent scanning via capping how much "effort" BOS employs when scanning. This may persuade potential users to use BOS such as those who prefer to leave protection scanning off in MPF due to the current time spent scanning (e.g. coverdisc dumpers). For example in MPF, a default scan depth of 3 with a "full scan" option off by default, or even a custom maximum search depth option in MPF. Alternatively, it could limit BOS to scanning X number of files, with an option to remove the limit and do a "Full Scan". The theory behind a maximum search depth (vs. bounded per-file scan time) is that protections/packers/etc are more likely to occur higher in the directory structure, while the mass of game assets that take up a large chunk of scanning time without any useful detections are more likely to occur at lower depths. The theory behind a file count limit is that it would work on folder structures that are deep but small.

claunia commented

2026-01-29 21:06:59 +00:00

@mnadareski commented on GitHub (Sep 7, 2025):

This has been partially addressed with the introduction of "no scan subfolders". It is also possible that this can be extended to limit the number of recursive steps (nested archives) that are scanned as well due to some recent changes. This item is not fully addressed, however, so it will be left open.

@mnadareski commented on GitHub (Sep 7, 2025): This has been partially addressed with the introduction of "no scan subfolders". It is also possible that this can be extended to limit the number of recursive steps (nested archives) that are scanned as well due to some recent changes. This item is not fully addressed, however, so it will be left open.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/BinaryObjectScanner#189