gwake87

Would adding randomization to the bot clicks possibly throw off detection? Would it be difficult to implement it and test it?

Thanks for the heads up man!

Hi exiled-bot community! It's been a year or two since I've played PoE. How has the bot been fairing? I'm thinking about reinstalling and picking back up. Are ban waves regular these days? And how has the bot progressed over the past year or so? I'm sure I can read all about it, but I wanted to see if anyone in the know could fill me in quickly and let me know if it's a good time to come back. I know ExileBuddy went dark a few months ago, and I'm wondering if that's lead to more third-party support here. Thanks in advance!

Sorry, all my bots were banned so I took a break for a bit. I forgot what the config was, but really just setup leapslam as a secondary skill and set a short delay on cyclone (maybe 50ms?) but no delay on leapslam. And have cyclone maybe a 9 priority and leapslam a 5. Then, if cyclone cant cast, that 50 ms delay will push leapslam to cast during the delay, and the bot usually unsticks. Play around with the delay, I think I used between 50 and 100ms usually. I also had my leapslam 5L with good support gems too, so the bot was probably 75% cyclone and 25% leapslam. Not ideal, but workable! Sorry I couldnt help more!

great post

I've made a few posts on cyclone over the past two or three months. I also run an lv85 cyclone marauder on Softcore and don't really have any issues, though I'm still too lazy to get Zana and run maps. He clears probably 200 iterations of Kaom's Stronghold a night (8-10 hours), and nets me about 2-3ex a night (not counting uniques; all currency) With that being said, the bot does not cast cyclone all the time. It used to get stuck all the time and just die, but then I setup leapslam as the secondary skill (priority 5 vs 9 cyclone). It leap slams to close gaps, and leap slams when cyclone won't cast. So the DPS isn't maximal, but he still mops up. Tooltip is like 35k I think

The only problem with this is if you want a gem leveled to, lets say level 15, but it's currently only 1/10 of the way to level 15 from 14. You have to babysit the bot until you see that gem pop up, and then dismiss it manually in game (this is if you want the bot to continue leveling your other gems during that time). Every time I create a new character and level him up with the bot I always miss dismissing certain gems at the desired levels and have to start over with new gems. Adding this feature sometime in the future would really help out, as long as it isn't too difficult of course. Thanks!

I have the same sentiments as ultima ^^. Thanks a lot guys!

+1

+1. Maybe have the bot enter last instance until it is % farmed

