Getting the “Invite Not Working” error in Palworld can kill the fun fast. You’ve got friends ready to join, a base half-built, and the co-op invite just refuses to connect. This is one of the most reported issues in Palworld multiplayer, and it usually comes down to a handful of fixable causes — network settings, game version mismatches, or server configuration problems.

Quick Answer

If your Palworld invites aren’t working, here’s the fastest path to a fix:

• ✅ Make sure you and your friend are on the exact same game version
• ✅ Check that your NAT type is Open or Moderate (not Strict)
• ✅ Verify your firewall isn’t blocking Palworld or Steam
• ✅ Try having the other player invite you instead
• ✅ If on a dedicated server, confirm the server is running the latest build

Most invite issues are resolved by matching game versions and fixing NAT/firewall settings. The steps below cover every scenario — from Steam co-op to dedicated servers.

Key Takeaways

• Game version mismatch is the #1 cause of invite failures in Palworld
• Strict NAT type blocks peer-to-peer invites in most cases
• Windows Firewall and antivirus software frequently block Palworld’s network traffic
• Dedicated servers require port forwarding (UDP 8211 by default)
• Steam overlay and Steam networking settings can interfere with invites
• Cross-platform play between Xbox/PC Game Pass and Steam is not supported

Understanding Palworld’s Multiplayer System

Palworld supports two main multiplayer modes: local co-op (up to 4 players via invite) and dedicated servers (up to 32 players). The invite system relies on Steam’s peer-to-peer networking for co-op sessions. When you send an invite, Steam handles the connection handshake. If anything blocks that handshake — firewall, NAT, version mismatch — the invite fails silently or times out.

Dedicated servers work differently. Players connect directly to the server IP and port, bypassing Steam’s invite system entirely. If you’re on a dedicated server and invites aren’t working, the problem is almost always server-side configuration or network routing.

Quick Wins — Try These First

These fixes resolve the majority of invite issues in under five minutes:

1. Verify Game Version Match

Both players must be on the same Palworld build. If one person hasn’t updated, invites will fail. Right-click Palworld in Steam → Properties → Updates → make sure “Always keep this game updated” is selected. Restart Steam completely after any update.

2. Restart Steam and Palworld

Fully exit Steam (right-click the system tray icon → Exit). Relaunch and try again. This refreshes Steam’s networking layer and clears stale connection states.

3. Swap Who Sends the Invite

If your friend’s invite isn’t reaching you, try sending the invite to them instead. Sometimes the connection works in one direction but not the other due to asymmetric NAT routing.

4. Disable VPN or Proxy

VPNs and proxy services interfere with Steam’s peer-to-peer networking. Disable them completely before trying to connect. This includes gaming VPNs like ExitLag or Mudfish.

Deep Fixes — When Quick Wins Don’t Work

If the basics didn’t solve it, these deeper fixes target the underlying network and system issues.

Fix Your NAT Type

Strict NAT is the most common network-level cause of invite failures. To check your NAT type in Steam: Steam → Settings → In-Game → check the NAT type display. If it shows Strict, you need to enable UPnP on your router or set up port forwarding for Steam’s ports (UDP 27015-27030, TCP 27015-27030).

To enable UPnP: log into your router (usually 192.168.0.1 or 192.168.1.1), find the UPnP setting under Advanced → NAT or Advanced → Gaming, and turn it on. Restart the router after enabling.

Allow Palworld Through Windows Firewall

Windows Firewall often blocks Palworld’s network access. Open Windows Security → Firewall & Network Protection → Allow an app through firewall. Make sure both “Palworld” and “Steam” are checked for Private and Public networks. If Palworld isn’t listed, click “Allow another app” and browse to your Palworld install folder.

Verify Game Files

Corrupted or missing game files can break multiplayer functionality. In Steam: right-click Palworld → Properties → Installed Files → Verify Integrity of Game Files. Wait for the process to complete, then restart the game.

Disable Steam Overlay

