What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Exilebuddy for PoE-1.1.3+ (Updated 02 May 14 01:41)

pushedx

Well-Known Member
Joined
Sep 24, 2013
Messages
4,252
Reaction score
290
Edit 2: A few more issues have been fixed:
#46 [02 May 14 01:41]
  • Updated ClickToMoveTo to close blocking windows during mid-movement.
  • ExplorePoi now closes blocking windows upon entry.
  • Lowered default ClickToMoveTo distance to avoid some issues where the cursor can be offscreen.
  • CloseBlockingWindows now closes the Instance Manager if it is open.
  • WaypointPoi was missing logic to close blocking windows, which could cause the bot to get stuck in stash. It has been added.
  • Default Skill Registration added for Vaal Reave, Vaal FireTrap, Vaal Sweep, and Molten Strike. Convocation is not added, because it requires special logic, and the other Vaal Auars are not supported yet, as they need to be tested first.

Edit: A new build has been released that should fix some of the movement issues and the bot not updating. Please download and test the new version.
#45 [02 May 14 00:14]
  • Please download a clean copy. The previous versions cannot auto-update. Future versions should update correctly now.
  • Fixed a logic issue in ClickToMoveTo that was moving the cursor too close to close between movement positions, causing stuttering and delays.
  • Added Molten Strike to the skills usable by Soul Taker.
  • The autoupdate check was readded as it should work correctly. A mistake was made during testing it, which is why it was removed.

You will need to download a clean copy of the Release version. The Beta version will not be updated soon, because it is a different set of code now. Here is the changelog, but you are always encouraged to check the Exilebuddy (SotV) Release/Beta Revision Guide for the latest information.
#43 [01 May 14 12:04]
* Please download a clean copy. Your other versions cannot auto-update.
* The AutoUpdate system has been temporarily disabled, as the separate versioning from Beta is not supported with our current design. The previous Release cannot autoupdate with it enabled.
* This is a client version maintenance update. No known EB bugs have been fixed, as efforts are being made to fix them in the new Beta version being worked on. We're sorry for the inconvenience and the delays, but it's for the best for long term EB development.
* Updated to 1.1.3.3.
* The bot will now only request up to 10 stash tabs. This is just a temp work around for the bot not requesting all your stash tabs.
* The bot should now handle clean exits from the gui a bit better than before rather than logging you out of the game.
* LokiPoe.AcquireFrame logic updated to try and address loading screen crashes again using a new method.
* Added an experimental fix to try and prevent the client from dropping input. Exploration has also changed to use the method, so there might be unintended side effects.
* Default skill gem list has been updated. If you manage your own lists, add the following skills: Spell Echo, Convocation, Vaal Reave, Molten Strike, Vaal Clarity, Vaal Grace, Vaal Discipline, Vaal Haste, Vaal FireTrap, Vaal Sweep.
 
Last edited:
The process crashes for some reason for me, and is hard to kill in windows. I've installed a fresh, clean one, and it simply freezes hardcore, i'll check the event log and try compability modes to see if it fixes anything.
 
Tried with three different pc's now, they're all running updated win7 (two of them barebone, one is on top of slackware), they all worked just fine with the other version, none are working now. The process crashes as i mentioned when opening the .exe, and refuses to get killed hardcore, probably locked waiting for some kernel resource caused by a buggy driver or similar.. Either way, only way i can kill it, is to reboot.

Tried compability mode, tried running as adm, not sure what fails
 
I got the same problem. After I run the application it crashes ... I try to run it again but it shows, that process is already running.
 
Make sure you have .Net 4.5.1 installed. If you still have problem's please open a support thread and attach the contents of the logs.
 
Hi.

Bot feels much slower this version. He's taking few steps then standing still, walking into corners much more. Also, the bot is not using quicksilvers enough this version.
 
Hi.

Bot feels much slower this version. He's taking few steps then standing still, walking into corners much more. Also, the bot is not using quicksilvers enough this version.


same behavior here, bot seems to be taking smaller steps

also seeing the quicksilver issue
 
Make sure you have .Net 4.5.1 installed. If you still have problem's please open a support thread and attach the contents of the logs.

Net 4.5.1 is still installrd. Ive botted until the patch with the exact same setup. It doesnt crash in the same manner either as it does when missing the framework. Ill try reinstalling it once im home.
 
bot afkable status? anyone have input, not sure if i want to turn on b4 work
 
it is but its really slow............ the new explore thing is just stupid
 
Ya, it moves around much slower now but otherwise it seems as afkable as before.
 
I'm getting the impression it moves around with considerable less problem than before. It also seems to handle doors much better than before.
It still backtracks a bit and runs too far into corners etc. but it's definitely an improvement (with exception of the move/stop/move twitchy movement and non-usage of Quicksilvers which I assume is a temporary thing).
 
maybe being slow will make it more human... making it less detectable? just maybe? here's my number? call me?
 
If the movement system that was swapped in needs to be tweaked some, it will. Exploration didn't change at all, it's still using the old system. The new system will be in Beta when it's finished. The new code does have a few different logic checks for ignored nodes to identify pathfinding issues.

However, the old system seemed extremely broken in this patch, to the point where the bot felt unusable even when doing basic testing. I was not comfortable simply putting out an update using it seeing how bad it was. Choosing between not releasing an update today, using the old system that seemed even more broken before, or using a newer system that the bot will be switching to (it's just not tweaked yet), the last option felt like the best thing to do.

So, improvements will be worked on this weekend for it, as the new code will fix a lot of problems the old code had, it's just not as smooth yet, because the old system worked an entirely different way. I actually did run the bot quite a lot using the new system, and it wasn't anywhere as bad as some people are saying it is for them. It's not as smooth looking as the first version, but it wasn't by any means "unusable".
 
Last edited:
Hi.

Bot feels much slower this version. He's taking few steps then standing still, walking into corners much more. Also, the bot is not using quicksilvers enough this version.

Same problem here. He takes a few steps, stand still for about 1 second and then move a few steps again.
 
same issue here, bot doing stop every 3-4 step (it look VERY SUSPICIOUS IN TOWN) nad bot dont use quicksilver flask
 
Back
Top