-
Content Count
378 -
Joined
-
Last visited
Everything posted by stef
-
its outdated (last update was 1.03)
-
desperately in search of
-
diso an update aswell, thx or a guide how to fix the memory address, that would be even better
-
well, max run time helps this case if it reaches that point the bot will log out
-
ye, as u can see inside the .au3 file. try to make a pic from the login button resources/login.bmp
-
the zone changer script from immo has multi stashing support, may take a look there
-
thats the only way to run ur bot minimize since it requires mouse & keyboard action. so you able to run it on your virtual machine while continue to use your computer as normal.
-
its no bug, multi stashing isn't supported yet. so its working as intended http://exiled-bot.net/community/index.php/topic/814-upd-v17-automatic-zone-changer-incl-stashtab-changing/ this script has stash tabbing included, may give it a try
-
i know ofc but the coords.ini is exactly for these type of things. if there is an issue with clicking on the wrong spot, you are able to fix it with different coordinates in most cases . so just put distance 41 or 42 instead of 40, restart the bot and see where it clicks. just play with the coords a bit, until the bot clicks the right slot.
-
go to Configuration\default and edit the coordinates.ini. only shot u have to make it work ; X coordinate of the first character in character selection screen (800x600 coordinates by default) first_character_x=632 ; Y coordinate of the first character in character selection screen (800x600 coordinates by default) first_character_y=110 ; distance between each character in character selection screen (800x600 coordinates by default) character_selection_offset_y=40 i dont know where it clicks right now, but may try to play with the distance a bit to make it work for all slots.
-
hm, what exactly does stuck at waypoint means? does the bot stuck on every run or only on 1 x occasion ? (which happens on every bot sometimes). e.g. running too far and not being on the waypoint. after he timeout'd bot will work again. if u unlock a new act/difficult you gotta change the last area/difficult unlocked in the gui. but guess u have done that already
-
yep, i guess so garena is elite only, so you probably used the "normal" version.
-
pretty much everything, mixing it up is the key to success imo (= more human like behavior)
-
no need to worry about that subject tbh its even more likely that they will detect the behavior of your "bot" sooner or later (when ggg staff people sitting in town and ur bot is doing strange stuff at the wrong time etc.).
-
What movies have you watched recently?
Walt replied to topic's stef in Exiled bot - Off topic forums
Hobbit in cinema yesterday. decent movie overall i prefer shows > movies like breaking bad, homeland, sons of anarchy, walking dead etc. they are just better -
yep true, it has sth. to do with scrolls. but it even happens sometimes with 40/40. I can't reproduce the problem 100 %. this definitely needs to be looked into, its a major issue sometimes. a partly solution to the problem is letting the bot ignore scrolls ...
-
true its running flawless here. not 1 error so far from autopoe great job
-
no. 8
-
kk cool, nice to hear apart from this error, it worked fine tho. will try the new version
-
same here :/ sometimes it happens with 10 min running, sometimes it last 1h.
-
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
-
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