stef
-
Content Count
378 -
Joined
-
Last visited
Posts posted by stef
-
-
same here :/
sometimes it happens with 10 min running, sometimes it last 1h.
-
Once i got that too, i have no idea what is it... O.o
hm i figured it might be useful to run it via the *.au3 file, to be able see the code/line were the error occurs. maybe that might help to fix it, because it happens fairly often for me
-
got this error after the script run some time. seems to happen only in vmware.
any hints/solutions? thx
-
hm, the unlock code/email feature seems broken aswell. worked flawless with an aol email with the previous version.
tried it two times 5 min ago, and the script wrote weird things into the account/password input field.
will try again later if i got more time
false alarm, working now after deleting the .ini and resetup it again
mistake was on my side apparantly
-
nice effort, but u can easily use teamviewer for full control of ur pc
other than that i wouldn't mind having a different option
-
hm, the unlock code/email feature seems broken aswell. worked flawless with an aol email with the previous version.
tried it two times 5 min ago, and the script wrote weird things into the account/password input field.
will try again later if i got more time
-
I think it is because i changed Run to ShellExecute, i'll add a line to only use ShellExecute when the user want to start the poe with arguments. Also it's working for me, in VM and also in my computer O.o
Pushed a new version for you, please check out if it's working for you.
no, i can tell you exactly what went wrong, the .exe name from the bot changed from ExiledBot.exe to ExiledBot GUI.exe. quick rename of the bot exe fixes the problem.
other than that it works great. for a future realease i would request that auto poe doesn't minimize the bot and move it to a different position on windows (and open the status tab). its a pity to have such a nice status tab now, but bot is minimized if u use auto poe.
overall great work, thx
-
1
-
-
Is this what you all do? What's your way to avoid detection?
if ggg want to, they could basically detect everything. whether by trade window, guild stash or drop method
as some guys posted in the last few days untouched mule accs were banned also (assuming they tell the whole truth). so it isn't 100 % risk free to mule anyway.
-
A suggestion, do not use one of the free/public VPNs, there could be 50 people already using it for botting. And those IP's are flagged.
I have botted over a month 5 toons (6th starting yesterday). 3 on and 2 off, then 2 on 3 off, all from my home IP. I have traded with resellers and traded all my orbs (10000s of orbs and items) directly to my mule (which is a bot).
I know any second I can get banned, the only thing I think I maybe doing different is not using a public VPN.
this
its safer to bot with ur home ip than any vpn u didn't bought yourself
-
well, if you are botting you have to know the risks.
nothing can ensure you 100 % risk free botting (counts for pretty much every game), you only could minimize the risk to a smaller percentage (don't bot 24/7 etc. pp.)
-
ebenfalls ger
Auto PoE
in Exiled Bot Programming
Posted · Edited by stef · Report reply
kk cool, nice to hear
apart from this error, it worked fine tho. will try the new version