heisenburger

Fixed the problem by changing my windows theme from classic to default and changing the windows display scale from 120% to 100%. Looting seems rock-solid now. I think the height of the window top-border has an effect on the bot's coordinates. It seems (0,0) is the top-left corner of the entire window (including the window border), so if your border is too big/small, it'll shift the bot's Y-coordinates down/up. But I could be wrong. It all depends on whether Alk used GetClientRect or GetWindowRect. Hopefully this is of some help.

It'd also be nice if the bot no longer clicks on strongboxes since these boxes automatically open when all box-mobs are killed.

Thanks for the update. I just tried again on a different pc and the bot had no problems with looting.... edit: nvm. the cursor still gets stuck when there are many items on the ground.

Looting failure rate is pretty high now because the bot no longer moves the cursor around to find what's on the ground. When the above happens, the bot gets stuck and the last line of the log shows: Rotten Entity not Ccleaned detected: address 554b1ef8, id 0ee9 Anyone else having the same problem?

+1. I'll pay $30 just to see this fixed. For now this little bug kind of cripples the whole chancing/map-upgrading feature. Would really appreciate a fix.

I agree with all the complaints. Hopefully someone on the EB team could explain why the bot sometimes has trouble accurately getting an item's coordinate on the screen. I know some coding and want to help out.

thanks for answering my question. I don't open strongboxes but still find mirrored maps in my inventory. Maybe the bot sometimes opens strongboxes by accident...

How do you guys even use the map-upgrade feature when the bot keeps getting stuck on mirrored maps?

I'm having the same problems, but it happens only in VMs. The bot can't click on the map device or the sell button. If I run the bot outside the VM, everything works fine. Log (idling in lab) 2014-11-17 22:59:28 [info] -> Clicking on map device 2014-11-17 22:59:29 [info] -> Opening map... 2014-11-17 22:59:29 [info] -> Clicking on map device 2014-11-17 22:59:29 [info] -> Opening map... 2014-11-17 22:59:29 [info] -> Clicking on map device 2014-11-17 22:59:29 [info] -> Opening map...

and how can you make the bot ignore mirrored maps?

For now I'd be happy if the bot can use augmentation orbs...or can it already?

The bot still has trouble exploring multi-level maps (my map-explore was set to 85%). Feel free to add the maps your bot has problems with. Overgrown Ruins The bot cannot go down stairs. It just stands next to the stairs. Tropical Island After the bot enters the cave, it'd come out and go in repetitively. Musuem The bot cannot enter the boss area because you need to pull the latch on the door to open it. Palace & Jungle Valley After entering the boss area, the bot would run to the corner and get stuck. Orchard & Dungeon After killing the boss, the bot would run to the corner and get stuck.

The bot simply gets stuck trying to enter the red portal to Piety's chamber.

Since we're at it... When you run multiple VMs, does each VM use resources from each core roughly evenly? If yes, does it mean an 8-core cpu is always better than a 4-core cpu for multibotting?

Are you saying all your 7 characters shared the same IP? That's like suicide.

Just to add something... does it make sense to use image search for looting? Right now when the screen is covered by items, the bot can't always locate the right item. Instead, the mouse just circles around the item but never lands on it.

1. The bot attempts to upgrade maps that cannot be upgraded (mirrored maps). This would put the bot in an infinite loop of using orbs on the mirrored map. 2. Very rarely, the "keep item / destroy item" menu would somehow pop up while the bot is stashing. When this happens, the bot would get stuck. 3. When there are too many items on the ground, the bot sometimes can never locate the right item. Suggestion: make the bot hold alt while moving the cursor could help a bit. This is because when you put the cursor over an item on the ground, the item under the cursor might not be highlighted unless you hold alt.

As long as GGG finds out you're running multiple characters from the same hardware or location, you'll most likely get banned. Make sure you understand what it takes to give every one of your characters a unique identify before you work on randomizing movements. If GGG really does watch for random movements, most of us would have been banned long ago.

It seems smart pickit can't check [Physical DPS] anymore. The weapons get stashed even when I have [Category] == "1Handed" && [Rarity] == "Rare" # [Physical DPS] >= "1000" && [stashItem] == "true" edit: it works if [stashItem] == "true" isn't there....

You can try, but the bot gets stuck in Sceptre of God pretty often too.

Had the same problem, but piety isn't worth farming using this bot. Each run takes too long.

Feedback: The bot doesn't return to corrupted area to pick up remaining items.

