After the 10th @r, even though MorePages says:
MorePages:
Find: >Next →</a>
Result: Found
Current Counter: 0
Current Page: http://btdigg.org/search?info_hash=&order=0&q=test&p=0
Next Counter: 1
Next Page: http://btdigg.org/search?info_hash=&order=0&q=test&p=1
All debugger buttons deactivate/turn grey.
Similarly, without the debugger only 10 results are found.
As far as the Magnet links, I understand about scraping them. I was mostly checking to make sure setting the seeders/leechers to 1 was the preferred scripting for that. I thought maybe BC recognized a link as Magnet and automatically did something with the seeds/leeches so put(1) isn't necessary.
Gotcha.. Ok, so sound like there is a bug.. But I'm not sure yet how to reproduce.
Can you check your settings..
What do you have set for max results per source?
and fetch results from multi pages is checked/enabled..
Oh, and the instance of bit che being used for testing is unlocked for Plus access?
And I see what you are saying for the magnets... I like your thought, possibly we force $seed/$leeches set to 1 if the script is silent on those values... That way, if scripting for a magnet only site, you could leave out those script lines to simplify slightly.. I'll look at it. My concern for doing something automatically when it detects a magnet is, what if script expects magnet, ommits S/L, but a torrent is loaded.. Then S/L would be 0.. And the auto filter comes into factor. So, at least initially, I think we could improve by doing a solution based on the script purposefully omitting S/L, and always set to 1?