PoE2 Network Settings Guide — Lockstep vs Predictive, Gateway Switching (0.5.0)

The 0.5.0 "Return of the Ancients" launch brought record player counts to Path of Exile 2, and with that came server congestion, packet loss, and increased latency on certain gateways. While GGG quickly deployed additional server capacity, many of the networking issues players experience can be mitigated by understanding PoE2's two networking modes — Lockstep and Predictive — and knowing how to choose the right gateway and tweak max_packet_size for your connection.

Lockstep Mode

Lockstep synchronizes your client with the server on every action. Your character does not move, use a skill, or pick up an item until the server confirms the action. This means zero desync — what you see is exactly what the server sees. The trade-off is that any latency spike directly freezes your game. If your connection drops from 30ms to 200ms for half a second, your character stops responding until the server catches up.

Use Lockstep when: You have a stable connection with ping under 80ms and no packet loss. This is the default recommendation for hardcore characters and competitive racing where desync can kill you. Most fiber and cable broadband connections in major metro areas qualify.

Avoid Lockstep when: You experience periodic latency spikes, use Wi-Fi (especially 2.4 GHz), play on a congested ISP during peak hours, or have a satellite/4G/5G connection. Lockstep on an unstable connection feels like constant freezing.

Predictive Mode

Predictive mode runs the game client locally and reconciles with the server periodically. Your character moves immediately when you press a key, and the server corrects your position if there is a discrepancy. This means no input freezing during latency spikes, but you can experience rubber-banding when the server corrects your position. The amount of rubber-banding depends on how far the client's prediction diverges from the server's truth.

Use Predictive when: Your connection is unstable, you have intermittent packet loss, your ping exceeds 80ms, or you play on Wi-Fi. Predictive mode makes the game feel playable on connections where Lockstep would be unplayable. The 0.5.0 update improved Predictive's reconciliation algorithm, reducing the severity of rubber-banding events.

How to Switch Modes

In-game, go to Settings > Game > Networking > Networking Mode and select Lockstep or Predictive. You can switch between modes at any time — even in the middle of a map — but it is best to do it in your hideout to avoid a brief freeze during the transition. There is also a networking_mode=lockstep or networking_mode=predictive key in production_Config.ini if you prefer to set it there.

Gateway Switching Guide

PoE2 routes your connection through regional gateways (servers). Choosing the wrong gateway adds unnecessary latency. Here is how to select the optimal one:

• Auto-Select is usually wrong. GGG's auto-select algorithm chooses based on ping alone, not packet loss or route stability. Manually test gateways to find the best one.
• Test each gateway: In the login screen, click the gateway selector at the bottom. Note the ping displayed. Join a level 1 character on each gateway and run around for 30 seconds. The best gateway is the one with the lowest stable ping and no spikes, not necessarily the lowest ping overall.
• California vs. Washington (NA): Both are good for western NA. California often has lower ping for west coast players but Washington can be more stable. Test both.
• London vs. Amsterdam (EU): For most EU players, London is best. Amsterdam can have routing issues with certain ISPs. Frankfurt is faster for central/eastern Europe.
• Singapore vs. Japan (Asia): Singapore is generally better for SEA players. Japan is better for China/Korea connections. Test both during peak hours.
• Australia: Use the Sydney gateway. The Melbourne gateway is sometimes less stable.
• After 0.5.0: Due to the player surge, some gateways are congested. If your usual gateway shows spiking latency, switch to a nearby alternative. For example, if Washington DC is congested, try Texas or California.

max_packet_size Tweak

The max_packet_size setting in production_Config.ini controls the maximum size (in bytes) of network packets the game sends. The default is 1500 (standard Ethernet MTU). If your connection has a lower effective MTU (common with VPNs, PPPoE DSL connections, or certain mobile hotspots), sending packets larger than the path MTU causes fragmentation and increased latency:

• Default: 1500 (standard Ethernet)
• VPN users: Try 1400 or 1350 (VPN overhead reduces effective MTU)
• DSL (PPPoE): Try 1492 (standard PPPoE MTU)
• Mobile hotspot / 4G: Try 1300 or 1200

To change it, add max_packet_size=1400 under [NETWORK] in production_Config.ini. You will need to create the [NETWORK] section if it does not exist. Test with a ping plotter or in-game latency graph after changing.

Reducing 0.5.0 Server Congestion Issues

The 0.5.0 launch day saw queue times of 30+ minutes on popular gateways. While GGG has added capacity, here are steps you can take to minimize congestion-related issues:

• Play during off-peak hours for your gateway. Weekend evenings on Washington DC or London are the most congested.
• Use a less populated gateway. For EU players, try Milan or Paris instead of London/Frankfurt. For NA, try Texas instead of Washington DC or California.
• Disable global chat — chat message processing consumes client-side networking resources on congested servers. Use /dnd or disable the global chat channel.
• Avoid trading during peak hours — the API server load from trade requests adds overhead that affects instance server performance.

For more PoE2 optimization guides, check our 0.5.0 Performance Guide or use the Config Generator for a full production_Config.ini.