06/13/2017
Hi all,
The recent release of a third-party client, OSHD, has sparked a lot of discussion within the community. We'd like to address the situation with OSHD, and discuss our stance on the client.
We’d like to thank you for your patience whilst conversations were taking place, both internal and external. Our priority is to ensure that we protect you, our pla
We will not be approving OSHD. It is in our best interests to be as transparent with you as we possibly can, and so I’ll share some of the substantial reasons as to why this is the case.
One thing you’re already aware of is the fact that the client simply is not compatible with our bot detection systems, there were a few instances of macro bans over the weekend which are a testament to that. I’ve seen some claims that these bans were targeted and I’d like to assure you that this is absolutely untrue.
The big question at hand is whether it’s possible for the client to avoid triggering our bot detection. This could be done through two methods: either we make changes to our bot detection, or we tell them how to avoid triggering it. The developers of OSHD are yet to respond to our requests for their code, and we can’t comment on how safe it is to use their product (in terms of account security in addition to the issues with bot detection). We have no relationship with the developers and so can’t simply take the client on trust. We are not willing to divulge the information needed to make changes to avoid our bot detection, as revealing this information carries a great risk which could threaten the health of Old School. Making changes to our own bot detection to aid this client could potentially pave the way for genuine botting clients which might appear to behave in a similar way. We will not jeopardise the integrity of Old School to facilitate a third-party client. We have no official ties with any third-party client, though some clients are able to operate without interfering with our bot detection, but that is not representative of any formal agreement.
Perhaps most im
We’re committed to improving our own client, but unlike third-parties we are legally and morally obligated to put the security and stability of Old School, and the safety of our pla
Ultimately the decision that has been reached is that OSHD is not approved for use. Should the developers of OSHD fail to meet our reasonable requests, we will be left with no other alternative but to take legal action against them in order to ensure the protection of you, our pla
The depth of discussion since OSHD surfaced has made it clear that there is interest among the pla