I little background first. I'm hard of hearing so I need English subtitles for everything. So automation tools such as Sonaar and Couchpotato are not that useful for me since I've found them to be unreliable for subs (too many subs are out of sync/missing). I find I have much more success with subs when I manually check the nfo's on my indexer(s) to make sure they have english subs included, before I grab the nzb's. I don't really find this time consuming. Excepts when incomplete downloads in NZBGet occurs (due to usenet provider problems), and I have to go back to the indexers again, re-do the same search(es) over again, try to browse and find (yet another) alternate nzb, and manually add it to the NZBGet queue. This get's a little time consuming and frustrating.
To make my life easier, is there a way to manually add one (or several) alternate nzb's to a item already in the download queue. For example, right click on an item in the queue and select "Add alternate nzb" for this particular item, browse to the alternate nzb's I want from my local disk, and click "add". I was thinking that the alternate nzb's could be added to a kind of "sub-queue" list that is visually located right indented and under the original item that was right clicked. This way, if the first (original) nzb fails to download, NZBGet would try the next alternate nzb from the sub-queue list. If this alternate nzb fails as well, NZBGet would try the next alternate nzb in the sub-queue list, and so forth down the list of the sub-queue, until a successful download occurs (pausing the rest of the items in the sub-queue list) or all alternate nzb's have been attempted. After this process in the sub-queue completes, NZBGet would move out of the sub-queue and back into the regular queue to complete the next task on the list there.
Maybe there is already a NZBGet script that does this? Any help would be greatly appreciated, thanks!
Note: my alternate nzb's usually always have the same content, but they would not necessarily have the exact same nzb file names (i.e., because each nzb would probably be from a different release group or post), so I'm skeptical that a dupe check command would be useful here. But I could be wrong.