The rewrite cuts off when I use a bracket within a bracket.
Example:
{This is an {example|sample} sentence|I'm providing an example} regarding the rewrite feature.
One Weird Output:
sample sentence regarding the rewrite feature.
Any way to fix this?
How did you come up with that spun syntax? It doesn't appear it was generated in PAR but rather by hand.
Ok a few comments about the spin syntax, ScrapeBox does up to 3 basic nested levels plus it handles multiple separate comments. This means you can generate "more" variations with ScrapeBox for a simple comment than you can do with PAR for an article.
Why not just do this?
This is an {example|sample} sentence regarding the rewrite feature.
I'm providing an example regarding the rewrite feature.
These are all issues from the internal spinner. Sbox spinnner is by far not capable to handle PAR multiple nested spun text for example:
{{Thanks|Thank you} for taking the {time|effort} to {discuss|talk about} this|{Great|Good|Hot} {post|posting|blog post|blog posting|message} and {good|great|nice} you {address|talk about} this|I was {reading|studying|checking} your {post|message|blog post|posting|blog posting}
this will cause text to be cut off in the comment preview. As was mentioned in the previous quote.
PAR chokes in this also, there's an uneven number of brackets meaning something not closed off. Removing the very first { and both tools still choke and don't display it right.
With the spinner it will handle default PAR format, it will do 3 nested levels example:
This is an {{sample|example}|{test|trial}|demo|demonstration} sentence regarding the rewrite feature.
Works perfectly in both tools:
Given that ScrapeBox can use multiple rotating separate comments, each with 3 nested levels of spin syntax in them it can already post an infinite amount of comment variations.. I don't think it needs anymore.
Kobalt2 if you are still having problems after removing spin syntax that's either invalid, or beyond the limitations of the tool please submit me a support email and i will get it sorted.
Proxy Harvester seems still buggy Sweet,
As i mentioned in the release notes, the Proxy Leecher is still "Beta" it was implemented at 5am and i went to bed and it's a long way from finished.
You don't have to use it, i just thought people would like to have a play around with a new feature sooner rather than later.