Accepting only first entry after entries sorted?

@omnigamer wrote:

Hey all, apologies if this is redundant or covered elsewhere but I've got a usecase that I can't seem to configure quite right: I'm sorting the output entries from my input plugin according to various criteria, and I'd like to just accept the first result, reject all the rest, and never see those rejected results again. The closest I've gotten with my filter steps of my task are:

        seen: local
        quality: 1080p bluray h264
        sort_by_weight:
            - field: 'torrent_seeds'
              weight: 50
            - field: 'torrent_snatches'
              weight: 5
        sort_by:
            reverse: true
        limit_new: 1
        accept_all: yes

After this filter step, I remove the discover value from the list which generated it, which ideally prevents flexget from searching (and downloading) it again. However, since I'm using the limit_new plugin to only accept the first value, the values rejected by it are added to the backlog, and this causes my filter block to simply add the next best result on the next run of the task.

Is there some way to handle this sort of thing that I'm not seeing here?

Posts: 5

Participants: 2

Read full topic