Thanks for the response. I will try that, but I don't like being forced to use the custom harvester when I purchased this plugin so that I can use the multi-threaded one.
I appreciate the suggestion, but I think the functionality to automate keyword export should be present in this *premium* plugin if it claims to be able to automate Scrapebox's behavior. I don't mind that I have to pay for it - I would gladly pay a bit more, as long as it can be useful to me. But it's not and I would be surprised if I'm the only one.
Sure I get what your saying, but do you realize the custom harvester is multi threaded same as the multi threaded harvester? Also the custom harvester uses a new thread system thats more effecient resource wise, it can harvest from 5+ times as many engines, it offers more options in the way of proxies, auto refresh, and you can run the proxy retries up to 99 instead of only 20 (with the multi harvester).
Running proxy retries up will make the harvester retry more proxies for your keywords so they don't get skipped. So overall it seems from every angle possible that the custom harvester would work better and more effeciently for you then the multi harvester. I mean it seems like extra work and doing it the hard way to do it he way you want to. Just my 2 cents.
Also the custom harvester is the latest in "the evolution of scrapebox harvesters". They started single, moved to multi and then moved to custom. It wouldn't surprise me if they kill off the single and multi harvester as they aren't needed and the custom does everything the others do, and does it better plus more, with the one exception of exporting uncompleted keywords. At that is subjective as if a keyword is completed in one engine and uncompleted in another then it gets exported as uncompleted and your redoing work and wasting time. Its not pheasible to have this feature in the custom harvester just due to that reason with 20+ engines.
Anyway, I say all that because of this one simple principal about scrapebox and any other program that I have learned and that has helped me incresingly make more money. Just because I have been doing something one way doesn't mean its not better to try and learn to do it differently. Often times I have people ask me questions or show me their methods and I realize I can adopt or learn from that and do it better. I used to avoid it and just do my way and stick with it, but I learned I was leaving production and effeciency on the table and at the end of the day I made less money. So I changed and continue to constantly. Problems, such as your having, when I have them, I hate them in a way, because I just want stuff to work, which Im sure you can sympathize with.
But more often then not, at the end of the day, the problem forces me to ask myself or others questions and I learn something new and learn how I can do something quicker, more effecient, something new etc... and all that results in me having more time and making more money for the time spent. So while it seems that your having a problem and you want scrapebox to build in a feature to the automator, its probably better to stop and look at what options are available and see if you can't change your method, which will eliminate the problem of needing to export keywords and thus save you time, hassle and work and ultimately result in more production which I would presume will make you more money.
I can't tell you how many times I have had someone tell me they wish there was a feature to do x, y or z so they could solve problem A, and when we talk it out, they can use exisiting functions to eliminate problem A in the first place, and not need those other features, which in turn saves them time. Just they way I think, its of course up to scrapebox to add or not add the feature, not up to me.
Matt