Need a Real Fix for AwakeBot
This kind of bot "[Only registered and activated users can see links. Click Here To Register...]"
I do not want an alternative, but a real fix.
Thank you not offer me silly solutions such as "put a cooldown."
Fix for "AwakeBot"
05/10/2016 20:11
ZeroTwo02#1
Need a Real Fix for AwakeBot
This kind of bot "[Only registered and activated users can see links. Click Here To Register...]"
I do not want an alternative, but a real fix.
Thank you not offer me silly solutions such as "put a cooldown."
05/10/2016 20:26
KazumiTanuki#2
a simple, quick and easy way would be by chaning the ID of the attributes and getting a decent resource encryption.
The bot checks the ID of the awake for example STR = ID 4 and then checks the value.
now if STR = ID 6531, the bot wont stop at the choosen value, which make it useless.
Only way to make it work again would be to look into resource files, find out the new ID and replace it with the old.
So Zerux would have to crack your Res encryption first, and then he would have to make a new bot for your server only.
I highly doubt he would do that and sell it for the same price as his current bot.
So get a really good encryption and do that.
The bot checks the ID of the awake for example STR = ID 4 and then checks the value.
now if STR = ID 6531, the bot wont stop at the choosen value, which make it useless.
Only way to make it work again would be to look into resource files, find out the new ID and replace it with the old.
So Zerux would have to crack your Res encryption first, and then he would have to make a new bot for your server only.
I highly doubt he would do that and sell it for the same price as his current bot.
So get a really good encryption and do that.
05/10/2016 20:33
ZeroTwo02#3
Yes so I do a reset all awakes on my server for fix a cheat ?Quote:
a simple, quick and easy way would be by chaning the ID of the attributes and getting a decent resource encryption.
The bot checks the ID of the awake for example STR = ID 4 and then checks the value.
now if STR = ID 6531, the bot wont stop at the choosen value, which make it useless.
Only way to make it work again would be to look into resource files, find out the new ID and replace it with the old.
So Zerux would have to crack your Res encryption first, and then he would have to make a new bot for your server only.
I highly doubt he would do that and sell it for the same price as his current bot.
So get a really good encryption and do that.
Stupid solution NEXT.
05/10/2016 21:05
alfredico#4
Solution one, block memory reading from your application.
Solution two, change and convert the whole awakening system to a better one.
Solution three, edit the current awake "formula" to make the bot unable to read the awake s. In other words, the 0x and other numbers stuff in randomoption.cpp
Solution two, change and convert the whole awakening system to a better one.
Solution three, edit the current awake "formula" to make the bot unable to read the awake s. In other words, the 0x and other numbers stuff in randomoption.cpp
05/10/2016 23:09
FlyffServices#5
If u are using the Source i able to write you a 1-line fixx who block all Awake bots.
You dont need change resource, window format or any shit like the other say LOL?
write me pm i do for free!
You dont need change resource, window format or any shit like the other say LOL?
write me pm i do for free!
05/11/2016 00:38
ZeroTwo02#6
mp :oQuote:
You dont need change resource, window format or any shit like the other say LOL?
write me pm i do for free!
05/11/2016 07:16
Zerux#7
Would be nice to see another try to fix the bot.
Some experienced Developers have tried fixing it but the only thing that happened was that the users got annoyed.
What Serveradmins tried to do:
-Detect the Bot (usesless due to Bot Information Randomization) :D
-Changing ID's (doesn't matter as the Bot uses multiple detection methods)
-Memory Protection (not really possible, "the client will always be compromised")
-Changing awakesystem: The have been a lot of different trys to fix it. eg. moving buttons or captchas. This takes about 10ms more for the bot to awake but the useres get annoyed as fck :D
@[Only registered and activated users can see links. Click Here To Register...]: Don't get scammed by people who sell you some "crappy" fix for this. And whats your Server? So I don't miss out on that fix :) I would be happy so see some creative Solution ;)
Some experienced Developers have tried fixing it but the only thing that happened was that the users got annoyed.
What Serveradmins tried to do:
-Detect the Bot (usesless due to Bot Information Randomization) :D
-Changing ID's (doesn't matter as the Bot uses multiple detection methods)
-Memory Protection (not really possible, "the client will always be compromised")
-Changing awakesystem: The have been a lot of different trys to fix it. eg. moving buttons or captchas. This takes about 10ms more for the bot to awake but the useres get annoyed as fck :D
@[Only registered and activated users can see links. Click Here To Register...]: Don't get scammed by people who sell you some "crappy" fix for this. And whats your Server? So I don't miss out on that fix :) I would be happy so see some creative Solution ;)