1.2.1
Added: Credit Save Mode.
Added: [Credit save] to Credit Log
Added: Auto stop/start
Added: Log reset
Fixed: Old image bug
Fixed: various small things
Fixed: Runtime error 3
Hia;
Another update; but atleast this one has something useful added into it; overall; it should end up saving your credits; as credit save mode does whats explained below; and old image bug (thats now fixed) didn't always use a queued saved result.
Credit Save Mode:
Some of the time the response we get back from CaptchaTrader isn't a 90% match to the image we submitted (IE: The person types only one word)... Strictly speaking this isn't allowed by CaptchaTrader; As users are /suppose/ to type in the whole two words and aim to enter at least 90% of the captcha (At-least get a accuracy rating of 90%+).
When we get a response that contains only one word; the human typer is at fault as he should've typed both words.... So what "Credit Save Mode" does is.... If the response we get back from CT isn't two words long; It responds to CT and says "Hey; That last result was wrong... Gimmi my credits back...." - But it still sends that /one word/ to kBot in the hope that Dark Orbit accept it and clears the captcha.
The aim of this is; to maximize the amount of captcha we can fill with our credits; and let our credits last longer; so we don't have to spend more and more money, or waste more and more time entering them to earn credits.
Example:
iptedes" (submission) refunded 1410 (+10) 50 seconds ago
"iptedes" submitted from reCaptchaTrader 1400 (-10) 50 seconds ago
( Seen at:

)
By default this setting is turned off.
Notes: I /think?/ they maybe a error somewhere in the credit save code? It's running around the clock here; so hopefully any problems in it will be pin-pointed fast.
Auto stop/start:
I noticed once the last thing in the log was 35 min ago; while an image was shown; no errors; no nothing; A bit clueless as to why it halted; I had same ver running on two machines, only one had the fault. Changed a few things in the code to hopefully stop that; But I've also added that: Every 30 minutes it stops/starts itself - This should allow the program to function over long periods of time; even if the problem is still there.
Log reset:
The program resets the log and debug log every now and again; I discovered the "Box" has a text limit; so once that limit was reached; we' would run into an error... unsure if anyone other than me got that error; but its solved
Runtime error 3:
Tricky bug; I'm not 100% sure why this is caused; Program ran for 5 hours once before it came last night... Another its (stil) running after 7 hours; traced the error to my ExtractText function; so I suspect its CT related; where CT does something the program isn't expecting. If this error occurs; It'll write to ErrrorLog.txt that'll show me which strings it tried to work with; return a blank string and (hopefully) the program will continue to work as normal. Being that it can take 5-6 hours to trigger this error; This isn't really a 100% tested fix
- Everythings other than runtime error 3 has been tested for a period of 7 hours; so bit of luck this should be more stable than other releases
Download:


@maximo_javi
PM me the jpg images in programs folder (After its got the problem; while debug mode is on)
@Zimmbo
To be honest; I'm clueless; It /should/ have created other jpg if in settings; "Debug" was ticked. Double check that option is ticked?... If that fails; I'd only suggest making a temp limited user on the server; and PM'ing me a way to connect so I can play about myself to see if I can solve the problem; but I suspect debug isnt ticked in settings, so try that first
regards
Tw