The Steam Overlay can occasionally interfere with invite notifications. Disable it: right-click Palworld → Properties → uncheck “Enable the Steam Overlay while in-game.” Restart Palworld and test invites again.

Flush DNS and Reset Network Stack

Open Command Prompt as Administrator and run these commands one at a time:

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Restart your PC after running these commands. This clears any corrupted network cache that might be blocking Steam’s connection.

Dedicated Server Invite Fixes

If you’re running or connecting to a dedicated server, the invite system works differently. Players connect via IP address rather than Steam invites.

Port Forwarding for Dedicated Servers

Palworld dedicated servers use UDP port 8211 by default. The server host must forward this port on their router. Without proper port forwarding, external players cannot connect. Forward UDP 8211 (and optionally TCP 8211) to the server machine’s local IP address.

Server Version Must Match Client

If the dedicated server is running an older build than the client game, connections will fail. Server admins should update the server immediately after any Palworld patch. On SteamCMD, use: app_update 2394010 validate to force an update.

Check Server Configuration File

Open the PalWorldSettings.ini file and verify these settings:

ServerPort=8211
PublicPort=8211
ServerPassword= (leave blank if no password)
MaxPlayers=32 (or your desired limit)

Incorrect port settings or a mismatched password are common causes of connection failures.

Platform-Specific Fixes

Steam (PC)

Make sure Steam Friends is online and not set to “Away” or “Invisible.” Check that Steam’s download region matches between players (Steam → Settings → Downloads → Download Region). Mismatched regions can cause connection issues.

Xbox / PC Game Pass

Xbox and PC Game Pass players use Xbox Live networking, not Steam. Invites are sent through the Xbox overlay (press Win+G). Make sure Xbox Live services are running and your Xbox account privacy settings allow multiplayer connections. Cross-play between Steam and Game Pass versions is not supported.

Xbox Console

On Xbox, check your NAT type in Settings → General → Network Settings. If it’s Strict, restart your router and console. Make sure your Xbox Live Gold/Game Pass Ultimate subscription is active — multiplayer requires it.

Common Misconceptions

“Palworld supports cross-play between Steam and Xbox”

As of the latest update, there is no cross-play between the Steam version and the Xbox/Game Pass version. Players on Steam can only play with other Steam players. Xbox console players can play with PC Game Pass players, but not Steam players.

“If I can play solo, my network is fine”

Solo play uses almost no network resources. Multiplayer requires open ports, proper NAT traversal, and stable peer-to-peer connections. A network that works perfectly for solo gaming can still block multiplayer invites.

“Reinstalling the game fixes everything”

Reinstalling rarely fixes invite issues because the problem is almost always network-related, not file-related. Save yourself the time and focus on NAT, firewall, and version matching first.

Quick Comparison: Multiplayer Connection Methods

Method	Max Players	How to Connect	Common Issues
Steam Co-op Invite	4	Steam Friends → Invite to Game	NAT, firewall, version mismatch
Dedicated Server	32	Direct IP connect or server browser	Port forwarding, server config
Xbox/Game Pass Co-op	4	Xbox overlay invite	Xbox Live status, privacy settings
LAN Play	4	Direct connect via local IP	Same network required, firewall

Deep Dive Tips

Use a Wired Connection

Wi-Fi adds latency and can cause intermittent packet loss that breaks invite handshakes. If you’re on Wi-Fi and invites keep failing, switch to an Ethernet cable. Even a cheap powerline adapter is more stable than Wi-Fi for gaming.

Check for ISP-Level Blocking

Some ISPs block or throttle peer-to-peer traffic. If you’ve tried everything and invites still fail, try connecting through a mobile hotspot. If it works on hotspot but not your home network, your ISP is likely the culprit.

Set a Static IP for Your Gaming PC

If you’re port forwarding, your PC’s local IP can change after reboots, breaking the forwarding rule. Set a static IP in your network adapter settings or create a DHCP reservation in your router. This ensures your port forwarding rules always point to the right machine.

Update Network Drivers

