Proxy setup

Mint can route its connections through a SOCKS5 proxy — useful for keeping multiple accounts on different IPs, lowering latency to far-away servers, or just hiding your home address from the license server.

Why use a proxy

• Account isolation — keep alts on distinct IPs to avoid the “too many accounts from one address” flag that some servers (Hypixel included) apply.
• Geo-routing — pick a proxy closer to the game server for lower ping than your home connection might offer.
• Privacy — the license verification call hits Mint’s API from the proxy IP, not yours.

What gets routed

Mint’s SOCKS5 layer routes only Mint’s own connections: the Minecraft client ↔ game server traffic and the one-time license verify call. Your browser, Discord, and everything else on your machine continue using your normal connection — Mint does not touch system-wide networking.

Adding a proxy

Proxy management lives on the Minecraft Multiplayer screen (the server list) — this is the natural place for it because it’s scoped to which server you’re about to join.

1. From the main menu, click Multiplayer.
2. Click the Manage Proxies button in the top-right of the screen.
3. Click + Add proxy.
4. Fill in the fields:
   • Host — IP address or hostname (e.g. proxy.example.com)
   • Port — typically 1080 for SOCKS5
   • Username (optional) — only if your proxy requires auth
   • Password (optional) — same
5. Save. The entry appears in the proxy list immediately.

Proxies persist in your config file (fishingmacro.json) so they survive restarts and updates.

Switching between proxies

The proxy list has a radio selector next to each entry. Click any proxy to make it active, or click Direct at the top to disable proxying entirely. You can keep multiple proxies configured and rotate between them — saving the list means you don’t have to re-enter credentials when you swap.

Testing a proxy

Each entry has a Test button that runs a short health check off the main thread (~2 seconds, doesn’t block the GUI):

1. TCP connect to host:port.
2. SOCKS5 handshake.
3. Authenticate, if credentials were provided.
4. Small reachability ping to a public endpoint to confirm end-to-end traffic works.

Result is shown next to the entry: green check (working), red ✕ (failed, with the reason in a tooltip), or yellow dot (test in progress).

Limitations

• SOCKS5 only. No HTTP, HTTPS-CONNECT, or SOCKS4 support.
• No system-wide routing. Only Mint’s own connections flow through.
• One proxy at a time. No proxy chaining.
• No DNS-over-proxy yet. DNS resolution still happens on your machine before the connection hits the proxy. If you need DNS isolation, route via a remote DNS resolver at the OS level.

Picking a provider

We don’t endorse specific services, but for Mint’s use case:

• Residential proxies — highest trust score on game servers, but the priciest option.
• Datacenter SOCKS5 — cheap, fast, but more often flagged by anti-bot systems.
• Self-hosted on a VPS — best price-to-quality if you’re comfortable running Dante or 3proxy on a $5/mo box.

Common proxy issues

• “Connection failed” on test — host or port is wrong, or the proxy is offline. Check with the provider.
• “Authentication failed” — username/password is incorrect, or the proxy doesn’t accept credentials in the format Mint sent. Double-check both.
• “Connected but Mint can’t reach Hypixel” — the proxy is alive but blocks (or fails to reach) the destination. Some free proxies blacklist popular game servers.
• High ping — proxy is too far from you or too far from the game server. Pick one geographically between the two.