-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
End of Support WarfaceBot #547
Comments
Thank you, @Levak ! Without you, I wouldn't have found developer friends. |
I would also like to express my gratitude for this project. But I still think it's too early to write it off. |
End of Support WarfaceBot? OH no! Excuse me, am I missing something? |
https://github.com/Levak/warfacebot/releases/tag/1.0.16b |
i dont understand bot isnt work but levak updating all time .. İf not work why updating ? İf it work why dont you interest our writing? |
bot not working yea why updating ? |
Keys are updated automatically. |
@Levak i've fixed the auth part. i'll make pr if i got time. |
The whole problem isn't really just the auth. But how people use Warfacebot. My.games was fed up of having to deal with the consequences of people abusing them left and right. Solo starting a spec ops to farm achievements was actually always seen as a violation of the EULA for them. Farming xp/cp in battle Royale was the last stroke that made them rewrite the auth to require the presence of an anticheat. It wasn't the strongest but my motto was to never tamper with it. Releasing a fix for the new auth will open the Pandore box once again to the cost of many banned accounts that will follow that will think everything will be like before. But a lot has changed since October 2020 in terms of security against bots that you might not see within a day of testing. In 2017, a similar situation happened. It was regarding private servers that were possible because the game process had a switch that could be used to make it work as dedicated server. Someone was eager to release instructions I gave him to the public. He did, despite my warnings, and in August 2017, the flag was removed. Ever since having private servers were either from dev leaks or from tremendous efforts which would often fade away because a new game update would break it. Here, Warfacebot is dead as a public bot. But its core is still being used by warface-statistics and wfstats.cf. If My.Games decides to push further the fight against bot because some smart guys decide to abuse it again (solo start, xp farm, ranked farm etc), then we can expect even stronger resistance from My.Games which would definitely kill warface-statistics and wfstats.cf. I do not advise such "fix" to be made public, nor being used for the same purpose people were using it in the past. Don't start another bot war. |
Hi Levak, thank you for all these years of WarfaceBots support. A lot has happened during this time, Yes, because of Russian players MailRu killed bots, but I hope that you will please us with new projects =)
The text was updated successfully, but these errors were encountered: