As you all know, GGG has been flagging accounts related to EB left and right. While we've managed to stop some of the reasons for the flagging, we haven't stopped them all. At this point in time, we're 95% certain we know exactly what was happening, and we've been working the past few weeks (somewhat silently unfortunately) at planning a system, and implementing it to resolve all the issues flat out, once and for all. We're at the point where these changes need to start being fully implemented, and tested. With all that said, in the next couple weeks, the Beta version of the bot will most likely be more broken than normal. We will ensure that we push the current Beta version to a Release so anybody using it, is still able to do so. Remember: our Betas are for users to help us test new things, and report any issues. If you are not willing to try out beta software (and thus; risk your accounts), we highly suggest that you not use them. We make every effort possible to keep the Release builds stable, and updated. However, with the changes required to resolve the account flagging, we may lag a bit behind. Please bear with us as we fully resolve the flagging issues, and implement a whole new system for exploration, and bot logic in general. This is just a very small list of things that these upcoming changes will fix, and should fix: Account Flagging based on the bot itself. We will not be able to stop flagging based on time-played and things like that. It's up to you as a user, to be smart about your botting hours, and how you bot. Indecision bugs. The new logic will resolve most (if not all) the bugs related to the bot being indecisive about what to do. Chest Opening. All chests will now be able to be opened. As well as breakable chests opened from a larger distance away. (Might be worth keeping a random Arc on your bar just for chests!) Zone completion is variable! You'll be able to set a "time allowed", % completed, among other things to tell the bot to finish a run early. Many many other improvements So basically, we're going to break the beta pretty badly in the next couple weeks. But in the long run, you'll see a much safer, and much smarter bot overall. We can't apologize enough to our users about the current state of the bot. It's just plain unacceptable. So please bear with us while we resolve the issues and bring you a proper product worth putting our name on.
Looking forward to testing it out. I'll give all my accounts a lot of testing while they're being thrown out and report back what I find odd. FOR THE GREATER GOOD!
YAY! I am self harming by using the other inferior products on the market. Thank you for sticking with it, making the always difficult decision to get back to the roots of the code and making those hard choices. Not that I expected a Buddy bot to say 'fuck it, screw this. here is your money back' WIMM
Very excited to hear the news but..... when you guys did the newest update it broke the item pickup on both release and beta versions... very frustrating as it makes the bot practically useless. It will pick EVERY thing up until inventory is full then go to town and back no stashing etc.
Please read this thread first. Release = the most stable (usable) bot version we currently have. Beta = the latest development bot version we currently have. You will want to use the Release version right now, as the beta is for our testing and the few people who can use an unstable bot as we update our code.
This is a BETA build of Exilebuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums. This build may have bugs, and new features which may not be fully tested. Use at your own risk! OS Name: Windows 8 OS Edition: OS Service Pack: OS Version: 6.2.9200.0 OS Architecture: x64 Exilebuddy is up to date! Error initializing LokiPoe main class object: System.ArgumentException: Смещение и длина вышли за границы массива или значение счетчика превышает количество элементов от указателя до конца исходной коллекции. в System.ArraySegment`1..ctor(T[] array, Int32 offset, Int32 count) в ..(IntPtr[] , ArraySegment`1& , ArraySegment`1& , ArraySegment`1& ) в ..(IntPtr ) в ..(Byte[] , IntPtr ) в Loki.Game.LokiPoe.(Process , Byte[] ) Please read the following thread before using this beta: http://www.thebuddyforum.com/exilebuddy-forum/140632-release-beta-coming-weeks.html Have problems with the lastest version.
Problem was both versions were doing the same things so I had to delete both beta and release folders and re-download the release version and now it works. Hope this helps others who may have similar problems.
Try again after today's patch, the shouldn't be any offset issues. The problem is a known problem, but there wasn't anything we could do about it. Typically, users would not notice it, but the PoE patch was delayed, so this time, you did notice it. Also, there was a general auth server maintenance, but everyone should have seen the global announcement on the forums!
Apoc or whoever is appropriate from the team, the biggest issue with "risking our accounts" isn't the account itself since accounts are free and plentiful (especially when you can just bot up a new toon), but the possible IP bans. This may be a silly thing to say/ask, but though I've botted for many years,I've had few accounts banned and I've never had to risk my IP. Could we maybe see a small guide (assuming it's even possible) on how to minimize risk and maximize protection our IP's a litte from bannage. I.e. proxies etc. Or even possible solutions for after an IP gets banned. I know I would be a tad more willing myself if not others to help in testing under those conditions. Thanks in advance for any help you can provide.
Google will provide you with all sorts of guides on how to hide your IP from GGG. (V.P.Ns are the most common)
Please bump new instance after x amount of time passed to a high priority feature. Would be a bandaid for a lot issues like 2 hour long proximity shield mob battles.
This is already in the new stuff. You can define a % complete, or a time elapsed, to finish a run. This should be enough for all users to tweak and see what works for them. (There's a few cases where these values are ignored, but I'll comment more on those later when it's more important)
