Is there already an issue for your problem?
NZBGet Version
v26.1-testing
Platform
All
Environment
Debian 12
26.1-testing-20260223
Current Behavior
If you set ParCheck to "Force" and use DirectUnpack a (successful) download which has broken/missing par2 sets instead gets the NZBPP_UNPACKSTATUS of 0 (skipped / errors due to par check)
Expected Behavior
a successful DirectUnpack job should set NZBPP_UNPACKSTATUS to 1 and not be overwritten by the subsequent par2 check
Steps To Reproduce
set ParCheck: Force / Unpack: Yes / DirectUnpack: Yes
Logs
important part:
Sun Mar 01 2026 15:09:20 INFO Unrar: All OK
Sun Mar 01 2026 15:09:20 INFO Direct unpack test_nzb successful
Sun Mar 01 2026 15:09:21 ERROR Par: Main packet not found.
Sun Mar 01 2026 15:09:21 WARNING Could not verify test_nzb: par2-file could not be processed
Sun Mar 01 2026 15:09:22 WARNING Skipping unpack for test_nzb due to par-failure
Extra information
This only happens if ParCheck is set to Force. when it's set to Auto the same nzb is downloaded, DirectUnpacked and correctly marked as successful.
I'm assuming this is because we skip the whole par2 check -> none available -> skip unpack -> mark as failed
Is there already an issue for your problem?
NZBGet Version
v26.1-testing
Platform
All
Environment
Current Behavior
If you set ParCheck to "Force" and use DirectUnpack a (successful) download which has broken/missing par2 sets instead gets the NZBPP_UNPACKSTATUS of 0 (skipped / errors due to par check)
Expected Behavior
a successful DirectUnpack job should set NZBPP_UNPACKSTATUS to 1 and not be overwritten by the subsequent par2 check
Steps To Reproduce
set ParCheck: Force / Unpack: Yes / DirectUnpack: Yes
Logs
important part:
Extra information
This only happens if ParCheck is set to Force. when it's set to Auto the same nzb is downloaded, DirectUnpacked and correctly marked as successful.
I'm assuming this is because we skip the whole par2 check -> none available -> skip unpack -> mark as failed