Skip to content
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

looting bot #3

Closed
0xRyanLucci opened this issue Mar 3, 2022 · 7 comments
Closed

looting bot #3

0xRyanLucci opened this issue Mar 3, 2022 · 7 comments

Comments

@0xRyanLucci
Copy link

can we do a discord chat about the looting bot?

@coccoinomane
Copy link
Owner

Hey @Bitcorn69 , sorry for the late reply.
As a consequence of the anti-bot patch released last week by Crabada, I am evaluating whether and how to proceed with the looting bot.
I'll update the readme when I have a plan :-)
PS: The mining bot on Github (this repository) is still working though and can be used for free.
Cheers,
Guido

@mzahirr
Copy link

mzahirr commented Mar 14, 2022

Hi @coccoinomane is there any progress for looting bot?

@nikohd12
Copy link

I don't think finding a loot will be fixed. Reinforce and settle can be fixed.

@0xRyanLucci
Copy link
Author

What about solving the captchas manually? There are also services to solve captchas with api but they are not fast enough...they have humans solving them and it costs per captcha.

@mzahirr
Copy link

mzahirr commented Mar 19, 2022

What about solving the captchas manually? There are also services to solve captchas with api but they are not fast enough...they have humans solving them and it costs per captcha.

I agree . Is there any way ?

@coccoinomane
Copy link
Owner

coccoinomane commented Mar 19, 2022

Hey guys, thank you for your inputs!

The more I think about the looting bot, the more I lean towards NOT going forward with it.

There are very good technical reasons that make the task daunting: reliance on third-party APIs to bypass the captcha makes it a non trivial implementation, and playing catch-up with Crabada's devs as they improve the captcha is very time consuming.

But, more than that, I love the Crabada game and I respect the Crabada community.

Before the captcha was implemented, making a looting bot was fair game: it was nothing else than interacting with the blockchain. Because everything on the blockchain is permissionless, I did not have any qualms to make a looting bot, and I even advertised it in the README.

Now, however, the team has gone a long way towards implementing anti-bot features, for a reason: bots have started to scare humans away, which is not good for Crabada and its community. After all, we all rely on Crabada, botters and normal players alike.

It is one thing to play by the blockchain rules, it is a whole another one to crack a captcha that was placed by the team for very good reasons. By bypassing the captcha I feel like betraying the trust of Crabada community, and, to be honest, I would not blame them if they started banning players and crabs.

Therefore, as @nikohd12 suggested, I think I will gradually remove the attack feature (which does not work properly anyway 😅) and, as far as looting is concerned, keep only the reinforceAttack and closeLoots features. I think that these two features can still help looters automate away a big part of their tasks, which is a good thing that does not hurt the community.

Obviously, I will also keep all mining-related functions.

Cheers,
Cocco

@xiguakaoya
Copy link

thx for your contribute for the community

coccoinomane added a commit that referenced this issue Mar 22, 2022
Remove the attack scripts that where made obsolete after the anti-bot patch of March 2022, see #3. Also, update the Crabada client with the new captcha attack method.

Commits:

* Removed redundant checks
* Update attack method in crabada web3 client
* Removed attack scripts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants