Forum Discussion
I can confirm this by stating that this problem has been occurring for multiple players including myself, that this is not a problem of the Private Match mods if being used, it is a recent problem affecting the game itself, and that a multitude of attempts at fixing this have been tried by many different people ranging from:
I want to clarify that public lobbies work, but for some reason the Private Match functions to invite friends are no longer working.
Known and Common Attempts
- Inviting through party first, (both ways), and trying with different people hosting.
- Unfriending and friending players through the EA App in and out of game.
- Turning off EA Overlay, and turning it back on after testing without it.
- Signing out and signing back into the EA App.
- Ensuring no other programs such as Steam or Discord are running in any manner including in the background.
- Restarting the game and restarting the computer.
- Reinstalling the game and or verifying files.
- Manually deleting all game files, (including root folder and Documents settings).
Uncommon Attempts / (DePotMan, your attempts solely for SWBF2 so far.)
- Completely removing the EA App, including all folders, files, temp files, registry entries, etcetera before reinstalling the EA App.
- Running a SFC scannow.
- Restarting the router, and completely uninstalling and reinstalling WiFI and ethernet drivers.
- Updating Windows.
- And finally, trying a different ethernet cable.
(Note: DePotMan, I think you're having an unrelated but similar issue as I've recently tried seeing if the same problem was occurring in SWBF2 with a friend, but was able to get into a CO-OP lobby just fine. There are no true Private Matches in SWBF2 so that's inapplicable.)
Some people also thought the Private Match mods, if they were using them, were a problem and also tried:
Attempts Related to Mod Usage
- Reinstalling the Private Match mod(s) and Frosty Mod Manager.
- Re-downloading the .fbmod file.
Nothing has worked, and many players, including myself, are not aware of why this has happened out of the blue. Hopefully, someone aware to the issue may be able to give an answer as to what happened, and or if a fix comes about.