|
ist eigentlich gerade der neue Version rausgekommen oder täusch ich mich da ? r7
3 September 2005 - WoWSharp v1.2.2057 - Release #7
Ok here's the deal of what happend. Up until now there was one static version of the WardenClient (the detection code within WoW). As such, a protection in WoWSharp was built to not allow new WardenClients to run.
Since yesterday, there have been an 'X' amount of WardenClients around. These are either completely random per user, or there are several different versions around.
Due to this change on Blizzards side, WoWSharp is no longer able to verify if the WardenClient has changed. Although there are still several checks in place which will try to validate the WardenClient, these checks (unlike previous version) could fail.
This means an increased risk with botting, and because of this we have changed our refund policy. We will no longer give refunds for banned accounts. This might not be good to hear for some, but the increased risk does not make this a viable option.
With that said, currently the bot IS safe, and I will keep an eye on it by doing daily checks. However the risk has increased, please be very aware of it.
You can download this version here:
WoW!Sharp v1.2.2057.r7
If you are using a custom bot or program, they do not need to be recompiled, just copy the wow!hider.dll from the download above and copy it to your WoW!Sharp directory. If you have no idea what I'm talking about, just use the download from above.
WoW!Bot in this release is based on the latest SVN version as-of-now (SVN version 696, priest *should* be fixed).
Some additional information
If World of Warcraft closes when running WoW!Inmate, try one more time if it still closes after that, do what's said in the (chat) log, visit this forum (and check if theres a post going on about it yet) or contact me directly. Do not keep trying, it wont help.
Update
Some of you have experienced WoW-closing after x period (for some at the start, others after x minutes/hours). Release #7 will solve that, there was a small bug in my code which would sometimes make WoWSharp think that a good packet was actually bad. This update is only required if you where (or are) experiencing crash problems.
|