Outdated network adapter drivers can cause all sorts of connectivity issues. Visit your motherboard or network card manufacturer’s website and download the latest drivers. Don’t rely on Windows Update for network drivers — they’re often months behind.

Quick Pick Guide

Not sure which fix to try? Follow this decision tree:

• Invite shows as sent but friend never receives it → Check NAT type, disable VPN, swap who sends the invite
• “Connection timed out” error → Verify game versions match, check firewall, restart router
• Friend appears offline in Steam → Both restart Steam, check Steam server status
• Can connect but get disconnected immediately → Verify game files, update network drivers, switch to wired connection
• Dedicated server won’t connect → Check port forwarding, verify server version, confirm IP and port

Frequently Asked Questions

Why can’t my friend join my Palworld world?

The most common reason is a game version mismatch. Make sure both players have the latest update installed. If versions match, check your NAT type and firewall settings. One of you may have a Strict NAT that’s blocking the connection.

Does Palworld support cross-play?

Cross-play is limited. Steam players can only play with other Steam players. Xbox console and PC Game Pass players can play together. There is no cross-play between Steam and Xbox/Game Pass ecosystems.

How many players can join a Palworld co-op session?

Standard co-op via invite supports up to 4 players (1 host + 3 guests). Dedicated servers support up to 32 players simultaneously.

Do I need port forwarding for co-op invites?

For standard Steam co-op invites, port forwarding isn’t usually required — Steam handles the connection through its relay network. However, enabling UPnP on your router helps. Port forwarding is only required for dedicated servers or LAN play.

Why do invites work sometimes but not others?

Intermittent invite failures usually point to network instability. Wi-Fi interference, background downloads consuming bandwidth, or ISP throttling can all cause sporadic connection issues. Switch to a wired connection and close bandwidth-heavy applications.

Final Thoughts

Palworld invite issues are frustrating but almost always fixable. Start with the basics — matching game versions, restarting Steam, and checking your NAT type. If those don’t work, move on to firewall rules and port forwarding. The vast majority of players resolve their invite problems within 15 minutes of following the steps above.

If you’re still stuck after trying everything, the Palworld community on Discord and the Steam forums are active and helpful. Someone has almost certainly run into your exact issue before.

Sources & Verification

• Palworld Official Discord — Multiplayer troubleshooting channels
• Steam Support — Steam Networking Documentation
• Pocketpair Official Website — Palworld Game Updates & Patch Notes

What Do You Think?

Did these fixes solve your Palworld invite problem? Drop a comment below with your setup and what worked for you. If you found a fix that’s not listed here, share it — other gamers will thank you for it.

Getting a team error in Muck can ruin your multiplayer session fast. Whether you’re trying to join friends or host your own game, team errors prevent you from playing together. Here’s how to fix it.

Quick Answer

Team errors in Muck are usually caused by network connectivity issues, firewall blocks, or version mismatches between players. The most common fix is ensuring all players are on the same game version and that your network allows Muck through the firewall.

✅ Verify all players are running the same Muck version
✅ Allow Muck through Windows Firewall
✅ Restart your router and game client
✅ Disable VPN if you’re using one
✅ Try having the host restart the server

Key Takeaways

• Team errors are almost always network-related, not game bugs
• Version mismatch is the #1 cause — everyone must be on the same update
• Firewall and antivirus software frequently block Muck’s multiplayer connections
• VPNs can interfere with Steam’s peer-to-peer networking
• A simple router restart fixes the issue more often than you’d think

What Causes Team Errors in Muck

Muck uses Steam’s peer-to-peer networking for multiplayer. When you get a team error, it means the game can’t establish a proper connection between players. This can happen during the lobby phase, when trying to join an existing game, or even mid-session when the connection drops.

The error is frustrating because Muck doesn’t give you a detailed message — it just says something went wrong with the team. That’s why you need to methodically check each possible cause.

Quick Wins — Try These First

These fixes resolve the majority of Muck team errors in under five minutes.

1. Restart Muck and Steam

Close Muck completely, then exit Steam entirely (right-click the Steam icon in the system tray and select Exit). Wait 10 seconds, relaunch Steam, then launch Muck again. This clears any stale network connections.

2. Check Game Version

All players must be on the exact same version of Muck. Have everyone right-click Muck in their Steam library, go to Properties → Updates, and make sure automatic updates are enabled. Then verify the game files.

3. Restart Your Router

Unplug your router for 30 seconds, then plug it back in. Wait for it to fully reconnect before launching Muck. This refreshes your NAT table and can resolve connection issues instantly.

Deep Fixes — When Quick Wins Don’t Work

If the basic steps above didn’t solve it, try these more thorough solutions.

Allow Muck Through Windows Firewall

Windows Firewall often blocks Muck’s multiplayer traffic. Open Windows Security → Firewall & network protection → Allow an app through firewall. Click “Change settings,” then “Allow another app.” Browse to your Muck installation folder (usually Steam\steamapps\common\Muck) and add both the Muck executable and the Unity crash handler. Make sure both Private and Public boxes are checked.

Disable VPN and Proxy Connections

VPNs reroute your traffic through different servers, which can confuse Steam’s peer-to-peer matchmaking. Disable any VPN software before launching Muck. If you’re using a proxy, turn that off too. Both the host and all joining players should have VPNs disabled.

Verify Integrity of Game Files

Corrupted game files can cause all sorts of multiplayer issues. In Steam, right-click Muck → Properties → Local Files → Verify Integrity of Game Files. Steam will check every file and redownload anything that’s broken. All players should do this.

Open Required Ports

Muck uses Steam’s networking, which requires certain ports to be open. Make sure these ports are forwarded on your router or allowed through your firewall:

UDP 27015-27030 (Steam game traffic)
UDP 27036-27037 (Steam P2P)
TCP 27015-27030 (Steam authentication)

Disable Antivirus Temporarily

Some antivirus programs flag Muck’s network activity as suspicious. Temporarily disable your antivirus and try joining a team again. If it works, add Muck to your antivirus exception list before re-enabling protection.

Quick Comparison Table

Fix	Difficulty	Time	Success Rate
Restart Muck & Steam	Easy	1 min	High
Check game version	Easy	2 min	High
Restart router	Easy	5 min	Medium
Firewall exception	Medium	5 min	High
Disable VPN	Easy	1 min	Medium
Verify game files	Easy	10 min	Medium
Port forwarding	Hard	15 min	High
Antivirus exception	Medium	5 min	Medium

Common Misconceptions

“It’s a server problem.” Muck doesn’t use dedicated servers — it’s peer-to-peer through Steam. If you’re getting a team error, it’s a connection issue between the players, not a central server being down.

“More RAM or a better GPU will fix it.” Team errors are network issues, not performance issues. Upgrading your hardware won’t help if the problem is your firewall blocking the connection.

“Reinstalling the game always works.” While reinstalling can help with corrupted files, it’s overkill for most team errors. Try the simpler fixes first — restarting, checking versions, and firewall settings solve most cases.

“Cross-platform play causes the error.” Muck is a PC-only game on Steam. There’s no cross-platform component to worry about. If you’re all on PC, the issue is local to your network setup.

Deep Dive Tips

If you’ve tried everything above and still get team errors, here are some advanced troubleshooting steps.

Check your NAT type. Open Steam → Settings → Downloads and look at your download region. If your NAT is strict, you may have trouble connecting to other players. Enabling UPnP on your router or setting up a DMZ for your PC can help.

Clear Steam’s download cache. Go to Steam → Settings → Downloads → Clear Download Cache. This forces Steam to re-authenticate and can fix underlying connection issues.

Run Muck as administrator. Right-click the Muck executable and select “Run as administrator.” This gives the game elevated permissions to access network resources that might otherwise be blocked.

Check for Windows updates. Outdated network drivers or Windows builds can cause compatibility issues with Steam’s networking stack. Make sure Windows is fully updated.

Quick Pick Guide

Not sure where to start? Follow this priority order:

