Exiled Bot Public Alpha v0.3b

[benkom]

nice i will try it later

[moustache]

for some reason, the bot has a hard time selecting the correct waypoint for me
My config file:

[general]
enable_game_automatic_restart = true ; Define here if you want to game to automatically restart when closed. Moreover, true will start the game unpaused and false will start the game paused.
enable_autologin = true ; If you want the bot to login automatically
start_bot_paused = false ; If you want the bot to start paused or not
character_to_use = 0 ; Define here which character you want to use in the character selection screen (default : 0, top character).
last_act_unlocked = 3 ; Last act unlocked
last_difficulty_unlocked = 1 ; Last difficulty unlocked (1 = normal, 2 = cruel, 3 = merciless)

zone_to_clean = sarn_slums ; Here write the name of the zone that you want the bot to clean. You have to write it /!\THE SAME WAY/!\ as it is written in
; the coordinates.ini file (without _x or _y ofc). For now, the bot can only clean one zone per run.
zone_to_clean_act = 3 ; Important!! you have to give the act which the zone belongs
zone_to_clean_difficulty = 1 ; Set the difficulty desired (1 = normal, 2 = cruel, 3 = merciless)

; [bugged]monster_no_kill_timeout = 300 ; if the bot didn't kill anything during last 300s (default), next instance! (set to 0 to disable this feature)
run_max_time = 720 ; maximum time (in seconds) allowed per run. when timer is reached, exit to login and start again

I'm trying to run in sarn_slums normal act 3 but it cannot choose the waypoint from camp.

Edit: Nevermind, I edited the coords file to fix it; that said, would the bot still work if the game was 1920 x 1080 if the coords were changed.

[Kelvinchan]

for some reason, the bot has a hard time selecting the correct waypoint for me
My config file:



I'm trying to run in sarn_slums normal act 3 but it cannot choose the waypoint from camp.

Edit: Nevermind, I edited the coords file to fix it; that said, would the bot still work if the game was 1920 x 1080 if the coords were changed.

the bot can fully work?????still a lot bug???

[moustache]

the bot can fully work?????still a lot bug???

I don't understand your question. I repaired the bot by fixing the generated coords file and asked the dev if I could reconfigure the coords file to change the resolution the bot runs at.

[Huaojozu]

Hey there, first up - thanks for your work. While it can use some more polish to make the experience smoother, it does the job just fine right now. Now for some questions/suggestions.

1) The bot stopped working with 0.11.1 patch today. It can log in just fine but cannot select a character nor can it navigate from town to the waypoint portal.
2) Several times, the bot would try to create a new instance by clicking as low as possible on the screen (where the "NEW" button would be, if all the instances were created). Then it would move on to the second to last button and so on. This would guarantee that it would always create a new instance. However, it would also often just simply click on the second button in the order, which would only create a new instance under certain conditions. Right now, the best place to farm with this bot in my opinion is City of Sarn (because I can easily configure AutoHotKey script to click in such a way as to get the bot to the end of the map even if it cant find any monsters by itself). However all my runs last around 2 minutes, which means I have to enter the same instance around 4 times (due to bot behavior with the instances) before farming a new one automatically.
Can I suggest that mod always clicks lets say three times at the location where the "NEW" button would be if the select instance screen is completely filled up? Then if it didnt get anywhere (which would mean the screen is not filled up), it would click three times at the location where the "NEW" button would be if the select instance screen was missing only one instance at the bottom (so almost filled up). It would continue in this manner until it gets to the very top instance.
As I have said, the bot seems to do just that occasionally but definitely not too often.

I can work around all the other issues with AutoHotKey so if you could please fix the bot for 0.11.1b and make sure it always selects a new instance, that would be awesome. Thats really all it needs to become a viable farming tool at least in the City of Sarn (and Forest is nice too). I have already farmed 2 Exalteds this way and loads of support gems.

[username1001011]

Right now, the best place to farm with this bot in my opinion is City of Sarn

I had problems there that the bot suddenly stopped at character selection screen

(because I can easily configure AutoHotKey script to click in such a way as to get the bot to the end of the map even if it cant find any monsters by itself).

Care-2-Share?

However all my runs last around 2 minutes, which means I have to enter the same instance around 4 times (due to bot behavior with the instances) before farming a new one automatically.

In the config.ini you can set the timeout of a game (unless bot chickens out first)

[masterpulha]

Really nice Bot, been using it for 2 days

Its not perfect, needs improvements to work on different type of maps, but cant complain.
I leveled for 59 to 69 in 1 day on the crossroads.

looking forward for next update

