heisenburger

This bot has thousands of users. If it's a scam, this place would be flooded by angry comments. This bot has saved me from wasting years of life. It's shame some people don't know how to use it.

When [AugmentIfPossible] is turned on, the bot would try to upgrade unidentified maps nonstop.

It's possible but also time consuming. Go hook the client with spy++ and look at how many kinds of messages are sent to the client per "real" mouse movement. Now try to simulate every message and see what happens. I didn't even bother trying. Just gave up right away.

lol alk will never get any sleep because of these requests. A hard-coded delay sounds good enough to me.

Logs?

This is very helpful. Thanks

There doesn't seem to be a delay in cases where the bot chickened to char-selection screen instead of login screen. So as soon as the bot sees the char-selection screen, it'd immediately try to select a character with almost no delay. Hopefully this will be fixed. (like adding a delay before selecting a char).

I'm having similar problems. Same logs. Except my bot crashes once every few hours on char-selection screen. Happens only with mapping turned on.

It happens about once every few hours. I was farming Voll. After the bot timed out and logged back in, it was still stuck. Log: 2016-04-15 23:36:14 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:14 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:14 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:14 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:14 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:14 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:14 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:14 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:14 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:14 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:14 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:14 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:14 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:14 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:15 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:15 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:15 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:15 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:15 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:15 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:15 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:15 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:15 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:15 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:15 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:15 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:15 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:15 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:16 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:16 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3 2016-04-15 23:36:17 [info] -> Trying to go to recorded position 83 444 !! 2016-04-15 23:36:17 [info] -> Moving to position(1809.623657, 4831.473145). State Priority: 3

I suppose you just don't have the time to watch your bots to notice any problem, because this won't do anything to make the bot get stuck less often. A lot of times the bot is stuck forever with mobs that aren't moving. A high dps won't help if the bot is never going to touch the mob, and "maintain keypress" will not magically attack the mob if you're stuck. To all the new players out there, you need another way to get unstuck if you have to use cyclone.

lol can you get lazier

Yeah good to see someone who gets the idea. I mean the bot should be able to use at least 2 skills at the same spot without trying to escape. When there are 4 totems in 2.2, this can be useful too.

@raze like I said, it'd be great to have an option to cast all your skills at the same spot with proper delays and move afterwards. It's impossible now because there's no option to delay a skill in the combat settings. You can cool down afterwards, but you can't delay beforehand.

@jsp: these are good points. I've been doing something similar to what you said like using different ranges just to cast different skills. I was hoping the bot could have an option to use all the skills at the same spot with proper delays and kite afterwards. In my last example I used the same range just to show the problem. The bot does use all skills but there's no delay in-between.

That's my point. Why should I get closer to a crowd just to cast a second skill? What this bot needs is a delay BEFORE casting a skill.

"why do u have them at prio 10 and 9,, go with prio 9 and 7" How is 9 and 7 better than 10 and 9? "why u want two different skills to be cast within the same range during 1.5 secs time?" For contagion+essence drain to work on a crowd, you need to use contagion on the crowd first and essence drain second in order to spread the debuff. I don't want to get closer to a crowd just to cast a second skill that should be cast at the same range. There are plenty of other reasons to cast multiple skills at the same range. For example: casting 4 totems. I'm not going to get closer and closer to a crowd just to cast each totem. The totems should be cast at the same time at the same range.

alright. Let's say I just want the bot to use skill1, wait 0.5s, use skill2, and kite. It should follow this order whenever a mob is detected. (skill1 is for contagion and skill2 is for essence drain, so skill1 has to be used first to infect the mobs) So I set skill1(Q) priority to 10, cooldown to 2500, range to 30 skill2(W) priority to 9, cooldown to 1000, range to 30 Now when the bot sees a mob, it'll press Q and W at the same time, so skill2 doesn't actually get cast in-game. This alone is a problem. I could create a "hacky" delay by lowering skill2's range to 25, but ideally the bot should just cast both skills. How would you deal with that?

Of course this bot is still the top choice. By hacky ways I mean there is no straightforward way to make the bot reliably do something like this: cast skill1, wait 0.5 sec, cast skill2, wait 0.5 sec, cast skill3, wait 0.5 sec, and start running. It's clear that cool downs on individual skills can't prevent the bot from casting all the skills at the same time. My totems work fine but it will be a problem when it comes to reliably casting 4 totems in a row. Look, the bot is good but this is still a real problem.

Yeah, there are hacky ways to make totems work, but there are other builds that require you to cast each skill properly in the right order. Example: Contagion -> Essence Drain. The bot always casts contagion and essence at the same time, so essence is actually skipped. So I think this still needs a fix because pressing all skill keys at the same time is a problem by itself.

Appreciate the replies. I did try various cooldowns and read jsp's guide, and even he said the priorities don't work well and used a hacky way to curse. After reading the logs, it seems skill priorities work properly, but the real problem is the bot presses all the skill keys at the same time, so not enough time are given to the low priority skills to actually get casted in the game. A suggestion is to put an optional delay before each skill, so the bot can cast the 1st skill, wait a bit, cast the 2nd skill, wait a bit, and cast the next...

lol no need to worry. All disagreements are welcome and will help me find out a fix. So for example, how would you make a bot curse the enemy first and cast multiple totems? I can't figure out a way to do this. I have to disagree. If a skill is low-priority, it should always be used after a high-priority skill. I understand what you mean, but currently the bot will not use the higher priority skill after using the lower priority skill even when mobs are in range. The bot likes to run away after using just 1 skill.

When kiting is enabled, the bot tends to use the skill with the highest priority and immediately tries to run away while ignoring the rest of the skills. Ideally, the bot should finish casting all the skills before trying to run away. There may be hacky ways to compromise, but it's far from perfect. This makes it hard to do things that involve using multiple skills in the right order. A fix to let us properly prioritize skills would be much appreciated. Example scenario: cursing enemies -> place totem1 -> place totem2 Key Q: (curse enemy) Priority = 10 Distance 30 Key W: (totem1) Priority = 9 Distance (if > 30, bot will actually use this first; if < 30, bot won't use this at all) Key E: (totem2) Priority = 8 Distance (same as above)

There will probably be more nasty stuff in the new league. For now it's best to stick to a build that moves a lot, like kiting with totems. The bot can usually accidentally dodge a lot of stuff.

What builds are you guys using?

Sometimes the bot accidentally selects the wrong char and gets stuck in town, so it'd be helpful to chicken if the wrong char is loaded into town. This requires the player to accurately specify a character name in the configs if they want to use this option.