I do this and the appeals seem to be a complete lottery. I've had a handful of accounts denied on their first appeal attempt and others that have gotten unbanned 3+ times.
@Token Running into a bug while chain questing (using a profile) to do Jungle potion. I have to restart my client in order for the script to do the quest.
[REDACTED BY STAFF] If you want to pay me back that's more than fair however I lost 15 accounts.. 8 of which were Vyre accounts so $60 each... 1 was a completed demonic build so $110-120 for that.
Disputed member: [member=308566-natever]
Thread Link: N/A Discord server + Auto delivery webshop
Explanation: This guy sold me 15x 40/40/40 melee accounts on the 17th of March and changed the passwords to the ones that I hadn't changed today.
Evidence:
[STAFF CHECK HIDDEN]
One transaction was for 10 accounts and the other was for 5. The screenshots here show one of my customers complaining to me that his account was hacked. I then checked the text file that nate delivered on the 17th of march and sure enough my customer's account was part of that batch.
Gif of discord UID:
@Khaleesi Would you be able to add CLI support, stop on dragon defender and enable auto retaliate when it's off? When using any special attack weapon while your auto retaliate is disabled will cause you to get beat to death.
There's no bulk proxy import feature for OSbot however you use CLI to start your accounts through .bat files.
Example:
"java -jar "Osbot.jar" -dismissrandoms -allow lowcpu -autologin -proxy 123.123.123.123:4444:username:password -bot Fisherman2016@hotmail.com:Password123:0000 -script 1097:fxAccountBuilder -world 301"
-autologin will automatically login to Osbot so long as you've logged into Osbot manually once.
-allow lowcpu starts clients in low cpu mode
-proxy format is IP:PORT:USERNAME:PASSWORD
-bot format is USERNAME:PASSWORD:BANKPIN
You must keep the .bat file and the osbot.jar in the same folder otherwise the clients wont start. Also notice in the .bat file the Osbot.jar is named "Osbot.jar" ... your jar file has to be named Osbot.jar otherwise it won't run. SOO when Osbot updates you have to delete the old jar file and rename the new one.
Best of luck