-
Content Count
112 -
Joined
-
Last visited
Everything posted by 7heend
-
I'm sorry if my english not good enough, it's not my main language.
-
why you are not willing teach someone how to update autopoe (pronooob for example)? I am saying this because autopoe is very important for botting and without it - productivity suffers.
-
no RMT ingame - no sense in bot. That's my opinion.
-
How soon this will be fixed? very annoying
-
Auto-pot for Quicksilver Flasks
rodin replied to topic's 7heend in User's script for POE and/or Exiled Bot
thanks a lot! -
Can confirm, doesn't work for me 2 ;(
-
Auto-pot for Quicksilver Flasks
rodin replied to topic's 7heend in User's script for POE and/or Exiled Bot
So, you don't know what's the problem? -
Auto-pot for Quicksilver Flasks
rodin replied to topic's 7heend in User's script for POE and/or Exiled Bot
Same colors everywhere: Saarn, Forest. Mby it's caused by lowered graphics? -
Auto-pot for Quicksilver Flasks
rodin replied to topic's 7heend in User's script for POE and/or Exiled Bot
And it's windowed, yes. Same color for town & library - 0x2A3D63 -
Auto-pot for Quicksilver Flasks
rodin replied to topic's 7heend in User's script for POE and/or Exiled Bot
Sorry for delayed answer. -
Auto-pot for Quicksilver Flasks
rodin replied to topic's 7heend in User's script for POE and/or Exiled Bot
Everything what been told in this thread, i've been done, but nothing helps, script keeps spamming flasks in town. Library, same colors as @benis. Color is _outOfTown = 0x2A3D63 -
Nope, i bought more
-
Sure, it's working for some time, but i cannot call ExiledBot stable, so it's running for a while and crush then. BTW, i dunno what's the problem, autopoe working normal on 3/5 of my vm's, but they are identical. MAGIC
-
Same, "run as admin" doesn't help
-
[1/15/2014 7:13:49 AM]: System startup [1/15/2014 7:13:54 AM]: Starting client [1/15/2014 7:16:04 AM]: Clicking on login button [1/15/2014 7:16:08 AM]: Running bot [1/15/2014 7:16:11 AM]: Starting bot [1/15/2014 7:16:21 AM]: Bot didn't answer, restarting [1/15/2014 7:16:27 AM]: Running bot [1/15/2014 7:16:32 AM]: Starting bot [1/15/2014 7:16:44 AM]: Bot crashed [1/15/2014 7:16:46 AM]: Running bot [1/15/2014 7:16:50 AM]: Starting bot [1/15/2014 7:39:33 AM]: Clicking on login button [1/15/2014 7:39:34 AM]: Client timed out, restarting [1/15/2014 7:39:46 AM]: Starting client [1/15/2014 7:40:21 AM]: Clicking on login button [1/15/2014 7:40:23 AM]: Starting bot [1/15/2014 7:48:29 AM]: Clicking on login button [1/15/2014 7:48:31 AM]: Starting bot [1/15/2014 7:48:41 AM]: Bot didn't answer, restarting [1/15/2014 7:48:43 AM]: Running bot [1/15/2014 7:48:47 AM]: Starting bot [1/15/2014 7:48:58 AM]: Bot didn't answer, restarting [1/15/2014 7:48:59 AM]: Running bot [1/15/2014 7:49:01 AM]: Starting bot [1/15/2014 7:49:12 AM]: Bot didn't answer, restarting [1/15/2014 7:49:12 AM]: Running bot [1/15/2014 7:49:15 AM]: Starting bot [1/15/2014 7:49:25 AM]: Bot didn't answer, restarting [1/15/2014 7:49:26 AM]: Running bot [1/15/2014 7:49:29 AM]: Starting bot [1/15/2014 7:49:39 AM]: Bot didn't answer, restarting [1/15/2014 7:49:40 AM]: Running bot [1/15/2014 7:49:42 AM]: Starting bot [1/15/2014 7:49:52 AM]: Bot didn't answer, restarting [1/15/2014 7:49:53 AM]: Running bot [1/15/2014 7:49:56 AM]: Starting bot [1/15/2014 7:50:06 AM]: Bot didn't answer, restarting [1/15/2014 7:50:06 AM]: Running bot [1/15/2014 7:50:11 AM]: Starting bot [1/15/2014 7:50:22 AM]: Bot didn't answer, restarting [1/15/2014 7:50:23 AM]: Running bot [1/15/2014 7:50:28 AM]: Starting bot [1/15/2014 7:50:38 AM]: Bot didn't answer, restarting [1/15/2014 7:50:44 AM]: Running bot [1/15/2014 7:50:47 AM]: Starting bot [1/15/2014 7:50:57 AM]: Bot didn't answer, restarting [1/15/2014 7:50:58 AM]: Running bot [1/15/2014 7:51:00 AM]: Starting bot [1/15/2014 7:51:11 AM]: Bot didn't answer, restarting [1/15/2014 7:51:12 AM]: Running bot [1/15/2014 7:51:14 AM]: Starting bot [1/15/2014 7:51:24 AM]: Bot didn't answer, restarting [1/15/2014 7:51:25 AM]: Running bot [1/15/2014 7:51:28 AM]: Starting bot [1/15/2014 7:51:38 AM]: Bot didn't answer, restarting [1/15/2014 7:51:38 AM]: Running bot [1/15/2014 7:51:43 AM]: Starting bot [1/15/2014 7:51:54 AM]: Bot didn't answer, restarting [1/15/2014 7:51:55 AM]: Running bot [1/15/2014 7:52:00 AM]: Starting bot [1/15/2014 7:57:30 AM]: Clicking on login button [1/15/2014 7:57:32 AM]: Starting bot [1/15/2014 8:06:10 AM]: Clicking on login button [1/15/2014 8:06:13 AM]: Starting bot --- etc for eternity.. fresh install of autopoe + bot doesn't help.
-
Ok, i figured out, that was a system problem caused by vm.
-
Ok. I figured out, that was a config mistake. But no mistakes for now, it sends error "PathOfExile.exe not found" when i'm selecting directory of "shared folder" on vm and NO ERROR when i'm selecting directory like folder on C:\ (vm). Old directory (Z:\Path Of Exile) works fine before. Btw, AutoPoe folder placed on C:\ (vm)
-
Mine is not starts the bot, just idleing on character selection screen. Nothing interested in log files, but: [1/12/2014 7:24:25 PM]: System startup [1/12/2014 7:24:30 PM]: System startup [1/12/2014 7:24:31 PM]: Starting client [1/12/2014 7:25:18 PM]: Clicking on login button Tried both var. of bot .exe name: ExiledBot / ExiledBot GUI, nothing works.
-
anyone got it to work?
-
Anyways, i hope for working autopoe 2 Just can't do my "systems" work correct without this tool.
-
Problem is still on the same place. VM's crushing. Bot files gain some kind of corruption & can't restart after (only fresh install of config. folder helps) and unfortunately, no working alternative to autopoe.
-
I'm using VMware7 cause there is no flickering at all - so, no aero. Running only MSI Afterburner with 15 fps max. limit for all programs. But with no MSI - still same prob. Can u upload your VM clone pls? i'll try your configuration. btw i got 2 PC's and same problem on both.