Exilebuddy is currently down for the Forsaken Masters update.

Please be patient as the API and bot are updated. This process will most likely take anywhere up to a week. Users will be compensated for the extended downtime. More information will be posted as needed, so please don't make threads asking for the current status of the update; there will be a lot to do!

 

Week downtime for both realms? I mean st and new leagues. GL

 

Thanks for the update and congrats on 1337 post number, pushedx.

 

As I said before just let me know if there is anything I can do to help move things along.

But pm me.. You should stick with that post number forevar.

 

An Overview of the Beta 2.0 Revamp (Pre-Forsaken Masters Changes)

Entirely new API/bot for 1.2+ now, so that's why this update will take so long (and possibly longer).

 

already missing the bot...this game is sooo boring to play

 

crap.. i just bought the bot..

 

same,
bought bot -> downloaded bot -> entered code -> "not supported" -> cry

 

There are no working PoE bots right now.

Please be patient. The bot will be up as soon as possible.

 

There are working PoE bots right now. Im using one. Dont know if it is ok if i say the name of it here.

 

Not really working if you have to baby sit it, like.. if it dies, it stays dead and you have to manual res, it sells shit you dont want it to.. So I don't know what "working means" in your definition. mine means I can leave it 24/7, tun 50 of it and only expect to collect the orbs at night, RMT, and rinse repeat.

- Sent from Samsung Galaxy.

 

Yep and you probably dont know which bot im using.

 

Don't mention it were not on the ''I use this another bot forum'' this is the buddy forum and this is the wrong thread to do that.

Focus on the topic or go to another forum.

 

The problem is not with the poe update, it is that the team is taking advantage of the patch to deploy a complete reworking of exilebuddy.

If they were not reworking it from the ground up, it would be launched by now.

Have patience.

 

Exactly this.

Exilebuddy is not just a bot for Path of Exile; it's a botting framework, with an almost complete client API provided. Updates affect us more than others, because we provide a large API for the game, and because we don't only have a few offsets and structs used in the bot itself. Our API is designed around the inner workings of the client, and when changes are made to that (which is pretty often), it requires a lot more work than usual. 1.2 made quite a few changes that affect us directly (although they weren't done specifically to target us), and not just from a botting logic standpoint with the new core game mechanics.

If the project design we had before 1.2 was working exactly as it should, the API required minimal updates on a regular basis, and the majority of the logic required for a good (but still basic) bot was done, then this update would have only been a day or so at most. It most likely would have been even less, because of the Taiwan launch and the availability of portions of the new client beforehand. However, that was not the case.

The pre-1.2 API we were using in Release, and subsequently in Beta 1.0 was not going to work correctly in 1.2. In addition, continuing to use the API as it was would have lead to increased downtime for future patches, an increased risk in flags/bans, and no chance of being able to add Garena client support. I realized this at the start of August with the Taiwan launch, and began working on rewriting it all in preparation of our 1.2 update.

In other words, quite literally, the entire EB project has now been rewritten in the past few months, and the core API over the past few weeks. The reasons for this are pretty obvious: the game is going to keep changing, and we're going to have to keep changing to keep up with it. The base logic we provide, has to be a lot better now because the core game is a lot harder. A lot of the game design changes made in 1.2 appear to target botting.

As a result, the way we develop and maintain EB has to significantly change. We need a setup that doesn't take as long to update for larger updates, and something that has less overhead updating for the smaller, more frequent updates. A lot of people have forgotten how much this game used to update over the past few months because GGG actually slowed down quite a while working on 1.2/TW. I don't expect that to always been the case, as they continue to grow the company and expand their game.

Progress for the new API/bot is going along well though. I know waiting for updates and something usable is painful, but this is hopefully one of those rare times where we do have longer than expected downtime for an update, but what we end up with puts us on the best course moving forward. I do expect there to be some bugs and issues that need to be worked out with the new Beta, but there's really no other alternative. It's the nature of bot development and just what happens when we try to do what we do, in a game like this.

 

any possibility to have implemented in the bot master's quests? Or it is left to plugin?

 

Really excited to see the new bot up and running, just got it and haven't been able to try it out yet. Tried some other bot(I'm sure most of you know what one I'm talking about) and it was shit, most of it was broken even before the update.

 

Yes, long term, I'd like to have it fully implemented, with an easy means for people to customize logic based on their build. Likewise for normal quests and other new core features in the game. The whole "community driven" aspect of things is simply for people who want things done faster, or in a different way than what we provide. That is, there's no way I could focus on mission quests right now in the bot, but if people in the community want to and share that, then our setup is made for that to happen.

Short term, it's not going to be in the logic we provide, because it requires playing though all the mission quests, and creating specific logic for each, and then setting up that logic to work for everyone in a generic way. I actually made some test logic for Haku's first quest, which you just have to explore an area, kill a boss, interact with an item, and then return it to the NPC. The logic is easy enough, but there's various cases that have to be handled that change the way a generic bot works.

For example, after you collect the spirit, various mobs spawn. Default bot logic would be to kill them all, but you need to run past some of them at times (I had one that was spawning summoned minions almost as fast as I was killing them). For cases like those, the bot would end up getting stuck, because of the disconnect between CR logic and what the bot is actually doing. Beta 1.0 also had issues with how Pois were setup for a similar reason as well.

I do have a solution for that, which will be in the Beta 2.0 release which will just be Beta for 1.2+. In Beta now, Pois are now called Tasks, and rather than design the bot around a bunch of Tasks that act on their own (e.g., looting task, combat task, chest task, etc...) make one large task that represents the current goal of the bot. The first one will simply be a GrindTask, which implements the logic to grind an area. To allow users to customize various aspects of it, I'd just have to code in a bunch of settings, but this new approach will solve the issue of execution cycles, and not being able to do more advanced logic because of conflicts. The downside is less modularity, and little code reuse since everything is specific to the current task, but, that's pretty much what will have to happen in this game.

 

This is good news. I assume those who have bought the bot have their subscriptions placed on pause untill the bot is up and running then?

also wil there be an estimated release date or any announcement to the key holders?

 

Yes, EB users will be compensated for the downtime. I'll talk to Hawker again later if more is needed depending on the current state of EB as a result of this update.

The estimated Beta release is currently tomorrow, but this PoE 1.2 update isn't a typical "bot update"; it's a "bot/API rewrite". The new EB Beta that will be released will have an entirely new API, and the bot/routine we have will lose a lot of features the old versions had, due to changes in how things have to work now (quite literally, we have to do everything different than before).

The goal is to get things back and fully functionality as soon as possible, but it's going to be a very time intensive process over the next few weeks.