hey friends, the bug squashing continues. for this thread, let's focus on the Stuck on Configuring issue. please reply with the following info:
Username
Platform
Region
If POS...
Ideas
- Vulture on Steam
- PC
- NA/Canada
- been happening for 2 hours
Its not from enabling or disabling cross play. This just happened because when you enable or disable cross play it forces you to reconnect. This is happening to people who have cross play on or off as well, who have opened the game and attempted to connect. Has nothing to do with cross play.😑
Try not to spread misinformation and confuse the developers. You may have experienced this AFTER disabling or enabling cross play, because you were forced to reconnect.
Not aiming for misinformation. Anecdotal evidence is often REALLY helpful in solving these type of issues. Bugs happen, patches can overlook miniscule details.
Some of the hardest misconfig issues and outages I've solved at work have been thanks to the tiniest detail I overlooked.
To add context. I had disabled crossplay yesterday. I've been in and out fine all day. Buddy got on, I logged out and back in at same time and I have configuring issue and he doesn't. He JUST installed the game which defaults to crossplay.
If the backend work pertained to their server pool or configs, there's a possibility it could be proxy/load-balancer related and that the fixes introduced issues to the clients that were pointing at crossplay vs PC for example. These things happen. Containers are weird, LB/Proxies are finnicky.