By the time the bot is released it wont be worth botting in Perandus but that is fine by me as long as the next time the league resets the bot will be up asap. Been using the other bot from the other company and had nothing but issues everyday.
Bot taking too long...
- Thread starter StrongBG
- Start date
darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
Wa wa, perandus this, perandus that. Most of you don't even know what profitable is. I'll make sure that when bot is released, STD and Per will be cancer for all to bot on. Your 66 Chaos for 1 Exalt will be 130 Chaos for 1 Exalt. I'll still profit. Botting scales in profitability when you have more then a M&P Farm.
darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
It's a secret.
I believe that this whole thread should have been named, "buddy team taking too long" .
The fact that PoE was getting a big expansion was known for a long time, yet still it was all left on pushedx's shoulders. And it's not the first time the bot takes long to get back up and running because he's the only one working on it.
Would it have been so hard to assign 1-2 guys from the wow team, or somewhere else, whatever, to help out pushedx for 1-2 weeks to get this done and share some of the workload? There is nothing happening in wow, there's like a hotfix patch every 2 months or so and that's it. So if you ask me it's faulty management from the buddy team for leaving all this work to 1 guy. Pushedx is doing all he can and he has to work way more than he should because he's the only one doing it. But the fact that the buddy team wouldn't assign a few guys to help out (at least somewhat) is disrespectful to the customers, because yes, while the people who have monthly keys would get compensated for the downtime, the lifetime users (which is like 90% of the keys) don't get anything at all. Just a 1month+ wait time, when it was all anticipated and could have been avoided by having more devs on this POE expansion.
I honestly don't care how long it takes and I'm sure pushedx will release a nice working bot, but given the fact that after all this time he's still the only one working when a major POE change comes is just silly. If however, the buddy team did assign more devs than pushedx, then there is no issue.
The fact that PoE was getting a big expansion was known for a long time, yet still it was all left on pushedx's shoulders. And it's not the first time the bot takes long to get back up and running because he's the only one working on it.
Would it have been so hard to assign 1-2 guys from the wow team, or somewhere else, whatever, to help out pushedx for 1-2 weeks to get this done and share some of the workload? There is nothing happening in wow, there's like a hotfix patch every 2 months or so and that's it. So if you ask me it's faulty management from the buddy team for leaving all this work to 1 guy. Pushedx is doing all he can and he has to work way more than he should because he's the only one doing it. But the fact that the buddy team wouldn't assign a few guys to help out (at least somewhat) is disrespectful to the customers, because yes, while the people who have monthly keys would get compensated for the downtime, the lifetime users (which is like 90% of the keys) don't get anything at all. Just a 1month+ wait time, when it was all anticipated and could have been avoided by having more devs on this POE expansion.
I honestly don't care how long it takes and I'm sure pushedx will release a nice working bot, but given the fact that after all this time he's still the only one working when a major POE change comes is just silly. If however, the buddy team did assign more devs than pushedx, then there is no issue.
Masturbate & Profit Kappa
The expansion was a MAJOR change, for the game, but also for the bot. the way it's designed is completely different, teaching someone how it works would take more time than doing it alone I guess (even tho they're familiar with the botting world) This could be buddy's team fault but who cares, we'll have a working & "safe" bot (don't mind the quotes, i'm scaring the newcomers huehue)
For example honorbuddy & Legion's xpac, it wont be that long because the game don't CHANGE literally, here the whole client got a restructuration (needed... lel) which means EVERYTHING needs to be checked out, wanna hear something fun about the "discoveries" he made on the first days? crashupload is now included into the client itself. Scary hu? but if he wanted he could've just get it to work as it was before xpac, and then Tony can't take vacations because holding all the QQ threads in the ban section. (jk, this uploader is not scary at all but still, little things like this can be extremely harmful)
The way exilebuddy was designed/redesigned was not optimized at all, rechecking everything every patch is painful, now we have wrappers that should handle all the little changes made to the game now that GGG took the time to fucking fix their shit. More features for us, less time for pushedx. bro deal. That's not an excuse for the downtime but still, what he has done is literally an alien job, AND it's for us. Nobody could've expected such changes when the xpac went live.
And for the "compensation" well, 2024 is far. 1 month won't change anything. More devs wouldnt have changed anything at all, because the design for such changes was bad, that's it.
darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
People who don't know how development works, please stop breathing my air please.
DontBeAfraid
Active Member
- Joined
- Oct 2, 2015
- Messages
- 742
- Reaction score
- 30
you're just pitiable.
It's a joke bro
get down of your horse. 
we're having fun lately everyone is angry as fuck and just a little thing can burn. ^_^
DontBeAfraid
Active Member
- Joined
- Oct 2, 2015
- Messages
- 742
- Reaction score
- 30
get down of your horse.
that's it.
Infinite Monkeys
Community Developer
- Joined
- Jul 7, 2012
- Messages
- 224
- Reaction score
- 16
Being rude to people with opinions different to yours isn't a joke, it's being an asshole.
Tattoo
Member
- Joined
- Dec 16, 2011
- Messages
- 133
- Reaction score
- 11
@Tonyx's "You filthy casual Kappa"
It's really a good, chilled live as a casual here down in the casual hell. I've gotten to old, times of cs and starcraft 1 happend long ago and right now i have to work and look after my wife and children. But for the sake of my life i never stopped playing and hopefully never will
It's really a good, chilled live as a casual here down in the casual hell. I've gotten to old, times of cs and starcraft 1 happend long ago and right now i have to work and look after my wife and children. But for the sake of my life i never stopped playing and hopefully never will
darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
Finally got some to dissect this.
The re-design was in the works for a while now, pushedx stated that numerous times. The bot has to go down, on every, single, patch. People QQ on why it's taking so long, every, single, time. It makes Perfect sense to take the correct amount of time to get the bot "up to today's standards", because it will help in the long run. It's investing time now, so time is saved latter.
Saving my exalts a month prior to patch, amassing 10k exalts, and other currencies so when the bot does go down. I can still Flip, exploit the market. Of course you wouldn't do this, you're too much of a greedy ignorant beep.
The competitor updated his bot in 3 days, then we all saw what happened on reddit. Don't compare a honda to a porsche. Your analogy of consoles is so flawed.
The consoles themselves run on different custom hardware, poe bots have a base they work on, PoE. You know what, I won't waste time on this because I just realized you don't think before you speak, even If I explained it, common sense if something you can't explain or teach.
Updated offsets? bug fixes?? Are you a Neanderthal? The fucking compiler was changed. Think nascar and f1 mechanic. Yes they work on cars, the cars are fundamentally different. Why does the competitor not have a working API? Because he's just doing that, offsets. The old sigs change, yes, but the ASM is totally different, and you would need to figure out the new ASM. Oh wait, I forgot, all you know is change a few lines here and there, voila, "I made this".
Lol.. less customizable and powerful?
Less customization means you are invalid in changing lines and saying it's yours, oh dam.
Powerful, so powerful, you're guaranteed to get banned, and be a celebrity.
Level 80 is nothing to be proud of, we can get to level 86 in a day.
API is vital if you don't know jack shit what you are doing, if there are millions of different API calls. Object explorer, and a brain, will let you use EB's API. Heck I used it to make QP, where was documentation then? Oh wait, there was none.
Are you like shitting me? It doesn't take two weeks to write so little. So why are there jobs out there responsible for sole API documentation?
Anything that is an extra feature not advertised on https://www.exilebuddy.com/index.html#plans
Is an optional extra, and extra time taken from core devs to make QoL for us.
darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
Why did you edit out your original post.. whatever.
It is Necessary from an actual core developer's standpoint. You're a little turd outside that thinks he knows the inner workings of a development cycle. Adding a few lines to oldroutine does not make you a dev, it makes you a script kiddy. No one can predict what's going to trend, don't give me that horseshit that eb should have known that an unreleased expansion would hit record. EB went down BEFORE the expansion hit, with PoE getting a compiler change. That's 1-2 weeks downtime already, before xpack. So, stop, talking, please, and, spreading, false, bullshit, on, these, forums.
You making a soliloquy ? Kappa
darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
Honestly the ones that are hurt the most from the long downtime are the big farmers. Yet you don't see me complaining. That's what separates me from the little whiny ones.
Just so this thread doesn't spiral out of control, allow me to make a few points:
TL;DR: The major compiler change completely broke our project. We're fixing it, while making changes to hopefully reduce future downtimes after large expansions (as they will keep coming).
1. The current extended downtime was inevitable once the 2.1.2d Patch was released. For the type of project Exilebuddy is, a major compiler change like that is major downtime no matter when it is deployed. It just so happened to be at the same time as the new expansion, which worked out better for us. It's hard to compare other buddy projects, since other games' clients are a lot different from PoE's, but it's one of those major project breaking events that we just have to deal with in the bot development world.
2. Exilebuddy isn't a simple memory/pixel/macro bot. We don't just change a few values each patch and everything magically works again. We are providing a nearly complete API to the Path of Exile client itself, so when the client undergoes major changes, so must our API. The bot implementation we provide is simple however, but it's built upon a very large API that allows other people to make bots with the game if they so choose, through Exilebuddy itself so they don't have to reverse the game and do all the low level work themselves. A lot of people already know this, but this is why Buddy products are a lot different than any others out there: we focus on bot frameworks, others focus on actual bots. Each has their own pros and cons, but that's a different topic.
3. Brooks’ law is why more people working on EB wouldn't speed up this update process. Most of EB's code is now mine, and the time it'd take to help other people understand the way the Path of Exile client is (it really is a lot different than most other of our projects) would far exceed the time it takes me to do the updates. The fact there was a compiler update that broke every single tool and changed the layout of just about ever single struct further illustrates the issue. If I need help with anything, it's available so it's not a case of any project mis-managing.
4. We write and maintain our own set of tools for working with the game to help speed up updates and catch things that change. That is why we caught both ***** detection systems, and why we can provide an API for the game. However, once again, due to the compiler changes, all those tools broke, and need to be updated, so that adds a lot of extra update time as things are readjusted. Before we can do a beta release, all this stuff needs to be updated and verified so we don't miss anything that is pushed out.
5. The major GUI system changes are being done because the old GUI system itself was broken from the compiler changes. It was either update the old system, and continue to have month long updates on large expansions, or try to find a way to setup things better in hopes of having significant less downtime in the future. In either case, we're still looking at over a month of downtime. The idea that EB could have been updated in a few days or a week is silly, as that was quite literally impossible, which is why downtime started before the expansion client was released.
I'm sure there's more I can point out, but you guys should get the picture. The only way we could have avoided the current situation is by not having a bot for PoE in the first place.
We truly are incredibly sorry for this downtime. It's just one of those things that can happen in the bot development world that is unavoidable though. When it happens, all we can do is take the time required to update everything, then get back to botting.
It is a shame we're missing out on Perandus, but if anything, the success of this league just opens the doors for even better leagues in the future, which we hope to be able to target for once with the new changes being done now. There's no guarantee though, since this is PoE and GGG is always unpredictable, but we'll try our best as always.
TL;DR: The major compiler change completely broke our project. We're fixing it, while making changes to hopefully reduce future downtimes after large expansions (as they will keep coming).
1. The current extended downtime was inevitable once the 2.1.2d Patch was released. For the type of project Exilebuddy is, a major compiler change like that is major downtime no matter when it is deployed. It just so happened to be at the same time as the new expansion, which worked out better for us. It's hard to compare other buddy projects, since other games' clients are a lot different from PoE's, but it's one of those major project breaking events that we just have to deal with in the bot development world.
2. Exilebuddy isn't a simple memory/pixel/macro bot. We don't just change a few values each patch and everything magically works again. We are providing a nearly complete API to the Path of Exile client itself, so when the client undergoes major changes, so must our API. The bot implementation we provide is simple however, but it's built upon a very large API that allows other people to make bots with the game if they so choose, through Exilebuddy itself so they don't have to reverse the game and do all the low level work themselves. A lot of people already know this, but this is why Buddy products are a lot different than any others out there: we focus on bot frameworks, others focus on actual bots. Each has their own pros and cons, but that's a different topic.
3. Brooks’ law is why more people working on EB wouldn't speed up this update process. Most of EB's code is now mine, and the time it'd take to help other people understand the way the Path of Exile client is (it really is a lot different than most other of our projects) would far exceed the time it takes me to do the updates. The fact there was a compiler update that broke every single tool and changed the layout of just about ever single struct further illustrates the issue. If I need help with anything, it's available so it's not a case of any project mis-managing.
4. We write and maintain our own set of tools for working with the game to help speed up updates and catch things that change. That is why we caught both ***** detection systems, and why we can provide an API for the game. However, once again, due to the compiler changes, all those tools broke, and need to be updated, so that adds a lot of extra update time as things are readjusted. Before we can do a beta release, all this stuff needs to be updated and verified so we don't miss anything that is pushed out.
5. The major GUI system changes are being done because the old GUI system itself was broken from the compiler changes. It was either update the old system, and continue to have month long updates on large expansions, or try to find a way to setup things better in hopes of having significant less downtime in the future. In either case, we're still looking at over a month of downtime. The idea that EB could have been updated in a few days or a week is silly, as that was quite literally impossible, which is why downtime started before the expansion client was released.
I'm sure there's more I can point out, but you guys should get the picture. The only way we could have avoided the current situation is by not having a bot for PoE in the first place.
We truly are incredibly sorry for this downtime. It's just one of those things that can happen in the bot development world that is unavoidable though. When it happens, all we can do is take the time required to update everything, then get back to botting.
It is a shame we're missing out on Perandus, but if anything, the success of this league just opens the doors for even better leagues in the future, which we hope to be able to target for once with the new changes being done now. There's no guarantee though, since this is PoE and GGG is always unpredictable, but we'll try our best as always.