🥇 First: Restart Muck and Steam, check versions match
🥈 Second: Restart your router, disable VPN
🥉 Third: Add Muck to firewall exceptions, verify game files
🏅 Last resort: Port forwarding, antivirus exceptions, reinstall

Frequently Asked Questions

Q: Why do I keep getting team errors even though my internet works fine?

Your internet might work for browsing but still block Muck’s specific traffic. Firewalls, NAT restrictions, and VPNs can selectively block game traffic while leaving regular web browsing unaffected. Check your firewall settings and try the fixes above.

Q: Can mods cause team errors in Muck?

Yes. If one player has mods installed and others don’t, it can cause version mismatches and connection errors. Make sure all players have the same mods installed, or play without mods entirely.

Q: Does the host need a better connection than other players?

The host acts as the server in Muck’s peer-to-peer setup, so a stable connection matters more for the host. If you’re getting team errors, try having a different player host the game — someone with a more stable wired connection.

Q: Will using an ethernet cable instead of WiFi help?

Absolutely. WiFi connections are more prone to packet loss and latency spikes, which can trigger team errors. If possible, both the host and joining players should use wired ethernet connections for the most stable multiplayer experience.

Q: I can join some players but not others. What’s wrong?

This usually points to a specific player having network issues. The person you can’t join likely has a strict NAT, firewall block, or version mismatch. Have that player go through the troubleshooting steps above, particularly the firewall and version checks.

Final Thoughts

Team errors in Muck are annoying but almost always fixable with basic network troubleshooting. Start with the quick wins — restart everything, check versions, and restart your router. If that doesn’t work, move on to firewall settings and port forwarding. The key is being methodical and making sure all players are on the same page with their setup.

Most team errors are resolved within 10 minutes using the steps in this guide. If you’re still stuck after trying everything, the Muck community on Discord and the Steam discussions board are great places to get help from other players who’ve dealt with the same issue.

Sources & Verification

• Muck Steam Community Discussions — Player-reported fixes for multiplayer issues
• Steam Support — Connectivity Troubleshooting — Official Steam network troubleshooting guide
• Muck Official Discord — Active community for real-time help

What Do You Think?

Did these fixes resolve your Muck team error? Have another workaround that worked for you? Drop a comment below and help other players who are stuck with the same issue. If this guide helped you, share it with your Muck squad so everyone can get back to surviving together.

Voice chat issues in Last Epoch can ruin the co-op experience fast. Whether you’re trying to coordinate dungeon runs with friends or trade callouts in endgame monoliths, a broken voice channel kills the fun. Here’s how to get it working again.

Quick Answer

Last Epoch voice chat not working is usually caused by incorrect audio device settings, Windows privacy permissions, or in-game voice chat being disabled. The fix involves checking three things: your default communication device, Windows mic permissions, and the in-game voice chat toggle.

✅ Set your headset as the default communication device in Windows Sound settings

✅ Enable microphone access for Last Epoch in Windows Privacy settings

✅ Turn on Voice Chat in Last Epoch’s Audio settings and verify the correct input device is selected

Key Takeaways

• Last Epoch uses your Windows default communication device for voice input
• Windows privacy settings can block the game from accessing your microphone
• The in-game voice chat toggle is separate from push-to-talk settings
• Steam overlay and Discord overlay can interfere with voice chat functionality
• Outdated audio drivers are a common cause of voice chat dropping out

Introduction

Last Epoch has built-in voice chat designed for co-op play, but it’s notoriously finicky. Players report everything from complete silence to robotic audio to voice cutting out after a few minutes. The problem spans across different headsets, microphones, and Windows configurations. This guide covers every fix that actually works, from basic settings checks to deeper system-level troubleshooting.

Check In-Game Voice Chat Settings

The first place to look is Last Epoch’s own audio settings. Many players don’t realize voice chat is disabled by default or that the wrong input device got selected during setup.

Open Last Epoch and navigate to Settings → Audio. Look for the Voice Chat section. Make sure the toggle is set to Enabled. If it’s off, that’s your entire problem right there.

