Skip to main content

Torrent-Specific settings

Use Settings → Torrent Specific for torrent reuse and rehash scheduling.

FieldDefaultEffect
Prefer max 16 torrentOffDuring torrent-client search, prefers a validated reusable torrent whose piece size is at most 16 MiB.
Rehash cooldown0Waits this many seconds after reusable-torrent submissions finish before starting rehash-dependent uploads.

Prefer max 16 torrent affects selection among reusable client torrents; it does not impose a piece size on every newly generated torrent. A negative rehash cooldown behaves as zero.

Compatibility field

Mkbrr threads remains in the schema but has no current runtime reader.

Verify the change

Save, prepare a source with known torrents in a configured search client, and inspect the selected reusable torrent. Rehash cooldown is observable only in a real upload plan containing both reusable and rehash-dependent tracker submissions.