It took me a while to tweak this setup too. I have my flicker 9 priority with a max dist of 40 and min of 0, it might go further than 40 though. But to get blood rage to actually work, I set it on a 10s cooldown, a max dist of 115 and a min of 20 (so it casts whenever it sees an enemy, but not if they're too close). This isn't super efficient, since it casts a lot while it's already up, but it's the only way i've found to sustain it pretty much all the time. Oh, and min monster required range to 120.

Thanks Alk, hope I didn't repost something!

Randomly, when exiting an area after a run and returning to town through TP, the bot will be stuck on the "esc menu" (the one that comes up when you push the escape button). This is what the log says: 2015-07-26 14:38:38 [info] -> Map explored !! 2015-07-26 14:38:38 [info] -> Restart state because area is cleared 2015-07-26 14:38:38 [info] -> Creating tp... 2015-07-26 14:38:40 [info] -> Distance computed for tp use: 0.000000 2015-07-26 14:38:40 [info] -> Restart state because area is cleared 2015-07-26 14:38:40 [info] -> Moving to position(5461.956543, 18538.042969). State Priority: 19 2015-07-26 14:38:40 [info] -> Distance computed for tp use: 0.000000 2015-07-26 14:38:40 [info] -> Restart state because area is cleared 2015-07-26 14:38:40 [info] -> Moving to position(5461.956543, 18538.042969). State Priority: 19 2015-07-26 14:38:40 [info] -> Distance computed for tp use: 0.000000 2015-07-26 14:38:40 [info] -> Restart state because area is cleared 2015-07-26 14:38:40 [info] -> Moving to position(5461.956543, 18538.042969). State Priority: 19 2015-07-26 14:38:41 [info] -> Distance computed for tp use: 0.000000 2015-07-26 14:38:41 [info] -> Restart state because area is cleared 2015-07-26 14:38:41 [info] -> Moving to position(5461.956543, 18538.042969). State Priority: 19 2015-07-26 14:38:41 [info] -> Error while reading progression. 2015-07-26 14:38:41 [info] -> Chicken state because no tp found in player's inventory 2015-07-26 14:38:41 [info] -> Restart state because area is cleared 2015-07-26 14:38:42 [info] -> Chickened via method ESC+CLICK! 2015-07-26 14:38:42 [info] -> Loading stash tab... 2015-07-26 14:38:43 [info] -> Moving to stash 2015-07-26 14:38:43 [info] -> Loading stash tab... 2015-07-26 14:38:43 [info] -> Moving to stash 2015-07-26 14:38:43 [info] -> Loading stash tab... 2015-07-26 14:38:43 [info] -> Moving to stash 2015-07-26 14:38:43 [info] -> Loading stash tab... 2015-07-26 14:38:43 [info] -> Moving to stash 2015-07-26 14:38:44 [info] -> Loading stash tab... 2015-07-26 14:38:44 [info] -> Moving to stash 2015-07-26 14:38:44 [info] -> Loading stash tab... 2015-07-26 14:38:44 [info] -> Moving to stash 2015-07-26 14:38:44 [info] -> Loading stash tab... The bot used a TP to get to town, and then opened the escape menu and got stuck there. There are plenty more TPs in my inventory, and it seems like the bot tried to look for the TP after it used a TP to get to town. As I said, this is random. The bot will sometimes do 100 runs without this happening, sometimes it happens in 10 runs.

Could the bot also be setup to run off of the computer clock (eg. start at x time +/- minutes and end at x time +/- minutes)? I think that would be more normal, as people probably login at scheduled times. You could even set it up to run certain days of the week and not others. I know this is probably possible how it's setup now, but if it isn't difficult it may be a nice addon And sorry for not using the correct subject method [use Computer Clock] uses the clock for run time. I'll do it next time.

Well, i'm sure your absolutely correct, but if GGG is able to actually see what you're character is doing real time this would potentially throw them off. It would at least look more normal. Plus, the addition of this feature probably wouldn't be too difficult, and added security couldn't hurt.

Thanks for the support guys! I'll try the mentioned method, but will probably use CWDT. It would be a lot easier I guess.

Can someone help me figure out how to have blood rage stay cast on my flicker build? My bot never casts it. I have it set on 9 priority (same as flicker), 15s cooldown, and no aura or recast. I've tried to set it as an aura, and/or as recast but neither would allow the bot to function. Any ideas?

I think it would be a good idea to add the ability to randomize (interval) anything with a time delay. This would include: clicking on items to sell, movement clicks, selecting zones, etc. The more randomization, the more fluidity and less chance of noticing bottling. I don't know if this would be difficult. I think since it's already incorporated into many things it would be pretty easy, just some UI updating.

My cyclone is working pretty well. The issue persists but I haven't had any serious issues. Just can't run any high-level (>71) content because those few seconds of stoppage will probably result in death. What I do to make cyclone viable is use leap slam as my #2 skill with a priority of 3 and no cool down. Cyclone priority 9 with a 75ms cooldown. It seems that when cyclone doesn't cast because of this issue, leap slam will instead. The result is a slightly less-effective run (because maybe 1/4 of the casts will be the weaker leap slam), but no stoppage of the bot. Aqueducts runs well so far doing this and docks is ok. Testing Kaom's stronghold now.

Same ^^

Just deleted the bot and reinstalled. Something must have gotten messed up in one of the config files I suppose.

So after a few hours I'm having many fewer issues, but this problem still persists. It is always when there is an object or an elevation difference between the player and the mob.

I've had a few short runs this week and he is doing much better with the lockstep. I set leap slam cool down to 0, 0-40 range and priority of 5. I set cyclone to cool down of 50ms, 0-15 and priority of 9. I think if he gets stuck and can't attack the short cool down allows leap slam to be used and will typically unstick him. Most nights I'd get like 200 runs and die maybe 120 times. Now I get like 150 runs and die maybe 20 times. I know those 20 deaths are from this bug, but it's much better now.

Actually with the new lockstep he is dying much less. I'll run him tonight if I can fix this loop login issue I'm having and repost.

I'm not home right now, so I can't put my log up at the moment. I'll try to be as thorough as possible. After the hot fix yesterday I tried to use my bot (0.50rc; vanilla client) without success. I was logged in and my char was in A3 merci ready to start a docks run. The bot was setup and working perfectly the past few days. When I clicked "start bot" the pointer just kept moving my char down and to the right every second or so. I restarted the bot, client and my computer, but this same sequence happened again. When I looked at the log it just kept repeating something like: "Logging in... Logging in... Logging in... Etc." I tried starting it from the client being closed and it would log in, but then keep clicking where the login button would be instead of selecting my character. Has anyone experienced this?