Below the toggle, check the Input Device dropdown. It should show your actual microphone or headset mic, not “Default” or some unrelated device. If you see multiple options, select the one that matches your hardware exactly.

Also verify the Push-to-Talk keybind. If it’s set to a key you’re not pressing, your voice will never transmit. Try switching to Open Mic temporarily to test if voice chat works at all.

Set Your Default Communication Device in Windows

Last Epoch pulls voice input from your Windows default communication device, not just the default playback device. These are two different settings, and mixing them up is the number one cause of voice chat failure.

Right-click the speaker icon in your system tray and select Sounds. Go to the Recording tab. Find your microphone or headset mic, right-click it, and select Set as Default Communication Device. You should see a green checkmark appear on the device.

If your mic doesn’t show up at all, right-click in the empty space and check Show Disabled Devices and Show Disconnected Devices. Your mic might be disabled rather than missing.

After setting the default communication device, restart Last Epoch completely. The game reads this setting on launch, not while running.

Fix Windows Microphone Privacy Permissions

Windows 10 and 11 have privacy settings that can block games from accessing your microphone entirely. Even if your mic works in Discord or other apps, Last Epoch might be specifically blocked.

Open Windows Settings → Privacy & Security → Microphone. Make sure Microphone access is turned on. Then scroll down to Let apps access your microphone and ensure that’s enabled too.

Look through the list of apps for Last Epoch or Steam. If you see either one, make sure the toggle is on. If Last Epoch isn’t listed, the game might be running through Steam — in that case, make sure Steam has microphone access.

Some players also need to enable Let desktop apps access your microphone at the bottom of the same page. This is the setting that actually covers most games.

Update or Reinstall Audio Drivers

Outdated or corrupted audio drivers cause all sorts of voice chat problems. If your mic works fine in other applications but not in Last Epoch, driver issues are a strong possibility.

Open Device Manager by pressing Win+X and selecting it from the menu. Expand Sound, video and game controllers. Right-click your audio device and select Update driver. Choose Search automatically for drivers.

If Windows says you have the latest driver but you’re still having issues, try uninstalling the device instead. Right-click → Uninstall device, then restart your PC. Windows will reinstall the driver on boot. This often fixes corrupted driver installations that updates don’t touch.

For headset users, check the manufacturer’s website for dedicated software. Headsets from HyperX, SteelSeries, Logitech, and Razer often need their companion apps for full functionality.

Disable Conflicting Overlays

Overlays from Steam, Discord, NVIDIA GeForce Experience, and other apps can intercept audio input and prevent Last Epoch from accessing your microphone properly.

Steam Overlay: Right-click Last Epoch in your Steam library → Properties → uncheck Enable the Steam Overlay while in-game.

Discord Overlay: Open Discord → Settings → Game Overlay → toggle it off for Last Epoch specifically, or disable it entirely.

NVIDIA Overlay: Open GeForce Experience → Settings → In-Game Overlay → toggle it off.

After disabling overlays, restart Last Epoch and test voice chat again. If it works, re-enable overlays one at a time to identify the culprit.

Verify Game Files on Steam

Corrupted or missing game files can break voice chat functionality. Steam’s file verification tool can repair these issues automatically.

Right-click Last Epoch in your Steam library → Properties → Installed Files → Verify integrity of game files. Steam will scan the installation and redownload any corrupted or missing files.

This process can take a few minutes depending on your drive speed. Once it’s done, launch the game and test voice chat before changing any other settings.

Quick Comparison: Voice Chat Fixes by Platform

Fix	Steam (PC)	Standalone
Verify game files	Steam verify tool	Reinstall from EHG website
Overlay conflicts	Steam + Discord overlay	Discord overlay only
Audio device settings	Windows Sound settings	Windows Sound settings
Mic privacy permissions	Windows Privacy → Microphone	Windows Privacy → Microphone
Driver updates	Device Manager / Manufacturer	Device Manager / Manufacturer

Common Misconceptions

