notelling123

Contagion Priority 6 CD 2000 (lower if you have a faster casting speed) Distance 35 Essence Drain Priority 5 CD 0-500 (depending on cast speed) Distance 35

Anything else I can try to rectify this problem - still exists in 0.53f

Making these changes doesn't seem to have any effect. While I'm not too concerned about the vendor problem, I am more concerned with the map problem. Here's what happens: 1. Picks up map from stash 2. Attempts to place map (may or may not work) 3. Attempts to click activate (may or may not work) 4. If 2 works but 3 doesn't it goes to stash for another map 5. Repeats 2, but there could already be a map in there. Tries to click activate but still has the map "in hand, under the cursor". So then, the "Keep" or "Destroy" dialog pops up and won't go away without my intervention.

I've been playing with this a bit. Here's what I'm trying now: ; AI clicks per second (default=10) AI_clicks_per_second=7 ; Delay in milliseconds between each click when selecting an area area_selection_click_delay=1200 ; Set here the delay in ms to wait before looting an item (to ensure that the item is really the one we want) pickup_delay=400 ; Set here the delay in ms between each item dropped in npc inventory item_vendor_delay=500

Version: 0.53b I'm finding that the bot misses clicks frequently. Either when selecting a zone, placing a map, or selling to the vendor. It's such a frequent problem that I find myself having to intervene. Any tips or additional settings I can try to adjust for this purpose? It doesn't seem to have a problem with combat elements, but everything else (zoning, maps, vendor).

I set it to the highest priority, distance 60, cooldown 12000, seems to work well.

I've been using the progression feature - I think it's great. But often I find I have to place the bot in the zone where progression ought to start. I wonder if a methodology purely based on "found" waypoints would not be more functional - I've seen it testing against quests but those could change in the future. It doesn't take on Brutus nor Merviel at this point but will find get you "to" those points.

So, I attached the bot to a different program, ran both PoE and the bot in regular (not as an admin) and it started working again.

I installed a new VM and the bot worked for a time. Today, I restarted the VM and now the bot does nothing other than hold focus over the window. I'm running both the bot and PoE in Admin mode. I don't know what else to try.

Digging up an old thread here. On a surface pro 3 I can get the game to run on Linux within a VMWare virtual machine. The only thing that kills me are serious latency spikes (4 seconds at times). But otherwise, can get it to run. Haven't tried to use the bot yet. I don't think it will work well with this much latency.

I tried reinstalling everything from the compendium, I didn't miss anything - but I reinstalled them in the vm all the same. That didn't solve the issue. Shortly I will try installing the game directly on the VM rather than sharing.

@Raze, You're right. In "MUST READ BEFORE POSTING". It says, "If the bug does not pertain to the bot it self, but something relevant like a VM please do not list the current release version!". Given my situation where the bot works outside of but not within the VM, I think you can appreciate how that may have been an ambiguous instruction. If you want people to be more specific, perhaps in the MUST READ BEFORE POSTING post, you could include a response framework like this: Bot Version: 0.51e Game Version(s): Steam & Normal VM: Yes, VMWare most recent Guide Followed: WalterWhite Installed: DirectX, .Net, VCRun Redis I'll look at the compendium to see if I'm missing anything within the VM, that's probably it. @Dynasto, yes, I installed it after it complained I was missing msv100 or something similar to that. Perhaps I'm missing something else the bot relies on in the OS?

I followed WalterWhites guide. I've got a shared path of exile running in the VM without issues. However, when I try to start the bot, nothing happens. It just brings the poe window into focus within the . I've tried all the common fixes, I'm not sure what to do next. It should be noted that the bot works as expected outside of the VM.