minecraft-rakbot

Keeps your nickname(s) occupied on offline/cracked Minecraft servers (where a nickname isn't tied to a licensed account), so nobody else can log in under your name while you're offline. On kick or disconnect it reconnects almost instantly; if its IP gets banned, it picks the next working proxy from the pool.

Install

npm install

Configuration

Edit config.json:

• accounts — list of nicknames/servers to hold. Each entry runs independently.
• reconnect.immediateRetryMs — delay before a normal reconnect (kick, server restart).
• reconnect.maxBackoffMs / backoffMultiplier — exponential backoff, only kicks in once every proxy for a given server is temporarily unavailable.
• proxy.enabled — route connections through free SOCKS5/HTTP proxies.
• proxy.refreshIntervalMin — how often to fetch fresh public proxy lists and re-validate.
• proxy.validateTimeoutMs — timeout for the proxy validation phase (tunnel-only check).
• proxy.connectTimeoutMs — overall timeout for a real bot connect attempt through a proxy (tunnel + actual Minecraft login). A proxy can open a tunnel fine but still fail to relay traffic, which would otherwise hang on minecraft-protocol's own internal timeout.
• proxy.maxConcurrentValidations — how many proxies to test at once.
• proxy.cacheMaxAgeHours — how long a cached known-good proxy is trusted before being dropped.

Run

npm start

How it works

• No proxies needed when proxy.enabled: false — the bot just keeps a direct connection.
• With proxy.enabled: true, the bot pulls free SOCKS5/HTTP proxies from public lists, validates each one with a real connection attempt to the target server (not just "is the proxy alive"), and only uses proxies that actually pass that check.
• On a kick whose reason mentions a ban/blocked IP, the current proxy is marked banned for that server and the bot immediately retries with the next working proxy.
• On a normal kick (e.g. the nickname just became free), the bot reconnects almost instantly to grab the nickname back before anyone else does.
• Known-good proxies are cached to proxy-cache.json. On startup that small cached list is re-validated first (fast) so bots can start reconnecting right away, while a full scan of fresh public proxy lists (thousands of candidates, slow) runs in the background and tops up the pool for later.

Risks and limitations

• Free proxies are unstable and die often — reconnect latency through a proxy will be noticeably higher than a direct connection.
• Some servers block known proxy/VPN IP ranges right at login — there's no guaranteed way around that.
• Network load scales with the number of accounts and reconnect frequency — with a large number of nicknames, check the server's connection-rate limits per bot.