“If my mic works in Discord, it should work in Last Epoch.” Not necessarily. Discord has its own audio pipeline and device selection. Last Epoch relies on Windows communication device settings, which Discord bypasses entirely.

“Voice chat issues mean the game is broken.” In most cases, it’s a local configuration problem — wrong device, blocked permissions, or a conflicting overlay. The game’s voice chat system works fine when the environment is set up correctly.

“Push-to-talk means open mic.” These are completely different. Push-to-talk requires you to hold a key to transmit. Open mic transmits constantly. If you have push-to-talk enabled but don’t know the keybind, it’ll seem like voice chat is broken.

Deep Dive Tips

If the basic fixes above don’t work, try these advanced troubleshooting steps. They target less common but equally frustrating causes of voice chat failure.

Disable audio enhancements: In Windows Sound settings → Recording tab → right-click your mic → Properties → Enhancements tab → check Disable all enhancements. Some audio processing features conflict with game voice chat.

Change audio sample rate: In the same Properties window, go to the Advanced tab and set the default format to 16-bit, 48000 Hz (DVD Quality). Some games don’t handle higher sample rates well for voice input.

Run Last Epoch as administrator: Right-click the game executable or Steam shortcut → Run as administrator. This can resolve permission issues that block microphone access.

Check antivirus/firewall: Some security software blocks voice chat traffic. Add Last Epoch and Steam as exceptions in your antivirus and Windows Firewall settings.

Quick Pick Guide

Problem	Most Likely Fix	Time
No one can hear me	Set default communication device	2 min
I can’t hear anyone	Check voice chat enabled in-game	1 min
Voice cuts out randomly	Update audio drivers	10 min
Robotic/distorted voice	Change sample rate to 48kHz	3 min
Worked before, stopped after update	Verify game files	5 min
Mic works in Discord but not game	Check Windows mic privacy settings	3 min

Frequently Asked Questions

Does Last Epoch have voice chat?

Yes, Last Epoch includes built-in voice chat for co-op multiplayer. It’s available when playing with friends in the same party. You can use it alongside or instead of third-party apps like Discord.

Why can’t my friends hear me in Last Epoch?

The most common cause is your microphone not being set as the Windows default communication device. Check Windows Sound settings, verify the in-game input device matches your mic, and make sure Windows privacy settings allow Last Epoch to access your microphone.

How do I enable push-to-talk in Last Epoch?

Go to Settings → Audio → Voice Chat. You’ll see a push-to-talk keybind option. Click it and press the key you want to use. Hold that key while speaking to transmit your voice. If you prefer always-on mic, switch to Open Mic mode instead.

Does Last Epoch voice chat work on Steam Deck?

Voice chat on Steam Deck can be problematic due to Linux audio layer differences. Make sure the correct input device is selected in Steam Deck’s audio settings, and verify the in-game input device matches. Some players report better results using Discord through Prose instead.

Can I use Discord instead of in-game voice chat?

Absolutely. Many Last Epoch players prefer Discord for voice chat because it’s more reliable and offers better audio quality. If in-game voice chat keeps giving you trouble, just disable it in settings and run Discord alongside the game.

Final Thoughts

Voice chat issues in Last Epoch almost always come down to three things: wrong default device, blocked permissions, or a conflicting overlay. Work through the fixes in order — in-game settings first, then Windows settings, then drivers and overlays. Most players resolve the issue within five minutes of checking their default communication device.

If nothing works, the Last Epoch community on Reddit and the official Discord server are active and helpful. Someone has probably dealt with your exact setup before.

Sources & Verification

• Last Epoch Official Forums — Community-reported voice chat fixes and developer responses
• Microsoft Support — Fix Microphone Problems — Official Windows mic troubleshooting guide
• Steam Support — Verify Game Files — How to verify integrity of game files on Steam

What Do You Think?

Got a voice chat fix that worked for your setup? Drop it in the comments below. If you’re still stuck after trying these steps, let us know your hardware and Windows version — we’ll help you figure it out.