darkbluefirefly
Community Developer
- Joined
- Nov 8, 2013
- Messages
- 1,927
- Reaction score
- 18
Because it's not just one user. And if that's the concern I would be fine with having everyone who wants the updated version, send a request via forum pm or email, and have the version emailed to them, even within a day or so. And that way people who are willing to take the risk and have requested the updated version are fine, and the others don't have to be any part of it unless they are willing to.
*Clap* *Clap*Let's say I did a quick update and didn't check anything. Think back to when the patch was deployed. It was late-evening time for people here in the States, and really early morning for EU. It wasn't exactly peak hours in general, but a good number of people would have updated their bots and went along their way. As Monday started, we'd have been in full swing by the time I'd have woken up. There might have been a few posts of people noticing things added, but let's be honest, if the bot is up and working, most people don't read the forums or other sites after updates because they don't have anything to be concerned about.
If the bot is working and running, unless someone higher up in the Buddy team has a strong reason to kill bot sessions and disable auth, that's never really done. In all likelihood, as long as things look normal, there's no real reason to think otherwise, so I most likely wouldn't have had any reason to do any further checks unless one of our users messaged me (which does happen frequently, but let's just say no one really said anything). I am working on other projects here, so if there's nothing seriously broken with EB, I don't have the time to spend doing things with it like I used to when I only worked on EB.
We're looking at possibly 2-3 days of being up and running without actually knowing what was added. The result in all likelihood (if GGG was trying to crush us instantly), would have been them detecting EB though some of their new code, causing everyone who used EB during that time to have had their account flagged for cheating. When/if GGG decides to do their ban wave (which they are smart, so they know to flag accounts, and track the flow of goods to mules, etc...), we would have been included, and it would have been disastrous.
All because I didn't do my job.
People have been "getting away with" cheating and botting in this game for quite a while now (I started my work in 2012, and have been checking every single patch since waiting for 'something'). By this time, I'm sure most people have given up on taking the precautions necessary to avoid any 'incidents'. I mean, it takes a lot of time and effort keeping up with changes, and after a while, people let their guard down and never expect anything because it seems like nothing will ever be done. It does gets tiring after a while, and I would know since I've been updating EB for quite some time since taking over back when Apoc was the main dev.
That's not the case with me though. I know we have to treat "every patch" as possibly "the patch" they come after us. As a result, every update takes a bit of time as things are checked over, and while users complain about the speed of updates, as they have for the past year of the bot's operation, we always tell them the same thing: it's for their safety. We can always give users compensation for downtime, but we can't un-ban their accounts if we cause them to get banned.
1.3.0i is finally the "proof" as to why we have to work the way we do here at Buddy when it comes to bot development. Yes, we're not perfect, and we have had bans and other mishaps, but the reason is typically due to being outsmarted in one form or another rather than us not doing the things we were supposed it. Had GGG found a way to sneak in bot detection that managed to slip past the things I typically do to check, it would have been very unfortunate, but hey, they would have just gotten us. It happens. There's no shame in it, it's part of the cat-and-mouse game of cheating in games and getting away with it. We just have to use it as a learning lesson and try to improve what we do to avoid it in the future.
That's not the case here though, because of the precautions taken. I say all this because, there's no reason to put out a functional build after a new cheat detection was put into place, without fully knowing what it currently does, and what it can do. I know exactly what they are doing, and what they can do, and the only reason why we're not being targeted yet, is because we didn't put out anything for them to target. You can't ban people for botting, if there's no working bot to ban them by. As soon as I hit that build button though, and we have a live build, things changes, and we need to make sure we are able to handle what they are doing, can do, and have a plan in place for all future patches that might head our way.
I know it's frustrating for users who just want to bot, but the old "almost worry free" era of botting/cheating in PoE is now over. A new era has begun with their focus on using client sided methods to catch cheaters. Before we return, we need to make sure we have the tools in place, and think far enough ahead to anticipate the things they might do, so we don't get trivially wiped. As to whether GGG actually goes after us, or has bigger fish to fry remains to be seen, but regardless, we need to be properly prepared for it.
That's why I am here and not else where.
I hope all you other current/future users will join me.