[Huaojozu]

Character Selection bug occurred only a few times for me. Pausing and unpausing the bot usually fixed it.

I use the AutoHotKey script for auto-flasks and chickening (I believe it is on this site too) and I just add this to the end:

F8::
Loop {
Click 400, 205
Sleep 500
Click 400, 230
Sleep 500
Click 50, 50
Sleep 2000
Click 750, 50
Sleep 10000
Click 50, 50
Sleep 3000
Click 50, 550
Sleep 10000
}
return

It works quite nicely for City of Sarn. Basically it goes top-left, top-right, top-left, bottom-left. Top-left is the general direction that the map is ALWAYS structured (unlike Forest which is less predictable) and the other directions are for getting around obstacles. I also use Leap Slam to prevent getting stuck. The first two clicks are for clicking on RESURRECT (just in case, to save time) and on I think RESUME in case the AutoHotKey script interrupts the exit to log-in screen while the escape menu is active.

I know about the timeout, and I have it set to 150. However for me, the bot almost always clicks on the second topmost instance. Since I can clear it in two minutes, its not enough time for the first instance to disappear (that takes 8 minutes so about 4 runs). That means the bot enters the same instance that it cleared on the previous run.

[Eminotic]

I had problems there that the bot suddenly stopped at character selection screen



Care-2-Share?



In the config.ini you can set the timeout of a game (unless bot chickens out first)

No reason to use the config, just use the GUI.

@Huaojozu, pretty common sense to do city of sarn. So I agree. Also, it's no shock that the bot stopped working after a big patch. I never have issues with new instances, so I can't comment on that really, besides something is most likely wrong with your settings.

[Huaojozu]

I never have issues with new instances, so I can't comment on that really, besides something is most likely wrong with your settings.

What timeout setting are you using? Also what are your instance setting in coordinates? I dont remember ever changing those but it is possible. Mine are

[instance_selection]
first_instance_x = 130 ; first button when creating new instance
first_instance_y = 185 ; first button when creating new instance
next_instance_offset_x = 0 ; offset to jump to the next button on instance selection screen
next_instance_offset_y = 52 ; offset to jump to the next button on instance selection screen

[Eminotic]

What timeout setting are you using? Also what are your instance setting in coordinates? I dont remember ever changing those but it is possible. Mine are

[instance_selection]
first_instance_x = 130 ; first button when creating new instance
first_instance_y = 185 ; first button when creating new instance
next_instance_offset_x = 0 ; offset to jump to the next button on instance selection screen
next_instance_offset_y = 52 ; offset to jump to the next button on instance selection screen

Same as yours, I set my stuff to reset every 90-120 seconds, i do this on hardcore, so I usually don't have to chicken logout since it's a tanky build, so that could be what's making yours overlap? Instances reset 8-15 minutes apart, I have like 7 slots or so before the screen gets full, so it's usually reset the first 1-2 by then

[Huaojozu]

Yeah, my problem is that the bot always selects the second instance, even though there are 3 instances already, so it should click on the 4th slot from the top. As far as I can tell, something is either making the cursor go to the wrong coordinates or telling the bot that only one instance is open. Chickening cannot be the issue since I ran the bot with a lvl57 character in Cruel Sarn and disabled chickening altogether at one point. Do you think that something like this might work:

1) Telling the bot to start at coordinates that would apply for the bottommost instance (which is always a new one) via the first_instance parameters.
2) Telling the bot to climb up in case less instances are available via setting the y offset for next instance to a negative number (most likely -52).

It should work in theory, though I am not sure if the code can handle negative numbers. Will test it out once we get updated offsets. On that note, I noticed that the autoflask script in AutoHotKey can search for new offsets automatically if none are inputted beforehand by simply deleting (or commenting out) the line with the old offsets. Shouldnt something similar be possible for this bot as well?

[username1001011]

No reason to use the config, just use the GUI.

Unfortunately the current gui has two bugs:

1) City of Sarn is not listed
2) if you change the act of the zone you want to bot, that's not auto-adjusted in the config

[Eminotic]

Unfortunately the current gui has two bugs:

1) City of Sarn is not listed
2) if you change the act of the zone you want to bot, that's not auto-adjusted in the config

Oh i never noticed that, I just cut up the config file to only do what I want it to do, since I don't need anything but like 2 different maps

[vlsf1980]

This bot really work well until yesterday, after the patch, the curser will always point south-east and will not go onto the waypoint. Even after manually teleport to a map and start-bot, it will just move in that direction.

I using default setting. Wondering if anyone else having this problem. Thanks.