Whenever the bot is stuck in an area, it waits until the idle timer is up, opens a portal, enters the portal (back to town), and enters the portal again (back to area). This loop would go on until I'm out of portals or the Max Run timer is up. Area tested: Lunaris Temple Level 3 Frequency: whenever the bot is stuck in the area Log: // While the bot is stuck in Lunaris Temple 2014-08-08 23:37:48 [info] -> Exploration : 7.017120 2014-08-08 23:37:48 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Exploration : 7.017120 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Exploration : 7.017120 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:49 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Exploration : 7.017120 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Exploration : 7.017120 2014-08-08 23:37:50 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:37:50 [info] -> Restart state because no monster were killed for 60 s 2014-08-08 23:37:50 [info] -> Creating tp... 2014-08-08 23:37:52 [info] -> Exploration : 7.017120 2014-08-08 23:37:52 [info] -> Distance computed for tp use: 0.000000 2014-08-08 23:37:52 [info] -> Restart state because no monster were killed for 60 s 2014-08-08 23:37:52 [info] -> Moving to position(39255.433594, 5679.347656). State Priority: 15 2014-08-08 23:37:52 [info] -> Distance computed for tp use: 0.000000 2014-08-08 23:37:52 [info] -> Restart state because no monster were killed for 60 s 2014-08-08 23:37:52 [info] -> Moving to position(39255.433594, 5679.347656). State Priority: 15 2014-08-08 23:37:53 [info] -> Exploration : 7.017120 2014-08-08 23:37:53 [info] -> Distance computed for tp use: 0.000000 2014-08-08 23:37:53 [info] -> Restart state because no monster were killed for 60 s 2014-08-08 23:37:53 [info] -> Moving to position(39255.433594, 5679.347656). State Priority: 15 2014-08-08 23:37:53 [info] -> Idling... 2014-08-08 23:37:53 [info] -> Idling... 2014-08-08 23:37:53 [info] -> Moving to position(2070.680908, 2407.683350). State Priority: 2 2014-08-08 23:37:53 [info] -> Moving to position(2070.680908, 2407.683350). State Priority: 2 2014-08-08 23:37:54 [info] -> Moving to position(2070.680908, 2407.683350). State Priority: 2 2014-08-08 23:37:54 [info] -> Exploration : 7.017120 2014-08-08 23:37:55 [info] -> Casting aura 2014-08-08 23:37:56 [info] -> Exploration : 7.017120 2014-08-08 23:37:57 [info] -> Casting aura 2014-08-08 23:37:58 [info] -> Exploration : 7.017120 2014-08-08 23:37:58 [info] -> Leveling Gems 2014-08-08 23:38:00 [info] -> Exploration : 7.017120 2014-08-08 23:38:00 [info] -> Moving to position(29571.556641, 4122.309082). State Priority: 2 2014-08-08 23:38:00 [info] -> Moving to position(29567.320313, 4123.159668). State Priority: 2 2014-08-08 23:38:00 [info] -> Moving to position(29810.361328, 4123.304199). State Priority: 2 2014-08-08 23:38:00 [info] -> Moving to position(29808.816406, 4119.701172). State Priority: 2 2014-08-08 23:38:00 [info] -> Exploration : 7.017120 2014-08-08 23:38:00 [info] -> Moving to position(29811.132813, 4127.162598). State Priority: 2 2014-08-08 23:38:00 [info] -> Moving to position(29805.576172, 4121.321777). State Priority: 2 2014-08-08 23:38:00 [info] -> Moving to position(29810.316406, 4125.383789). State Priority: 2 2014-08-08 23:38:00 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Exploration : 7.017120 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Exploration : 7.017120 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:01 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:02 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:02 [info] -> Exploration : 7.017120 2014-08-08 23:38:02 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:02 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:02 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 2014-08-08 23:38:02 [info] -> Moving to position(29808.474609, 4123.511230). State Priority: 2 Sometimes, the bot also gets stuck trying to enter the portal (only in town). Log (when the bot is stuck next to a portal in town) 2014-08-08 23:55:12 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:12 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:12 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:13 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:13 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:13 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:14 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:14 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:14 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2 2014-08-08 23:55:14 [info] -> Moving to position(2657.586670, 2451.015137). State Priority: 2

Sometimes, when my bot is in town and tries to enter a portal, it just stands beside the portal and constantly clicks on the portal's edge...This would go on until the max-run timer is up. Does this happen to anyone else?

For example, when this bot clicks on the "log in" button, does it always click on the same pixel on that button? If it does, GGG could use it to detect botting. Does this bot already have this feature? If not, should it be implemented?