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.