hamncheese

i dont have the aura loop on/off bug what i said is

0.14h Exiledbot like the title says same old problem for me - item stuck on cursor i know a lot of ppl would say upgrade your pc, more ram, its your vpn fault, etc or some other thing along these lines the point is, if Exiledbot do need a certain Hardware spec then do please put on some sort of warning for minimum specification and in my honest opinion a good software shouldnt be limited to only a certain spec, because the broader spec it can go, more customer what im wondering is, the bot seems to have so little feedback reading from the client and have to resort to timer based behaviour, for instance : selecting waypoint normal > act1 > mudflats : the bot dont know wether the client is allready loading or not, it kept clicking normal > act1 > mudflats > normal > act1 > mudflats over and over again until the client properly load the map. altho in the end the bot did know if a proper map is load / not now im not a programmer, but i notice that the bot Does have a reading capability, like Aura, i dont know what the bot reads (memory ? pixel?) but the bot can decide if an aura is On or Off now im thinking cant the same principle applied to cursor ? as to read wether theres an item or not on the cursor ps: this item stuck on cursor bug is also an infinite loop, the bot cannot resolve on how to release the item from cursor, and would just be doing infinite relog reading from the improvement note on 0.14g Fixed bug when bot tries to pick an item while inventory is full (resulting in an annoying boring f*****g infinite loop/crash). i think this bug warrants the developer attention just my 2 cent other bug still at large - running back and forth cannot decide wether to explore or loot - closing client when doing chicken new bug not on 0.14f - stashing main scroll stack when it hit max number on settings ie: 40 (not a big deal tho this one)

wholeheartedly agree with similar "lol" comment altho i didnt receive actually "lol" i did get the "nothing is wrong with the bot its your VM or connection" i was complaining a bit in the shoutbox about the - item stuck on cursor - bug yes i know that hardware lag and or latency lag does affect how frequent this bug pops up nevertheless theres quite a lot of ppl complaining about this bug what i dont like is the "its not my fault its your crappy stuff" response

Exiledbot 0.14f after further observation im guessing this is the bot AI and how it affected by this bug 1. bot kills mob 2. if mob drops no Loot 3. bot Explore what actually happen when the bug occur 1. bot kills mob 2. Lag (from hardware/connection) -- mob drops loot ** at this point the bot has already decided that there is no Loot, and move on to Exploring ** but somewhere in the program bot botices theres a Loot, and the command to pickup loot kicks in 3. bot cannot decide wether to Loot or Explore this happens even not on VM with a system of Quadcore cpu and 8gb ram, with latency 100-200 so, again, what i think would be an ideal solution, Loot always have higher priority over Explore

i agree with this, its almost always when bot tries to id something, and its getting VERY frustrating.... the bot would just stuck on logout--login---logout----login and so on

hmm o thought the old version wont work because of the offset. i dont have the guts to tried it in case something went wrong and GGG can sniff the old version bot anyone up for the task ? lol

thank you for noticing this problem crossing my fingers for the next version PS: ive manage to reproduce this several times : - look for a big or rather a long chain of mob - throw some rares - start bot (f12) and the bug kick in (several times, not always)

