Lethal Company FAQ — Ping, Servers, Network

Yes. Lethal Company has no anti-cheat system, so PingAim is fully compatible with zero risk of bans. PingAim's WFP driver routes Lethal Company.exe through your best available network connection — whether that's phone 5G tethering, a second ISP line, or your most stable adapter. Because Lethal Company uses host-client P2P networking through Steam's relay infrastructure, PingAim gives you a second connection path to reach the session host with lower latency and less jitter. The benefit is most noticeable when you have two active connections (e.g., WiFi and a phone hotspot) and your primary connection is congested.

The 'can't interact' problem is almost always a latency issue. Lethal Company runs on a host-client P2P model — every interaction (pressing E on scrap, opening a door, activating equipment) requires a confirmation from the host player's machine. If your ping to the host is high (150ms+) or experiencing jitter spikes, the confirmation takes too long and the interaction appears to fail. The fix depends on root cause: if you are the client, check your ping using the Resource Monitor or the PingHUD mod. If the host has a poor connection, the only real fix is for the host to improve their setup or for your group to switch to a host with better connectivity.

Lethal Company is a solo-developed indie game. Running dedicated servers globally costs thousands of dollars per month — an expense that is unrealistic for a one-person studio. Steam Datagram Relay (SDR) provides a free, built-in P2P brokering and relay service that handles NAT traversal so players generally don't need to port-forward. The trade-off is that session quality is tied to the host player's machine and connection rather than a consistent datacenter. This is a common and reasonable architectural choice for small indie multiplayer games.

Yes, significantly. In Lethal Company, the host's machine runs all authoritative game logic: creature AI, inventory state, world events, and all interaction confirmations. The host's upload bandwidth is split between all connected clients — in a 4-player lobby, the host is sending game state to three other players simultaneously. If the host has slow upload speed (under 5 Mbps) or high jitter, all clients experience lag regardless of their own connection quality. If you consistently have a better internet connection than your friends, hosting yourself will produce the smoothest experience for the group.

Lethal Company does not have a built-in ping display. The easiest method is to install the PingHUD mod from Thunderstore (thunderstore.io/c/lethal-company) using a mod manager like r2modman — it adds a small in-game overlay showing your current latency to the host. Without mods, you can open Windows Resource Monitor (Task Manager → Performance → Open Resource Monitor → Network tab) to see Lethal Company.exe's network activity, then trace the Steam relay IP to estimate latency using a tool like PingPlotter.

Port forwarding is generally not required for Lethal Company because the game uses Steam Datagram Relay (SDR) for NAT traversal. Steam's relay infrastructure handles hole-punching and connection brokering automatically. However, if you are behind a particularly strict NAT or corporate firewall, ensuring standard Steam ports are open (UDP 27015, 27031-27036) may help. If you are the host and experiencing connection issues specifically with players behind strict NATs, there is currently no official configuration option beyond the default Steam networking settings.