minecraft bot with proxy
A fresh IP for every bot, so none get throttled
Bring any proxies you like. Assign one to each bot, or tick the rotation pool and every reconnect picks a fresh one.
SOCKS5, SOCKS4, HTTP
Paste a list in the formats you already have, with or without authentication.
Rotation pool
Spreads reconnects across all your proxies automatically.
No markup
Proxies are yours. We do not resell them, so you pay your proxy provider and nothing extra.
Which proxy types work
Minecraft uses a raw TCP connection, so the proxy has to tunnel TCP. SOCKS5 and SOCKS4 work with any port. HTTP proxies work only if they allow the CONNECT method to the Minecraft port, which many cheap ones block.
One proxy per bot or a rotating pool
Assign a specific proxy to each bot to keep accounts on separate IPs. Or choose the rotating pool and every reconnect picks the next proxy, which spreads load and avoids reusing an address a server just throttled.
Adding proxies
Paste a list in the dashboard, one per line, as socks5://user:pass@host:port, http://host:port or host:port:user:pass. Passwords are masked after saving and are never shown again in the page.
Why bots use proxies
A proxy gives each bot its own IP address. That avoids join throttling when many accounts come from one address, keeps one blocked address from affecting every bot, and lets a bot connect from a place closer to the game server.
A proxy does not change what the server rules allow. It only changes the address the server sees.
SOCKS5, SOCKS4 and HTTP
SOCKS5 is the usual choice. It carries any TCP traffic and supports a username and password. SOCKS4 works for simple cases without authentication. An HTTP proxy works only if it supports CONNECT on the Minecraft port, and many cheap ones limit CONNECT to ports 80 and 443.
If a proxy works in a browser but not for a bot, the CONNECT limit is the first thing to check.
Datacenter or residential
Datacenter IPs are cheap and fast, but some networks block whole ranges. Residential IPs look like home connections and cost more, often billed per gigabyte. A bot sends little data, so measure a day of real traffic before you pick a plan.
Adding and assigning proxies
Paste proxies one per line in a common format and the dashboard parses them. Passwords are masked once saved. Assign one proxy to each bot, or let the dashboard hand them out from the list. If a proxy fails, the console shows the connection error.
Avoiding common mistakes
Free public proxies are slow and often blocked. Too many bots behind one proxy defeat the point. A proxy far from the game server adds latency and timeouts. Keep proxy passwords out of shared scripts.
Common questions
Do you sell proxies?
No. You bring your own, so you pay your proxy provider directly and nothing extra to us.
Are free proxies okay?
They tend to be slow and unreliable and are often blocked. For stable bots use a paid SOCKS5 provider.
How many accounts per proxy?
Fewer is safer. Many accounts behind one IP can trigger join throttling, so spread bots across several proxies.
Do I need a proxy for one bot?
Not usually. Proxies matter once you run several accounts or a server throttles your address.
Which type should I buy?
SOCKS5 in most cases. Check that it allows the Minecraft port.
Can I mix proxy types?
Yes. Each bot can use a different proxy and type.
How do I test a proxy?
Start one bot behind it and watch the console. A good proxy connects within a few seconds.
Are my proxy credentials safe?
Passwords are masked in the dashboard, and node tokens are protected. Still, use proxies you can replace.