Server List Bypass

What this is for

Use server-list-bypass when a target network behaves differently if a client pings the server list before joining.

The built-in plugin does one simple thing:

1. it performs a status ping first
2. it waits for a random delay
3. it starts the real join attempt

This flow can pass anti-bot systems such as EpicGuard that expect a status ping before login.

When it helps

Use this plugin when:

• the target uses an anti-bot layer in front of the real server
• direct join attempts are rejected, slowed down, or challenged
• the network appears to expect a status ping before a normal login

When it does not help

Do not treat this as a generic fix for all connection failures.

It does not replace:

• valid accounts
• working proxies
• correct proxy forwarding setup
• correct hostnames or routing
• anti-cheat or gameplay bypasses after join

If the problem is a dead proxy, a wrong hostname, or broken forwarding, this plugin will not fix it.

Enable server-list-bypass

How to tune the delay

The delay is the main setting.

• Start with the defaults if you have no reason to do otherwise.
• Increase the delay if the anti-bot layer appears to reject immediate joins after a ping.
• Keep the range randomized rather than using a single fixed number if you want less uniform behavior.
• Do not jump straight to large delays unless the network clearly needs them.

Start with this process:

1. test with one bot and the default delay range
2. increase the delay slightly if the ping succeeds but the join still looks too abrupt
3. only scale the bot count after a single bot reliably passes

Safe testing workflow

When you are not sure whether the plugin is helping, isolate it cleanly:

1. try a join without server-list-bypass
2. enable it with the default delay range
3. test one bot
4. compare the result before touching other settings

This test shows whether the problem is the handshake flow or another network setting.

Common failure patterns

The ping works, but the join still fails

Try a different delay. If the error continues, server-list behavior is not the cause. Then review the proxies, forwarding mode, and host routing.

Everything fails with and without the plugin

That usually means the root cause is elsewhere. Do not keep tuning this plugin if the status ping makes no difference.

The network lets one bot in, but larger batches fail

This usually means rate limiting, poor proxies, or too many bots.

Related pages

• Import Proxies
• Forwarding Bypass
• Proxies
• Cannot Connect Or Times Out