Checker accounts send requests to the Mojang API to check if the name is available. If it is, another account claims it. This circumvents the strict rate limit on the claiming endpoint by utilizing the lower rate limit on the checking endpoint. Even with only one account MCSniperRust is as fast as MCSniperGo with over 200(assuming a droptime of over 24h).
- Download and run the latest release
- Add one account into the
Claim Accountfield, the format isemail:passwordorbearer token - Add some accounts into the
Checker Accountsfield, the format isemail:passwordorbearer token - Optionally add proxies to the
Proxiesfield, one for every 3-4 checker accounts is recommended, the format isprotocol://user:pass@ip:portorprotocol://ip:port - Enter your desired name in the "Name" field
- Press the "Start" button
The checker accounts don't need to own minecraft!
Check out this site
- Add a custom icon
- Error handeling for non working proxies
- OAuth2 authentication
Important
The ratelimits are exaggerated by a bit to prevent hitting them because of lag. There could exist more ratelimits when combining one account with multiple IPs. But I don't have the time nor the resources to test this currently.
The ratelimit per IP is 20 requests every 60 seconds.
There seems to be no rule how these requests need to be spaced out.
The ratelimit per account is 30 requests every 300 seconds.
And there is one that doesn't allow you to spam more than 20, but the time to reset seems very low, it's way lower than the time it'll take with spaced out requests.
- MCSniperGo, for the idea
- This fork of MCSniperGo by @impliedgg, for the auth
- ATTACH, from the MCSniperGo/Forge Sniping dc, for general information
- The Mojang API docs, for information about the API
There are probably some bugs, if you find any please make an issue or even better a pull request.