this bug is the single most annoying bug in my opinion. Bot cannot decide wether to move to Point A or Point B and repeatedly clicking point A and B endlessly until timer kicks in and relogs the bot i have never really timed it but is around 15 mins ? why this is the most annoying bug ? because i caught more than once when bot was relogging due to this bug and the bot was leaving good loot (unique, chaos, i even saw once it left GCP on the ground) and when bot came back and make new instance well the loot is gone so im thinking just how many the bot was actually throwing away due bug, not to mention the wasting of time for the relog to kicks in and the wasting time for the poe client to reload im guessing Point A : bot is trying to explore im guessing that because this happens almost always when theres never any mob around, if theres a mob like in the screenshot, bot would kill mob, and return to his dance between point A and B. i have made sure that i dont have Skills settings with a large distance, all my skills settings distance are 200 including aura, so im pretty sure theres no skills with extra large distance thats triggers when looking for mob outside the screen Point B : bot is trying to loot, scroll of wisdom on red circle this only happens whenever theres a loot and the bot was clearing area around that loot, if he clears out to certain distance this bug would happen so to my observation it looks like the bot have the same priority for Exploring and Looting (running back) several solution ive tried : apwkid gave some solution http://exiled-bot.net/community/index.php/topic/1481-list-of-bugs-with-possible-solutions/ i tried his method but to no avail i still get this bug very often often something like 1 bug every 2 maps what i think would be an ideal solution : Looting should always have higher priority over Exploring after all user can allready set their prefered distance to clear out mob from Loot PS : i tried the bot without using Smart Pickit and this bug never happen, altho i only used it around 8 hours or so, since the default Loot behaviour can only Loot Rares and Stash it, so bot would easily fill up the stash, hence why i got back to Smart Pickit. This has happen to me since Exiledbot ver 0.14e I really hope someone have a solution for this or temporary fix thank you for anyone reading my post

BlackSun Thank you so much for your programyour program AutoPoe is the main reason i bought life time, without your AutoPoe the standalone bot cannot endure 24/7 (or maybe its just me dont know how to set it up yet) but anyway hang in there mate, im going to be the first to donate to AutoPoe, it deserves to be built into the Bot , that just imho keep it up mate

Exiled Bot Beta v0.14e Autopoe v1.8b Confirmed the bug on AutoPoe previous version that cannot skip the Welcome window of Bot has been fixed thank you so much BlackSun

ah sorry about my previous post, u can just ignore it, i didnt realize it was fixed allready, going to download the latest version and report back

nevermind this post problem has been fixed before i posted this

thank you so much for responding alkpone for now the best solution is using AutoPoe script made by BlackSun

Another solution ive tried : using the AutoPoe script made by BlackSun http://exiled-bot.net/community/index.php/topic/697-auto-poe/ this appears to be the best solution so far Blacksun script would kick in if theres no poe client within xx time but i still think the bot itself should be able to detect wether theres an active poe cient window or not maybe for the future version i hope

reporting bug after 6 days of observation since the first day i tried exiledbot the bot would appears to randomly closes poe client i afk a bit and came back to find the client was allready closes without any error window and i never had any error or black screen of death, playing poe has always been a smooth for me after further observation it seems this happend everytime the bot chicken out and observing further im guessing this what happen : the bot would chicken - press esc - click Exit To Login Screen - press esc- click Exit To Login Screen - press esc- click Exit To Login Screen emulating this behaviour manually did close the poe client how i came to this conclusion : this only happen when the bot is inside a VM with a low Ram and Cpu , and the poe client would be slow to respond when i tried the bot inside my real system it can run all night without closing the poe client, and when it DID chicken, the chicken would run smoothly, the bot would login again normally i set the chicken to 70% hp Bot inside VM : everytime it chicken would result in the closing of poe client Bot inside real system : no problem so far several solution ive tried : turning off the chicken by setting it to 0 (i tried changing the setting using the GUI and editing the config.ini and always close and open a new bot to avoid the bot not loading the new settings) this solution has failed because the when the bot dies it would still run the chicken script/command thus ends up in the closing of the poe client adding more ram and cpu power to the VM it works 70% of the time (2 days observation), after several hours the vm eventually fill the vm ram and would have the same slow response and when chicken happen at that point, it would close the poe client, so adding more ram/cpu ? since im planning to run multiple bot with the lowest machines posisble this is not ideal for me what i think would be the ideal solution : the chicken script/command should be : chicken - press esc - click Exit To Login Screen - click Exit To Login Screen - click Exit To Login Screen - click Exit To Login Screen or adding more sleep/time in between pressing esc edit : another ideal solution would be to have the option to really turn off chicken mode